Deploying parts of a JHeadstart application?

In a small JHeadstart project I wonder how deploy the application. The application has to main windows and 12 wizard windows.
As the wizard windows (of course) are closely linked to one of the the two main windows there exists one application definition file (listing all wizard and the main windows).
Currently, the whole application is deployed at the same time. This works fine. What I want is to deploy only parts of the application, lets say only new wizards not previously deployed.
My question is if it is OK and advicable to deploy parts of the application. If yes, I do not expect to get all the details on how to do it here. Hints for further reading would however be appreciated.

J2EE only allows for deploying a complete web application. You cannot redeploy (new) parts of a web application.
So, if you want to deploy the wiuzards separately, then you need to create separate ViewController projects, and deploy them as separate web applications. But then they do not share session state, and users need to log on again for each wizard (unless you are using Single Sign On).
Steven Davelaar,
JHeadstart team.

Similar Messages

Does the Jheadstart application can deploy to Application 10g

Hi Jhs team:
Does the Jheadstart application can deploy to Application 10g ?

Ting Rung,
We did not test this yet, but assuming OC4J did not break backwards compatibility, it should work.
I would say, give it a try, and let us know if you run into problems.
Steven Davelaar,
JHeadstart Team.

Error after deploying JHeadstart application 10.1.3 to OracleAS 10.1.2

Hello JHeadstart Team,
I'm using jdev 10.1.3 (SU5) and jhs 10.1.3 (SU1).
My application runs well in the embedded OC4J. To deploy it to my external application server I did the steps written in the article "How to deploy a JDev 10.1.3 application to OracleAS 10.1.2" (http://blogs.oracle.com/jheadstart/2006/08/27#a54).
Pages with AutoQuery=Yes are running ok.
After calling pages with AutoQuery=No and executing queries I recieve folling error:
500 Internal Server Error
javax.faces.FacesException: #{searchBestaende.advancedSearch}: javax.faces.el.EvaluationException: java.lang.NoSuchMethodError: oracle.jdbc.OraclePreparedStatement.setObjectAtName(Ljava/lang/String;Ljava/lang/Object;)V
     at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:78)
Caused by: javax.faces.el.EvaluationException: java.lang.NoSuchMethodError: oracle.jdbc.OraclePreparedStatement.setObjectAtName(Ljava/lang/String;Ljava/lang/Object;)V
     at com.sun.faces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:130)
     at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:72)
     ... 21 more
Caused by: java.lang.NoSuchMethodError: oracle.jdbc.OraclePreparedStatement.setObjectAtName(Ljava/lang/String;Ljava/lang/Object;)V
     at oracle.jbo.server.OracleSQLBuilderImpl.bindParamValue(OracleSQLBuilderImpl.java:3934)
Are there any libraries missing?
Regards
Peter

Peter,
From the error message, it seems to be an issue with JDBC libraries or JDBC library versions. I suggest you log a TAR through metalink for this issue.
Steven Davelaar,
JHeadstart Team.

New record insert in JHeadstart application deployed to Tomcat

Hello Friends,
I developed an application with JHeadstart and it works well but when I deploy it into Tomcat a problem appears:
I have some records -let's say employees- and I want to enter a new record. I click the "New Employee" button but the selected record seems in the form instead of empty form. This problem is seen in the first run of the program.
How can I overcome this Tomcat problem, I need an immediate help.
thanks...

Dear Muller,
THanks your reply, As my test to generate new jheadstrat application again that using JHEADSTART10.1.2.2.32 release, the problem be solve! but I follow /install.html to migration our exist application that using JHEADSTART10.1.2., the problem cannot be solve after did all migration procedure , the problem whether can be solve using migration path on exist application?
the following is my migration procedure:
For upgrading from a previous JHeadstart 10.1.2.0.x build, apply the following steps:
1. Apply the steps in section Installation in the existing JHeadstart 10.1.2 Home, overwriting the old JHeadstart 10.1.2.x files.
2. For each JHeadstart project where you want to make it possible to run JHeadstart Application Generator with all the new features and fixes, perform the following steps:
* Select all JHeadstart Generator Templates (*.jut files, *.jjt files, and *.jtp files) in the JDeveloper (ViewController) Project and choose File - Erase from Disk. If you customized one or more templates, you should re-apply the functional changes you made.
* Select all JHeadstart generated files in [HTML Root]\common in the JDeveloper (ViewController) Project and choose File - Erase from Disk. If you customized one or more of these files, you should re-apply the functional changes you made.
* In each Application Structure File, for each Lookup of type "lov", turn on the new Generation Switch "Generate LOV Page?"
3. Other upgrade steps to perform for each JHeadstart project, to ensure that the new JHeadstart Runtime will work correctly:
* Correct the link to the JHeadstart documentation in index.html. In previous builds, this link was incorrect. It should be * Re-enable JHeadstart on each (ViewController) JHeadstart project. Choose Overwrite All and Yes to All, unless you know you have customized images or other supported files other than web.xml or uix-config.xml. A backup will always be made of those two files. If you customized the uix-config.xml or web.xml file, you will have to re-apply the customizations.
* If you don't generate the Struts-Config Service-level Entries anymore (a setting in the JHeadstart Application Structure File), you should manually add the processorClass attribute to the <controller> element of your struts-config.xml file(s) like this: <controller ... processorClass="oracle.jheadstart.controller.strutsadf.JhsRequestProcessor"/>
* If you subclassed any JHeadstart runtime classes in your own Java classes, check the overridden methods to see if they have changed. You might need to change the way you override the JHeadstart behavior as well.
Note that if you have overridden classes in JhsDataAction just to override default behavior of the JHeadstart BindingUtils or ReportingUtils classes, the new JhsDataAction has a much easier way to achieve that. Just override JhsDataAction.getBindingUtils() or JhsDataAction.getReportingUtils(), and make sure that it returns your own subclass of BindingUtils or ReportingUtils.
For upgrading from a previous JHeadstart 10.1.2.x build, apply the following steps:
1. Apply the steps in section Installation in the existing JHeadstart 10.1.2 Home, overwriting the old JHeadstart 10.1.2.x files.
2. Re-enable JHeadstart on each (ViewController) JHeadstart project. Choose Overwrite All and Yes to All, unless you know you have customized images or other supported files other than web.xml or uix-config.xml. A backup will always be made of web.xml and uix-config.xml. If you customized the uix-config.xml or web.xml file, you will have to re-apply the customizations.

Deploying OSB project as a part of a bigger application

Hi friends,
how can we deploy OSB as a part of a bigger application ?
Lets just say,
I am getting a request packet from front end application. I process this request using OSB and I am getting the required response packet from the backend legacy system.
Now the BIG question......what do I do with this response packet.

no
by using a default descriptor like war or ear you won't be able to do this
like vladodias said you could create some big zipfile archive this and let for example hudson do the deployment.
deployment in this case means, unzip the whole zipfile and deploy all the artifcats which are in it (deploy ear/deploy war/deploy jar/deploy osbjar/execute sql scripts/etc)
in that case you will have sort of 2 extra steps in your deployment model. 1 pre archive step which will bundle all the artificats created by your other deployment steps (creating war etc), and 1 pre deployment step which will unzip the file and execute all the default deploy steps on those unzipped archives (like deploy war/deploy ear/execute sql/etc)

Problem deploying parts of CS4

I have some problems deploying parts of CS4 Design Std
I ran setup --record=1 and built XML files for each Acrobat, Illustrator, InDesign and Photoshop and each time I deselected every component which could be deselected (like Acrobat.com, Air, Flashplayer,...)
(Some people don't need Acrobat, others don't need InDesign and so on and noone needs air and Flashplayer, as they are maintained already)
If I run Setup.exe --mode=silent --deploymentFile="$application.xml" each setup works fine.
But as soon as I installed Acrobat the InDesign setup fails with code 7 and also the other way round.
Acrobat, Illustrator and Photoshop together work flawlessly.
acrobat.xml
<?xml version="1.0" encoding="UTF-8"?>
<Deployment>
<Properties>
<Property name="EULA_LANGUAGE">de_DE</Property>
<Property name="INSTALLDIR">C:\Program Files\Adobe</Property>
<Property name="OS64Bit">1</Property>
<Property name="StartMenuSubFolder">C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Adobe Design Standard CS4</Property>
<Property name="defaultLanguage">de_DE</Property>
<Property name="driverAdobeCode">{AA1AFF46xxx}</Property>
<Property name="eula_EPIC_EULA_ACCEPTED">1</Property>
<Property name="eula_EPIC_EULA_SELECTED">2</Property>
<Property name="installLanguage">de_DE</Property>
<Property name="installSourcePath">C:\Program Files (x86)\Common Files\Adobe\Installers\1e3ba55b33b1e8227645fb9c82acca3</Property>
<Property name="mediaName">Adobe CS4 Design Standard Disc 1</Property>
<Property name="mediaPath">payloads\AdobeDesignSuiteStandard4-mul\AdobeDesignSuiteStandard4-mul.msi </Property>
<Property name="mediaType">0</Property>
<Property name="mediaVolumeIndex">1</Property>
<Property name="overrideFile">0</Property>
<Property name="pers_EPIC_SERIAL">1327xxx</Property>
<Property name="serialNumber">1327xxx</Property>
<Property name="sessionID">1e3ba55b33b1e8227645fb9c82acca3</Property>
<Property name="setupVersion">2.0.138.0</Property>
</Properties>
<Payloads>
<Payload adobeCode="{AA1AFF46-803D-4446-BDF3-CDB5F9E33D6D}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{AC76BA86-1033-F400-7760-000000000004}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{0A621EC5-B98B-45C9-95FE-A7D0DA3150EA}">
<Action>donotinstall</Action>
</Payload>
<Payload adobeCode="{5746C6E3-DC6E-4762-9445-F89C50B5E1D2}">
<Action>donotinstall</Action>
</Payload>
<Payload adobeCode="{5D195AB1-30AC-44F6-93FE-225CE5BBAB74}">
<Action>donotinstall</Action>
</Payload>
</Payloads>
</Deployment>
InDesign.xml
<?xml version="1.0" encoding="UTF-8"?>
<Deployment>
<Properties>
<Property name="EULA_LANGUAGE">de_DE</Property>
<Property name="INSTALLDIR">C:\Program Files\Adobe</Property>
<Property name="OS64Bit">1</Property>
<Property name="StartMenuSubFolder">C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Adobe Design Standard CS4</Property>
<Property name="defaultLanguage">de_DE</Property>
<Property name="driverAdobeCode">{AA1AFF46xxx}</Property>
<Property name="eula_EPIC_EULA_ACCEPTED">1</Property>
<Property name="eula_EPIC_EULA_SELECTED">2</Property>
<Property name="installLanguage">de_DE</Property>
<Property name="installSourcePath">C:\Program Files (x86)\Common Files\Adobe\Installers\1e3ba55b33b1e8227645fb9c82acca3</Property>
<Property name="mediaName">Adobe CS4 Design Standard Disc 1</Property>
<Property name="mediaPath">extensions\AdobeInDesign6AppLang-de_DE\AdobeInDesign6AppLang-de_DE.msi</ Property>
<Property name="mediaType">0</Property>
<Property name="mediaVolumeIndex">1</Property>
<Property name="overrideFile">0</Property>
<Property name="pers_EPIC_SERIAL">1327xxx</Property>
<Property name="serialNumber">1327xxx</Property>
<Property name="sessionID">1e3ba55b33b1e8227645fb9c82acca3</Property>
<Property name="setupVersion">2.0.138.0</Property>
</Properties>
<Payloads>
<Payload adobeCode="{043A67CA-08C4-4669-A2A1-B03F6D8D509C}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{064F0D64-1F54-4F4B-953E-BAED5D7E69B2}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{08D66D31-CC4B-101B-B7BF-FD1B1E2718A8}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{0967604F-33E6-4C6B-934B-157C3AB4ED4C}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{14A5A29B-D252-4575-B40C-695B8D8B34D5}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{2965A5F0-0326-4479-B140-F5799BD025B7}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{2B47D5DE-E019-4130-AB69-2DAB4DEEBB0A}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{3095E614-711B-48D2-BAAF-0CA9D9968F68}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{31FC14DD-7641-4BEB-B5D1-9976F99AF956}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{35304775-CB5F-101B-A142-83B5468C225C}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{395FC443-B34B-4E77-9928-23C147FC83F1}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{3A4D8E3D-83E0-425F-A8FB-B04538CDC2A0}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{490F274E-689A-4ECF-AC3E-322347ED7613}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{53560287-20EA-4EB6-9B5C-5B1EC080350A}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{563275A9-CC66-101B-8B71-81B8A321A480}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{5A2D6654-8164-4810-A76F-FD160223558E}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{5C99A447-812B-4531-816B-38F0C8B19F02}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{603DA164-1FA4-43F4-AD82-0A56206E5BD7}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{73656117-7621-4603-9830-786F7F46F966}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{8167335C-8FEA-4576-8EC2-8AC77EC58F19}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{87809DB4-F038-4C7B-9CA9-FFB6EAE6042F}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{87C4EC3E-47F0-4287-A436-9ADA103E05E9}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{9907B3BB-23CD-424E-B18F-A2E158D4B6D0}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{9D0C6527-C1EC-4AFD-B446-4BC12C83C8EF}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{9DFDAC02-972C-4A6A-9419-AD702DC40EC6}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{A9A71A55-3C8A-4DCD-8291-1F4B749627C9}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{AA1AFF46-803D-4446-BDF3-CDB5F9E33D6D}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{AB8E4534-C573-4CC9-BA6A-76DD14055510}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{B2A01A26-BCD8-4BFB-ADC2-164416D42A38}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{D95B5192-2606-4176-893B-7B6704D2605B}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{E769C759-5B9B-487B-AAC3-FAB7015D7B9A}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{E9124DCC-945E-4450-B8CD-689A6FE15F8D}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{0A621EC5-B98B-45C9-95FE-A7D0DA3150EA}">
<Action>donotinstall</Action>
</Payload>
<Payload adobeCode="{3CD02B3D-9EEE-4786-95A8-73E7BA8558CA}">
<Action>donotinstall</Action>
</Payload>
<Payload adobeCode="{5746C6E3-DC6E-4762-9445-F89C50B5E1D2}">
<Action>donotinstall</Action>
</Payload>
<Payload adobeCode="{5D195AB1-30AC-44F6-93FE-225CE5BBAB74}">
<Action>donotinstall</Action>
</Payload>
<Payload adobeCode="{6743AE49-4594-4CAE-807C-27682446F498}">
<Action>donotinstall</Action>
</Payload>
<Payload adobeCode="{CBC8AB3C-85F0-4D16-8E01-95E0343EE383}">
<Action>donotinstall</Action>
</Payload>
</Payloads>
</Deployment>
Also the complete Suite-setup created by wizard returns code 7
complete.xml
<?xml version="1.0" encoding="UTF-8"?>
<Deployment>
<Properties>
<Property name="EULA_LANGUAGE">de_DE</Property>
<Property name="INSTALLDIR">C:\Program Files\Adobe</Property>
<Property name="OS64Bit">1</Property>
<Property name="StartMenuSubFolder">C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Adobe Design Standard CS4</Property>
<Property name="defaultLanguage">de_DE</Property>
<Property name="driverAdobeCode">{AA1AFF46xxx}</Property>
<Property name="eula_EPIC_EULA_ACCEPTED">1</Property>
<Property name="eula_EPIC_EULA_SELECTED">2</Property>
<Property name="installLanguage">de_DE</Property>
<Property name="installSourcePath">C:\Program Files (x86)\Common Files\Adobe\Installers\1e3ba55b33b1e8227645fb9c82acca3</Property>
<Property name="mediaName">Adobe CS4 Design Standard Disc 1</Property>
<Property name="mediaPath">extensions\AdobeInDesign6CommonLang-de_DE\AdobeInDesign6CommonLang-de_DE .msi</Property>
<Property name="mediaType">0</Property>
<Property name="mediaVolumeIndex">1</Property>
<Property name="overrideFile">0</Property>
<Property name="pers_EPIC_SERIAL">1327xxx</Property>
<Property name="serialNumber">1327xxx</Property>
<Property name="sessionID">1e3bxxx</Property>
<Property name="setupVersion">2.0.138.0</Property>
</Properties>
<Payloads>
<Payload adobeCode="{043A67CA-08C4-4669-A2A1-B03F6D8D509C}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{064F0D64-1F54-4F4B-953E-BAED5D7E69B2}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{08D66D31-CC4B-101B-B7BF-FD1B1E2718A8}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{0967604F-33E6-4C6B-934B-157C3AB4ED4C}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{0D47D055-102E-443D-9FE7-FFF0BBAB6A98}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{14A5A29B-D252-4575-B40C-695B8D8B34D5}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{176894A3-E35F-45C0-98E3-3FB4CD46C0E0}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{2965A5F0-0326-4479-B140-F5799BD025B7}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{2B47D5DE-E019-4130-AB69-2DAB4DEEBB0A}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{3095E614-711B-48D2-BAAF-0CA9D9968F68}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{31FC14DD-7641-4BEB-B5D1-9976F99AF956}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{35304775-CB5F-101B-A142-83B5468C225C}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{395FC443-B34B-4E77-9928-23C147FC83F1}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{3A4D8E3D-83E0-425F-A8FB-B04538CDC2A0}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{490F274E-689A-4ECF-AC3E-322347ED7613}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{4F3CE025-D60B-4E6B-8D39-B04CD3769008}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{53560287-20EA-4EB6-9B5C-5B1EC080350A}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{563275A9-CC66-101B-8B71-81B8A321A480}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{5A2D6654-8164-4810-A76F-FD160223558E}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{5C99A447-812B-4531-816B-38F0C8B19F02}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{603DA164-1FA4-43F4-AD82-0A56206E5BD7}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{6A7D180B-9A75-4C62-BE94-FE44BE3732C2}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{71C506FA-C006-4822-A371-059856E706CA}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{73656117-7621-4603-9830-786F7F46F966}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{79E0F594-E8F3-4930-8EBD-0C7178302EFB}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{7F60FD0C-F2FF-433A-A91C-EC76152DEF05}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{8167335C-8FEA-4576-8EC2-8AC77EC58F19}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{87809DB4-F038-4C7B-9CA9-FFB6EAE6042F}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{87C4EC3E-47F0-4287-A436-9ADA103E05E9}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{98D81F21-D408-4431-B1CD-FD5F34F70DA0}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{9907B3BB-23CD-424E-B18F-A2E158D4B6D0}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{9D0C6527-C1EC-4AFD-B446-4BC12C83C8EF}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{9DFDAC02-972C-4A6A-9419-AD702DC40EC6}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{9F299EC3-0FBB-4C64-80C8-66849A26CFBD}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{A6148177-E733-4F44-8123-C7565DFA7819}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{A9A71A55-3C8A-4DCD-8291-1F4B749627C9}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{AA1AFF46-803D-4446-BDF3-CDB5F9E33D6D}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{AB8E4534-C573-4CC9-BA6A-76DD14055510}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{AC76BA86-1033-F400-7760-000000000004}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{B2A01A26-BCD8-4BFB-ADC2-164416D42A38}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{CFCD7AD2-150A-4194-BA98-4C59850A0F98}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{D7AF82DE-06CD-493D-8866-58BD4A7C54EB}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{D95B5192-2606-4176-893B-7B6704D2605B}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{DBB1B2E9-0DF9-495C-B58D-C23A3599EDA7}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{E769C759-5B9B-487B-AAC3-FAB7015D7B9A}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{E9124DCC-945E-4450-B8CD-689A6FE15F8D}">
<Action>install</Action>
</Payload>
<Payload adobeCode="{0A621EC5-B98B-45C9-95FE-A7D0DA3150EA}">
<Action>donotinstall</Action>
</Payload>
<Payload adobeCode="{3CD02B3D-9EEE-4786-95A8-73E7BA8558CA}">
<Action>donotinstall</Action>
</Payload>
<Payload adobeCode="{40E33B80-0C73-41A0-82A5-9AF7D1D68C98}">
<Action>donotinstall</Action>
</Payload>
<Payload adobeCode="{5746C6E3-DC6E-4762-9445-F89C50B5E1D2}">
<Action>donotinstall</Action>
</Payload>
<Payload adobeCode="{5D195AB1-30AC-44F6-93FE-225CE5BBAB74}">
<Action>donotinstall</Action>
</Payload>
<Payload adobeCode="{6743AE49-4594-4CAE-807C-27682446F498}">
<Action>donotinstall</Action>
</Payload>
<Payload adobeCode="{8AD0C0B9-B397-45FE-89A3-D42F95F6E9EF}">
<Action>donotinstall</Action>
</Payload>
<Payload adobeCode="{CBC8AB3C-85F0-4D16-8E01-95E0343EE383}">
<Action>donotinstall</Action>
</Payload>
</Payloads>
</Deployment>
Where is the problem?
Unfortunately, Adobe refuses support, as this is a custom installation... (I have several tickets and they didn't solve a single one finding some pretext every single time or simply withdraw it *mad*)

J2EE only allows for deploying a complete web application. You cannot redeploy (new) parts of a web application.
So, if you want to deploy the wiuzards separately, then you need to create separate ViewController projects, and deploy them as separate web applications. But then they do not share session state, and users need to log on again for each wizard (unless you are using Single Sign On).
Steven Davelaar,
JHeadstart team.

How to Deploy 11g Forms and EBS Applications?

Dear All,
Just need to know some technical information regarding EBS.
Previously I have worked with Oracle forms and reports 6i and we used to deploy the application developed in this tool to publish using Application Server 9i/10g. I also have hands on experience on that.
Now after 4 years I am again trying to do some hands-on on later versions.
Just want to know that for Developer Suite 10g, If i developer the application it will be published using Application Server 10g? so that the user can access this application?
How EBS application is host and published?
Will really appreciate your kind help.
Thanks, Imran

How to Deploy 11g Forms and EBS Applications? Forms 11g is not certified with EBS 11i/R12
Just need to know some technical information regarding EBS.
Previously I have worked with Oracle forms and reports 6i and we used to deploy the application developed in this tool to publish using Application Server 9i/10g. I also have hands on experience on that.
Now after 4 years I am again trying to do some hands-on on later versions.
Just want to know that for Developer Suite 10g, If i developer the application it will be published using Application Server 10g? so that the user can access this application?
How EBS application is host and published?
Will really appreciate your kind help.Oracle Developer 10g comes as part of Oracle EBS installation, so no Oracle AS installation is required. You need need to install Developer 10g on your client to build forms/reports.
Using the OracleAS 10.1.2 Forms and Reports Builders with Oracle Applications Release 12 [ID 444248.1]
How To Bring Up 10G Forms Builder In R12 Environment? [ID 579318.1]
Thanks,
Hussein

Deploying junitee outside of the application ear file

I have an application that is deployed within an ear file, and I have junitee tests
within a war file, called test.war. I would like to not have to place the test.war
within the ear file because the ear may be release code but I still want to test
it using the junitee tests. Instead I would like to optionally add the test.war
to the application context and not the ear file. How would I go about doing that?
I tried to deploy the test.war from the weblogic console, and hand editing the
config.xml, and adding the test.war as a module to the application.xml (within
the ear file).
In all cases when I try to then use classes within the ear file I get ClassNotFoundExceptions.
Probably because Weblogic is not including the test.war as part of the same application.
Thank in advance for any help.
-Fazle

I'd probably have 2 build targets, debug and production. Your debug
target could include the unit test war file.
-- Rob
Fazle Khan wrote:
I have an application that is deployed within an ear file, and I have junitee tests
within a war file, called test.war. I would like to not have to place the test.war
within the ear file because the ear may be release code but I still want to test
it using the junitee tests. Instead I would like to optionally add the test.war
to the application context and not the ear file. How would I go about doing that?
I tried to deploy the test.war from the weblogic console, and hand editing the
config.xml, and adding the test.war as a module to the application.xml (within
the ear file).
In all cases when I try to then use classes within the ear file I get ClassNotFoundExceptions.
Probably because Weblogic is not including the test.war as part of the same application.
Thank in advance for any help.
-Fazle

What is JHeadstart? Can Forms be converted to JHeadstart applications?

Is JHeadstart a part of Oracle Developer Suite? Can Designer 10g Release 2 generate JHeadstart applications?

JHeadstart is not part of ODS. It is a separate consulting offering, see the FAQ on the JHeadstart Product center for more info:
http://www.oracle.com/technology/consulting/9iservices/jheadstart.html
And yes, JHeadstart can generate ADF/JSF application from Designer metadata. See the Developers Guide (http://download.oracle.com/consulting/jhsdevguide1013.pdf), chapter 4 for more info.
Steven Davelaar,
JHeadstart Team.

Error while deploying web service in Netweaver application

Hi,
In my group, two members working in the development of a WebDynpro based application. We have created a track and are using the same for development. For our application
the team member 1 created a Dc say DC1 for EJBS(both
entity and session) and another DC say DC2 for the application archieve 'ear'
and activated the two DCS. When another member of
the team is trying to create a webservice in the checked out DC, the
webservice was created successfully but while deploying the
application archive DC it gives an error (details furnished below).
Error:
:Caught exception during application deployment from SAP J2EE Engine's
deploy service:java.rmi.RemoteException: Cannot deploy
application asianpaints.com/pe_mgt_ear.. Reason: Webservices common
deployment exception! The reason is: Error occurred,
trying to update web services for application
asianpaints.com/pe_mgt_ear. . Additional info: none; nested exception
is:
java.lang.Exception:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment
exception! The reason is: Error occurred, trying to update web services
for application asianpaints.com/pe_mgt_ear.
WSDeploymentException: Webservices common deployment exception! The
reason is: Error occurred, trying to parse documentation
for web service NewPEProcessorService. .
So we created one more DC3(referring the entity beans of DC1) and
created the required session bean and webservice in that
DC. It got deployed successfully. Again when we are trying to create
new webservice it got created but the deployment got
aborted with the same error as mentioned above:
The detailed error description we got in both the cases is given below:
Mar 30, 2006 1:07:39 PM /userOut/deploy
(com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy
Thread,5,main]] INFO:
[005]Additional log information about the deployment
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[/usr/sap/J2E/JC00/SDM/program/log/sdmcl20060330074205.log]/>
<!PATTERN[sdmcl20060330074205.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[ISO8859_1]/>
<!LOGHEADER[END]/>
Mar 30, 2006 1:12:07 PM Info: -
Starting deployment -
Mar 30, 2006 1:12:07 PM Info: Loading selected archives...
Mar 30, 2006 1:12:07 PM Info: Loading
archive '/usr/sap/J2E/JC00/SDM/program/temp/temp35515asianpaints.com~pe_mgt_ear.ear'
Mar 30, 2006 1:12:17 PM Info: Selected archives successfully loaded.
Mar 30, 2006 1:12:17 PM Info: Actions per selected component:
Mar 30, 2006 1:12:17 PM Info: Update: Selected development component
'pe_mgt_ear'/'asianpaints.com'/'J2E_HSSPNEW_D'/'20060330130420' updates
currently deployed development component
'pe_mgt_ear'/'asianpaints.com'/'J2E_HSSPNEW_D'/'8008'.
Mar 30, 2006 1:12:17 PM Info: The deployment prerequisites finished
without any errors. All items are correct.
Mar 30, 2006 1:12:17 PM Info: Saved current Engine state.
Mar 30, 2006 1:12:17 PM Info: Error handling strategy: OnErrorStop
Mar 30, 2006 1:12:17 PM Info: Update strategy: UpdateAllVersions
Mar 30, 2006 1:12:17 PM Info: Starting: Update: Selected development
component
'pe_mgt_ear'/'asianpaints.com'/'J2E_HSSPNEW_D'/'20060330130420' updates
currently deployed development component
'pe_mgt_ear'/'asianpaints.com'/'J2E_HSSPNEW_D'/'8008'.
Mar 30, 2006 1:12:17 PM Info: SDA to be deployed:
/usr/sap/J2E/JC00/SDM/root/origin/asianpaints.com/pe_mgt_ear/J2E_HSSPNEW_D/20060330130420/temp35515asianpaints.com~pe_mgt_ear
.ear
Mar 30, 2006 1:12:17 PM Info: Software type of SDA: J2EE
Mar 30, 2006 1:12:17 PM Info: ***** Begin of SAP J2EE Engine
Deployment (J2EE Application) *****
Mar 30, 2006 1:15:07 PM Info: Begin of log messages of the target
system:
06/03/30 13:12:17 -
06/03/30 13:12:20 - Start updating EAR file...
06/03/30 13:12:20 - start-up mode is lazy
06/03/30 13:12:23 - EAR file updated successfully for 3161ms.
06/03/30 13:12:23 - Start updating...
06/03/30 13:12:24 - EAR file uploaded to server for 525ms.
06/03/30 13:15:07 - ERROR: Not updated. Deploy Service returned ERROR:
java.rmi.RemoteException: Cannot deploy
application asianpaints.com/pe_mgt_ear..
Reason: Webservices common deployment exception!
The reason is: Error occurred, trying to update web
services for application asianpaints.com/pe_mgt_ear. . Additional info:
none; nested exception is:
java.lang.Exception:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException:
Webservices common deployment exception! The reason is: Error occurred,
trying to update web services for application
asianpaints.com/pe_mgt_ear. . Additional info: none
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:164)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:118)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:86)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateManager.makeUpdate(WSUpdateManager.java:52)
at
com.sap.engine.services.webservices.server.deploy.WSDeployer.makeUpdate
(WSDeployer.java:274)
at
com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:390)
at
com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:387)
at
com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:159)
at
com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java
:290)
at
com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
at
com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
at
com.sap.engine.services.deploy.server.DeployServiceImpl.update
(DeployServiceImpl.java:584)
at
com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch
(DeployServiceImplp4_Skel.java:1278)
at
com.sap.engine.services.rmi_p4.DispatchImpl._runInternal
(DispatchImpl.java:294)
at
com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at
com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request
(P4SessionProcessor.java:119)
at
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageLis
tener.java:33)
at
com.sap.engine.core.cluster.impl6.session.MessageRunner.run
(MessageRunner.java:41)
at
com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged
(Native Method)
at
com.sap.engine.core.thread.impl3.SingleThread.execute
(SingleThread.java:95)
at
com.sap.engine.core.thread.impl3.SingleThread.run
(SingleThread.java:160) Caused by:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices
deployment exception! The reason is: Error occurred, trying to generate
web services deployment files for application
asianpaints.com/pe_mgt_ear. . The error refers to application: none,
jar: , web service: .
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:296)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.deployWebServices(WSUpdateProcessor.java:262)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:155)
... 21 more
Caused by:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common
deployment exception! The reason is: Error occurred, parsing
com.sap.engine.services.webservices.server.deploy.descriptors.sapwebservices.WSDescriptor descriptor, application
asianpaints.com/pe_mgt_ear, web service NewPEProcessorService, location
message: type: jar file, location:
/usr/sap/J2E/JC00/j2ee/cluster/server0/./temp/deploy/work/deploying/reader1143704544275/asianpaints.com~HSSPNEW_UserDetails.j
ar . . Additional info:
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:907)
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebService(WSDefinitionFactory.java:176)
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebServices(WSDefinitionFactory.java:158)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:284)
... 23 more
Caused by:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common
deployment exception! The reason is: Error occurred, trying to parse
documentation for web service NewPEProcessorService. .
Additional info:
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseDocumentation(WSDefinitionFactory.java:1586)
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDAndDocumentation(WSDefinitionFactory.java:15
60)
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:814)
... 26 more
Caused by: java.lang.NullPointerException
at
com.sap.engine.services.deploy.server.DeployServiceImpl.update
(DeployServiceImpl.java:596)
at
com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch
(DeployServiceImplp4_Skel.java:1278)
at
com.sap.engine.services.rmi_p4.DispatchImpl._runInternal
(DispatchImpl.java:294)
at
com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at
com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request
(P4SessionProcessor.java:119)
at
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageLis
tener.java:33)
at
com.sap.engine.core.cluster.impl6.session.MessageRunner.run
(MessageRunner.java:41)
at
com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged
(Native Method)
at
com.sap.engine.core.thread.impl3.SingleThread.execute
(SingleThread.java:95)
at
com.sap.engine.core.thread.impl3.SingleThread.run
(SingleThread.java:160) Caused by:
java.lang.Exception:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment exception! The
reason is: Error occurred, trying to update web services for
application asianpaints.com/pe_mgt_ear. . Additional info: none
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:164)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:118)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:86)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateManager.makeUpdate(WSUpdateManager.java:52)
at
com.sap.engine.services.webservices.server.deploy.WSDeployer.makeUpdate
(WSDeployer.java:274)
at
com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:390)
at
com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:387)
at
com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:159)
at
com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java
:290)
at
com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
at
com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
at
com.sap.engine.services.deploy.server.DeployServiceImpl.update
(DeployServiceImpl.java:584)
at
com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch
(DeployServiceImplp4_Skel.java:1278)
at
com.sap.engine.services.rmi_p4.DispatchImpl._runInternal
(DispatchImpl.java:294)
at
com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at
com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request
(P4SessionProcessor.java:119)
at
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageLis
tener.java:33)
at
com.sap.engine.core.cluster.impl6.session.MessageRunner.run
(MessageRunner.java:41)
at
com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged
(Native Method)
at
com.sap.engine.core.thread.impl3.SingleThread.execute
(SingleThread.java:95)
at
com.sap.engine.core.thread.impl3.SingleThread.run
(SingleThread.java:160) Caused by:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices
deployment exception! The reason is: Error occurred, trying to generate
web services deployment files for application
asianpaints.com/pe_mgt_ear. . The error refers to application: none,
jar: , web service: .
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:296)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.deployWebServices(WSUpdateProcessor.java:262)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:155)
... 21 more
Caused by:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common
deployment exception! The reason is: Error occurred, parsing
com.sap.engine.services.webservices.server.deploy.descriptors.sapwebservices.WSDescriptor descriptor, application
asianpaints.com/pe_mgt_ear, web service NewPEProcessorService, location
message: type: jar file, location:
/usr/sap/J2E/JC00/j2ee/cluster/server0/./temp/deploy/work/deploying/reader1143704544275/asianpaints.com~HSSPNEW_UserDetails.j
ar . . Additional info:
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:907)
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebService(WSDefinitionFactory.java:176)
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebServices(WSDefinitionFactory.java:158)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:284)
... 23 more
Caused by:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common
deployment exception! The reason is: Error occurred, trying to parse
documentation for web service NewPEProcessorService. .
Additional info:
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseDocumentation(WSDefinitionFactory.java:1586)
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDAndDocumentation(WSDefinitionFactory.java:15
60)
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:814)
... 26 more
Caused by: java.lang.NullPointerException
at
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException.writeReplace(WSDeploymentException.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0
(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke
(Method.java:324)
at java.io.ObjectStreamClass.invokeWriteReplace
(ObjectStreamClass.java:896)
at java.io.ObjectOutputStream.writeObject0
(ObjectOutputStream.java:1011)
at java.io.ObjectOutputStream.defaultWriteFields
(ObjectOutputStream.java:1332)
at java.io.ObjectOutputStream.writeSerialData
(ObjectOutputStream.java:1304)
at
java.io.ObjectOutputStream.writeOrdinaryObject
(ObjectOutputStream.java:1247)
at java.io.ObjectOutputStream.writeObject0
(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.writeObject
(ObjectOutputStream.java:278)
at
com.sap.engine.services.rmi_p4.DispatchImpl.throwException
(DispatchImpl.java:135)
at
com.sap.engine.services.rmi_p4.DispatchImpl._runInternal
(DispatchImpl.java:296)
... 8 more
For detailed information see the log file of the
Deploy Service.
06/03/30 13:15:07 -
Mar 30, 2006 1:15:07 PM Info: End of log messages of the target
system.Mar 30, 2006 1:15:07 PM Info: ***** End of SAP J2EE Engine
Deployment
(J2EE Application) *****
Mar 30, 2006 1:15:07 PM Error: Aborted: development component
'pe_mgt_ear'/'asianpaints.com'/'J2E_HSSPNEW_D'/'20060330130420':
Caught exception during application deployment from SAP J2EE Engine's
deploy service:
java.rmi.RemoteException: Cannot deploy application
asianpaints.com/pe_mgt_ear..
Reason: Webservices common deployment exception! The reason is: Error
occurred, trying to update web services for application
asianpaints.com/pe_mgt_ear. . Additional info: none; nested exception
is:
java.lang.Exception:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common
deployment exception! The reason is: Error occurred, trying to update
web services for application
asianpaints.com/pe_mgt_ear. . Additional info: none
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:164)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:118)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:86)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateManager.makeUpdate(WSUpdateManager.java:52)
at
com.sap.engine.services.webservices.server.deploy.WSDeployer.makeUpdate
(WSDeployer.java:274)
at
com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:390)
at
com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:387)
at
com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:159)
at
com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java
:290)
at
com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:323)
at
com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3027)
at
com.sap.engine.services.deploy.server.DeployServiceImpl.update
(DeployServiceImpl.java:584)
at
com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch
(DeployServiceImplp4_Skel.java:1278)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal
(DispatchImpl.java:294)
at com.sap.engine.services.rmi_p4.DispatchImpl._run
(DispatchImpl.java:183)
at
com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request
(P4SessionProcessor.java:119)
at
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageLis
tener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run
(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run
(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute
(SingleThread.java:95)
at com.sap.engine.core.thread.impl3.SingleThread.run
(SingleThread.java:160)
Caused by:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices deployment exception! The
reason is: Error occurred, trying to generate web services deployment
files for application asianpaints.com/pe_mgt_ear. . The
error refers to application: none, jar: , web service: .
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:296)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.deployWebServices(WSUpdateProcessor.java:262)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:155)
... 21 more
Caused by:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment
exception! The reason is: Error occurred, parsing
com.sap.engine.services.webservices.server.deploy.descriptors.sapwebservices.WSDescriptor descriptor, application
asianpaints.com/pe_mgt_ear, web service NewPEProcessorService, location
message: type: jar file, location:
/usr/sap/J2E/JC00/j2ee/cluster/server0/./temp/deploy/work/deploying/reader1143704544275/asianpaints.com~HSSPNEW_UserDetails.j
ar . . Additional info:
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:907)
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebService(WSDefinitionFactory.java:176)
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebServices(WSDefinitionFactory.java:158)
at
com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:284)
... 23 more
Caused by:
com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment
exception! The reason is: Error occurred, trying to parse documentation
for web service NewPEProcessorService. . Additional
info:
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseDocumentation(WSDefinitionFactory.java:1586)
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDAndDocumentation(WSDefinitionFactory.java:15
60)
at
com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:814)
... 26 more
Caused by: java.lang.NullPointerException
(message ID:
com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Mar 30, 2006 1:15:17 PM Info: J2EE Engine is in same state
(online/offline) as it has been before this deployment process.
Mar 30, 2006 1:15:17 PM Error: -
At least one of the Deployments
failed -
Deployment failure happens only when the DC contains a web service; else, it goes through properly.
Can anyone of you indicate where we are going wrong and what should be done to resolve this issue?
Thanks a lot in advance.
Regards,
Ravi

Hi,
You can go to the Visual Administrator -> <SID> -> Server -> Services -> Deploy -> Runtime tab -> option Container at the bottom and see if everything is correct and running in the webservices_container.
If something necessary to the deployment is not started you can select it and click in start.
I hope it helps.
Thanks,
Anderson

Deployment of an Adobe AIR application in an enterprise environment

Dear Team members,
first of all my apologies for posting this thread in more than one forum (see Installations Issues) but the argument is very important to us and I don't know where discuss it.
I would like to post a question to you regarding deployment doubts that we are trying to address.
My company is working on the new version of our primary application previously built as a J2EE application with some reporting functions with Flex, and we want to use AIR in order to leverage its possibilities:
Seamless integration with existing application functionalities (implemented as standard JEE web application pages) thanks to the integrated HTML capabilities
Improved integration of the user interface with the desktop
Native processes to provide additional functionalities
Our application is targeted to pharmaceutical industry, subject to FDA regulations, and it affects more than 5000 users for each customer, so we have some specific requirements affecting the deployment and distribution of the software:
Allow to run multiple versions of the software on the same client machine (to support test and acceptance activities in addition to the production environment)
Minimize the effort of the initial setup on each client
Manage the version upgrades without manual activities on each client
Keep the test/acceptance and production environments strictly aligned to improve effectiveness of formal validation (ideally, an application once validated should be transported in production without any source code modification, recompilation or repackaging)
The current browser-based strategy is perfectly fit to these requirements, and in the shift towards a desktop-based strategy we need to continue satisfying them as much as possible. We evaluated the standard distribution strategy of Adobe AIR applications, and noticed several attention points in this scenario.
The first issue we encountered is the back-end services endpoint discovery problem. Simply hardcoding a server URL in the packaged application could be a viable solution for public internet-accessible applications, but we need to support multiple customers in their intranet, and each one typically requires multiple environments for the application (acceptance, production, etc.). Maintaining dozens of different packages of the AIR application to support all these customer environments clearly is not the solution. Neither we want to force thousands of different users to enter and maintain the correct server location in their local preferences.
So, we thought to use a badge hosted in the back-end application to run the local AIR application: using the underlying API, we could activate the application specifying also the network location of the back-end services. We could also rely on the badge to install the application (and the AIR runtime if necessary)… however, application packaged as native installers cannot be installed, upgraded, or launched by the badge API (and we need to package ours as native to use native processes).
We also noticed that multiple versions of an AIR application cannot be installed side-by-side in a client machine, and that the installation and upgrade of the application can be performed only when the local user has administrative rights on the machine (using standard or native packages), forcing us to rely on external software distribution systems in some customer scenarios (introducing additional complexities in the release cycle).
At this point, in our opinion the standard deployment strategies of Adobe AIR applications are unfit for enterprise environments. In the enterprise world, many of the applications have migrated to a completely browser-based solution, while others enhanced their client layer to comply with the requirements, for example installing only a thin portion of the client code and allowing to connect to multiple server versions/environments with it (e.g. the SAP GUI universal client). Without smarter deployment and distribution tools, AIR applications currently are a step back compared to web applications in terms of manageability.
So, we are trying to develop a solution to address these problems, with some concepts similar to JStart: install on the client machine a launcher application capable of being activated from a web page, dynamically locate, download and run the actual client bytecode, transparently enforce client software updates, and supporting multiple applications (and multiple versions of the same application). However, we are facing many technical problems due to internal architecture of AIR and we already spent a considerable amount of effort trying to find a solution. We are now thinking to return on the choice of AIR, going back to Flex.
What is the position of Adobe on this argument? Is Adobe aware of these issues and are there any plans on this topic? Any advice?
Thank you in advance

For those following along, Oliver Goldman will be answering this post in future articles on his blog.
Many great comments and questions here. I’m working on some follow-up posts to address these; nothing I could cram into this comment field would really do your query justice. - Oliver Goldman
Pursuit of Simplicity
Chris

How to deploy a secured ADF 11g application to WebLogic 10.3 server?

Hi,
I have just enabled security in our ADF 11g application, as descripbed in [chapter 29|http://download.oracle.com/docs/cd/E12839_01/web.1111/b31974/adding_security.htm#insertedID0] of the Fusion Developer's Guide. It works fine in the embedded WebLogic server of JDeveloper.
Now I'm trying to deploy to our WebLogic 10.3 server, which runs in production mode. I'm running into all sorts of problems. The WebLogic console seems to have hundreds of security related pages, I don't know which one I should use, let alone how to use it. The Fusion Developer's Guide doesn't cover deployment to a production server:
>
When the target server is configured for production mode, you typically handle the migration task outside of JDeveloper using tools like Oracle Enterprise Manager. For details about using tools outside of JDeveloper to migrate the policy store to the domain-level in a production environment, see the [Oracle Fusion Middleware Security Guide|http://download.oracle.com/docs/cd/E12839_01/core.1111/e10043/toc.htm].
>
However, this guide is of very little help to me. I found [chapter 7|http://download.oracle.com/docs/cd/E12839_01/core.1111/e10043/addlsecfea.htm#insertedID0], which says "The recommended tool is Fusion Middleware Control." I have no idea what "Fusion Middleware Control" is, where to get it and how to use it.
Long story short: I'm totally lost. I'm looking for a step by step guide on how to deploy a secured ADF 11g application to a WegLogic 10.3 server that is running in production mode. Any help is highly appreciated.

Ok, I found a [very helpful blog post |http://andrejusb.blogspot.com/2009/01/practical-adf-security-deployment-on.html] by [Andrejus Baranovski|http://www.blogger.com/profile/04468230464412457426]. I wish Oracle's documentation was as clear as this...
The blog post refers to an article by Steve Muench, called [Simplified ADF 11g Application Credential and Policy Migration to Standalone WebLogic Servers|http://www.oracle.com/technology/products/jdev/tips/muench/credmig111100/index.html]. This article presents an Ant script that migrates policies from JDeveloper to WebLogic, using some PFM. (See the last definition here.)
The problem is that Steve Muench's script assumes that JDeveloper and the standalone WebLogic are on the same machine. However, in a typical environment, such as the one I'm working in currently, this is not the case. In our case the developer stations are Windows machines, while our WebLogic server runs on a HP-UX machine. So the question is: how to perform this migration between two machines with different operating systems?
Regards,
Bart Kummel

Unable to Generate JHeadStart Application in Jdeveloper 10.1.3

Hi,
I migrated forms 6i to web JHeadStart 10.1.2 with JDeveloper 10.1.2,without any problems but when i Opened the same project in JDeveloper 10.1.3 to Generate JHeadStart Application the version
of JDeveloper 10.1.3 was unable to open this project.
I tried do update
JDeveloper 10.1.3 with the Service
Update 2 but still there was no option under TOOLS->PREFERENCES for generating the JHeadStart Application which is present in JDeveloper 10.1.2.
Any suggestion would be a great help..
Thanks,
Kevin

there is a specific JHeadstart forum: JHeadstart
Regards
Grant Ronald

Error in deploying the java studio creator application to tomcat

Hi,
I'm trying to deploy my Sun Java Studio application to Apache Tomcat 5.0.28.
A simple JSF web application built using the creator works fine after deploying the war file under tomcat/weapps directory.
In case of a application with databse connection I'm getting the
" com.sun.rave.web.ui.appbase.ApplicationException: org.apache.jasper.JasperException: org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of class '' for connect URL 'null' "
above error. My application connects to Oracle database using the Oracle Server type provided by the Studio Creator.
I have copied
jstl.jar
standard.jar
to webapps\%app%\WEB-INF\lib
The below url is currently not available ( Page not Found )stated as a solution in most of the querries regarding the deplyment to tomcat.
http://developers.sun.com/prodtech/javatools/jscreator/reference/tips/deploy_to_tomcat.html
Thanks for any help
abhi

I had similar problems.
I used mysql with tomcat and have mysql in my Creator environment as well but still had the driver message you experienced.
I found that simply copying the WAR file into the webapp directory in tomcat caused a faulty deployment (it was creating /etc/tomcat5/localhost/YourProject.xml as a directory, not as a file)
I updated my Projects/MyProject/build.xml to include a deploy target and I manually execute the ant deploy step (having not figured out how to tweak the internal ant within Creator)
Note that this requires two jar files (see comments in the ant definition)
<project name="YourRoster" default="default" basedir=".">
    <description>Builds, tests, and runs the project YourProject.</description>
    <import file="nbproject/build-impl.xml"/>
   <property file="build.properties"/>
   <property name="appdir" value="."/>
   <property name="distdir" value="${appdir}/dist"/>
   <property name="warfile" value="${distdir}/${app}.war"/>
   <property name="builddir" value="${appdir}/build"/>
   <path id="classpath">
      <pathelement location="${servlet.api.jar}"/>
      <pathelement location="${jsp.api.jar}"/>
      <fileset dir="${builddir}/WEB-INF/lib">
         <include name="*.jar"/>
      </fileset>
   </path>
   
   <target name="lrp-init">
      <tstamp/>
      <fail unless="app" message="Run ant -Dapp=... or update 'build.properties'"/>
   </target>
   <target name="deploy-tomcat" depends="dist"
      description="Deploy web application.">
      <echo message="Deploying ${app} ..."/>
      <taskdef name="deploy"
         classname="org.apache.catalina.ant.DeployTask"/>
      <deploy url="${manager.url}" username="${username}"
         password="${password}" path="/${app}"
         war="file:${warfile}"/>
   </target>
   <target name="undeploy-tomcat" depends="lrp-init"
      description="Undeploy web application.">
      <echo message="Undeploying ${app} ..."/>
      <taskdef name="undeploy"
         classname="org.apache.catalina.ant.UndeployTask"/>
      <undeploy url="${manager.url}" username="${username}"
         password="${password}" path="/${app}"/>
   </target>
   
   <target name="try.undeploy-tomcat" depends="lrp-init"
      description="Call the undeploy task (which may fail).">
      <taskdef resource="net/sf/antcontrib/antcontrib.properties"/>
      <trycatch>
         <try>
            <ant target="undeploy-tomcat"/>
         </try>
         <catch/>
      </trycatch>
   </target>
   <target name="redeploy-tomcat" depends="try.undeploy-tomcat,deploy-tomcat"
      description="Undeploy and deploy web application.">
   </target>
</project>In addition, the build.properties...
jsf.dir=/opt/jsf-1_1_01
tomcat.dir=/opt/tomcat5
app=YourProject
username=tomcatAdminUser
password=tomcatPassword
manager.url=http://localhost:8080/manager
servlet.api.jar=${tomcat.dir}/common/lib/servlet-api.jar
jsp.api.jar=${tomcat.dir}/common/lib/jsp-api.jar
jsf.lib.dir=${jsf.dir}/lib
jstl.lib.dir=${tomcat.dir}/webapps/jsp-examples/WEB-INF/lib
commons.lib.dir=${tomcat.dir}/server/lib
jsf.libs=jsf-api.jar,jsf-impl.jar
jstl.libs=jstl.jar,standard.jar
commons.libs=commons-beanutils.jar,commons-digester.jarHope this helps.
...Lyall

Weblogic 92 MP3 Deployment of newer version of application in production

Hi,
I have Weblogic 9.2 MP3. I need to deploy newer version of application in Production (first in QA).
My question is that, can i deploy that newer version of application without stopping the server (after deploy i need to restart, i know) on the server ?
I think it might give the problem because of the same name of the application.
If suppose i am able to deploy the application will it run properly with the environment (means the production or QA).
Please provide me the documentation other then bea official.
Thanks in advance!!!!!!

For those following along, Oliver Goldman will be answering this post in future articles on his blog.
Many great comments and questions here. I’m working on some follow-up posts to address these; nothing I could cram into this comment field would really do your query justice. - Oliver Goldman
Pursuit of Simplicity
Chris

Deploying parts of a JHeadstart application?

Similar Messages

Maybe you are looking for