This content has been marked as final. Show 5 replies
I dont think there is something called deployFlex try with deploy option with current parameter it should work.
if you need more details simply type this. " help('deploy') "
you will syntax and example will be there.
wls:/mydomain/serverConfig/Servers> progress= deploy('myApp','c:/myapps/myapp.ear','mywar@webserver,myjar@ejbserver', 'nostage', 'c:/myapps/plan.xml')
Deploying myApp from c:/myapps/myapp.ear ...
...Deployment of 'myApp' is successful
Current Status of your Deployment:
Deployment command type: deploy
Deployment State : completed
Deployment Message : null
wls:/mydomain/serverConfig/Servers> deploy(appName='businessApp', path='c:/myapps/business', createPlan='true')
wls:/mydomain/serverConfig/Servers> deploy('demoApp', 'c:/myapps/demos/app/demoApp.ear', targets="myserver",
wls:/mydomain/serverConfig/Servers> deploy('jmsApp', 'c:/myapps/demos/jmsApps/demo-jms.xml', subModuleTargets='jmsApp@managed1')
wls:/mydomain/serverConfig/Servers> deploy('demoApp', 'c:/myapps/demos/app/demoApp.ear', archiveVersion='901-101', appVersion='901-102')
thanks for the feedback.
I'm following Oracle Fusion Application Release Notes 11.1.3 from 1st July, Chapter 188.8.131.52 Mandatory Deployment of Extensible Flexfields:
After upgrading to 184.108.40.206.0, redeploy PIM extensible flexfields using the following Weblogic Server Tool (WLST) command:
This is the only info I have, so I don't know if I need to prepare something first (EGO_ITEM_EFF?), or if I use WLST properly.
One more point I had seen internally that with Flex Fusionapp provide some guide line regarding this issue.
There is BUG 11777495 which help you solve this problem.
Check with support.