on 02-15-2013 12:15 PM
Hi All,
Yesterday, I have applied "EBF 20512:2.1 SP03 PL02" patch on sybase worksapce 2.1.3
by below steps
1. Opened cmd prompt using "run as administrator " option
2. Navigated to the "C:\ebf20512\MobileSDK213patch02-drop7\"
3. Run installebf.bat file
4. I am able to successfully applied patch on my sybase worksapce
Please find the attached Capture1.JPG for the same.
After that I have imported my old workfow application and regenerated the workflow code.
Now minfest.xml file having 2.1.2 as sup workflow version
<ContextVariable>
<Name>SupWorkflowVersion</Name>
<Value>2.1.2</Value>
<Certificate>false</Certificate>
<Password>false</Password>
</ContextVariable>
In Sybase SCC also I am seeing the same, under workflow context variables
Please find the attached Capture2.JPG for the same.
is it sybase worksapce issue?
(or)
PL02 patch not applied properly ?
Please find the Capture3.JPG for present sybase workspace about screen.
Thanks in advance,
Lakshman Balanagu.
For the context variable SupWorkflowVersion, can you take a look at one of your 2.1.3 projects that you have not migrated. I think the SupWorkflowVersion will say 2.1.2.
When you deploy a workflow to SUP, the context variables that are defined in the manifest.xml appear in SCC.
So, I don't think the SupWorkflowVersion number of 2.1.2 is a problem. If I remember correctly, this was something the development team forgot to change prior to the release of 2.1.3.
In the generated workflow folder, compare the comments in the file Workflow.js that was generated using 2.1.3 SP02 with one that was generated using 2.1.3. Specifically there should be a line that says The template used to create this file was compiled on Thu Mar 8, 2012 or something similar for 2.1.3, whereas in 2.1.3 SP02 the value will be different. It is possible though that this particular file was not modified from the 2.1.3 release to the 2.1.3 SP02 release in which case the date would be unchanged. Many of the files are not regenerated if the file already exists such as API.js. I would suggest creating a new mobile workflow, generate the html/js and then take a look at the dates in the top of the comments of files such as API.js, Utils.js etc.
A couple of other places to check would be the jar files that provide the workflow tooling in Eclipse. They typically have dates as part of their name.
Have a look at C:\Sybase\UnwiredPlatform\Unwired_WorkSpace\Eclipse\sybase_workspace\mobile\eclipse\plugins.
The plugins that are named com.subase.uep.xbw.* are related to the mobile workflow tooling. The 2.1.3 release would have versions from around March of 2012 I think.
Finally, have a look at the version number of the Hybrid Web Container.
Hope that helps,
Dan van Leeuwen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, It' not a problem, workflow application running fine.
below are the comments in workflow.js file
/*
* Sybase Mobile Workflow version 2.1.3
*
* Workflow.js
* This file will be regenerated, so changes made herein will be removed the
* next time the workflow is regenerated. It is therefore strongly recommended
* that the user not make changes in this file.
*
* The template used to create this file was compiled on Fri Oct 12 19:39:08 IST 2012
*
* Copyright (c) 2010, 2011 Sybase Inc. All rights reserved.
*/
And pungins version:
C:\Sybase\UnwiredPlatform\MobileSDK213\Unwired_WorkSpace\Eclipse\sybase_workspace
\mobile\eclipse\plugins\com.sybase.uep.xbw.edit_2.1.3.201210121941.jar
So I am consider development team forgot to change prior to the release of 2.1.3
Thanks for the reply
I double-checked and yes, you are correct, SupWorkflowVersion is being generated incorrectly.
It shouldn't cause any specific problems, so you should be fine leaving it the way it is.
Should you wish to address it, however, you can patch it manually, either in the manifest directly or in SCC. We can also provide you with a private patch via support, should you wish.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.