Application Deployment Process

Hi,
I am looking for a definition of a standard application deployment process for J2EE servers. Maybe I missed this information in the specifications, if so, please point me to the right chapter.
To become a bit more concrete, I am searching for information on if there is a specification on what happens on deployment/startup, i.e., where the entry points are that objectes of an application are created, hence, if the application can be made aware of being "started" by the application server.
If there is no such general process, maybe someone could help out with specific information on either sun's server or Tomcat.
Thanks.
Stefan

Well, maybe it's in the JSR 88. Unfortunately not accessible at the moment. Thanks for all the other links, they are quite interesting, too.
My general problem is, that I mostly find the typical information on how to use servlets etc. Just, I do not want to start my application after the invokation of a servlet but on deployment time (i.e., when my application gets deployed to and started by the Java Application Server) and wondered, if there is a standard process besides simply loading the applications classes and making the server aware of new URLs.

Similar Messages

Application deployment manager process

Can someone brief me about the ADM in siebel 8.0?
If possible explain how to export LOV's using LOV in siebel 8

The Application Deployment Manager Guide has an introduction to the component.
http://download.oracle.com/docs/cd/B40099_02/books/AppDeployMgr/AppDeployMgrTOC.html
In brief, yes, it will let you migrate LOVs from one environment to another, along with many other non-repository configuration items.
We tried to use it in 7.8, but it was lacking in many places (Hierarchical LOVs were a pain, for one) but I hear things are much improved in 8.
Edited by: mroshaw76 on 15-Mar-2010 08:40

Application Deployment issue in Webdynpro project

Hi,
I have created an sample Webdynpro project which just displays the name. EAR file has been transformed to SCA file using NWPACKTOOL for deploying the application in JSPM.
When i tried to deploy the SCA file i am getting an exception as,
Deployment Items -
     1. Client path 'C:\usr\sap\WP1\SYS\EPS\in\test1.sca'
          Deploy status is 'Aborted'
          Description:'1. Item is skipped because of failed deployment of item 'test.com_test' and because the applied error strategy is OnErrorStop
          2. Contains Aborted deployment component:
test.com_test'.
          SCA : name 'test', vendor 'test.com', location 'local', version '1000.1.0.1.0.20110810105342'
          Contained DCs:
               1.1 : Relative path 'C:\usr\sap\WP1\SYS\EPS\in\test1.sca --> test.sca.ear'
                    Deploy status is 'Aborted'
                    Description:'1. ASJ.dpl_ds.006193 Error while deploying ear file C:\usr\sap\WP1\J00\j2ee\cluster\server0\.\temp\tcbldeploy_controller\archives\56\test1_sca1312954437078\DEPLOYARCHIVES\test.sca.ear; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception while [validating application test.com/test.
     The test.com/test application was processed from [developmentserver] containers, but none of them returned information about deployed components.
     The registered containers in this moment were [BRMS_Content_Archive, z_com.sap.security.policy-configurations, utl_handler, developmentserver, Monitoring Configurator, component.info_handler, servlet_jsp, connector, classification_handler, CTCContainer, JDBCConnector, PortalRuntimeContainer, dbcontentcontainer, scheduler~container, Content Container, src.zip_handler, PCD Content Deployment Handler, ConfigurationsContainer, orpersistence, appclient, JMSConnector, Cluster File System, Cache Configuration Upload, com.sap.security.ume, SCA Composites Container, metamodelrepository, textcontainer, eden_handler, Galaxy_Content_Archive, uddi_handler, MigrationContainer, com.sap.security.login-modules, webservices_container, EJBContainer, dbschemacontainer, MDRContainer, com.sap.security.policy-configurations, app_libraries_container].
     Possible reasons :
     1.Empty or incorrect application, which is not recognized by registered containers.
     2.An AS Java service, which is providing a container, is stopped or not deployed.
     3.The containers, which processed it, are not implemented correctly, because the application was deployed or started initially, but containers didn't return information about deployed components in the application deployment info].'.
                    SDA : name 'test', vendor 'test.com', location 'local', version '2', software type ('J2EE', s
Can some one help me in deploying the SCA file?
Please let me know how to resolve this issue.
Thanks in Advance!!
Regards
MG
Edited by: madhanssmile on Aug 10, 2011 2:34 PM

go to "DC Metadata" "used DC" , and "Properties" in context menu
for all you your components.
problematic component reference probable has check box "deploy time" checked.
remove that reference.
usually only "Build time" check box must be checked. try to do so.

The deployment process seems to die or get stuck, iAS 6 SP3 for Solaris 8?

When I deploy my application in iAS 6 SP3 for Solaris 8 the deployment process seems to die or get stuck. In the shell window i get the messages
iasdeploy for iPlanet Application Server 6.0 SP3
Connected to LDAP server on sstu15.auto.com port 389
iPlanet Application Server is running in international mode
sstu15:null
sstu15:10 kas> deployment action ''J2EEInstallEar'' (/u02/home/iplanet/JAR/SSS.ear) running.
sstu15:10 kas> deployment action ''J2EEInstallEar'' (/u02/home/iplanet/JAR/SSS.ear) running.
After this nothing happens for a really long time.
When starting the deployment I get in the beginning of kas.log two entries
ADMIN-168: kas> deployment get log ''J2EEInstallEar''
GDS-007: finished a registry load
but suddenly the second line disappears and the only message I get is the first entry. I need to break the deployment process and kill the processes manually.
When starting the application server I get two error messages:
Connected to LDAP server on sstu15.auto.com port 389
iPlanet Application Server is running in international mode
Connected to LDAP server on sstu15.auto.com port 389
iPlanet Application Server is running in international mode
iPlanet Administrative Server
Version 6.0 SP3, Build 20010704
Copyright (c) 1996-1997 KIVA Software Corporation.
Copyright (c) 1998-1999 Netscape Communications Corporation.
Copyright (c) 2000-2001 Sun Microsystems, Inc. Some preexisting portions Copyright (c) 2000 Netscape Communications Corp
. All rights reserved.
Use of this software is governed by the terms of the executed license agreement between you and iPlanet E-Commerce Solutions.
[14/Feb/2002 11:02:12:7] error: ADMIN-071: kas> error: failed to either start up or connect to engine ''0'' (CCS0)
[14/Feb/2002 11:03:08:8] error: ADMIN-071: kas> error: failed to either start up or connect to engine ''1'' (CCS0)
I think all processes starts OK, I get one for .kas and one for kas, one for .kxs and one for kxs and finally one for .kjs and one for kjs.
Is someone familiar with this/these problem(s)?

It seems you are deploying a very big application. Try to deploy this application with following command
j2eeappreg <filename>
It should work fine. It was a bug with iasdeploy command in iAS SP3 which had been fixed in iAS SP4.

Exception during application deployment

Hi all,
I'm trying to deploy a wd application from NWDS (NW2004 sp19) and I get an error:
The application references the following jars - com.sap.security.api, com.sap.security.api.ep5, bc.rf.framework_api and bc.util.public_api. I also defined a Sharing Reference - "PORTAL:sap.com/com.sap.km.application".
Full error stacktrace:
06/10/2008 10:20:25 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
[007]Additional log information about the deployment
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7186 - 630]/>
<!NAME[D:\usr\sap\EPT\JC00\SDM\program\log\sdmcl20081006082023.log]/>
<!PATTERN[sdmcl20081006082023.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[Cp1255]/>
<!LOGHEADER[END]/>
Oct 6, 2008 10:20:23 AM Info: -
Starting deployment -
Oct 6, 2008 10:20:23 AM Info: Error handling strategy: OnErrorStop
Oct 6, 2008 10:20:23 AM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Oct 6, 2008 10:20:23 AM Info: Update strategy: UpdateAllVersions
Oct 6, 2008 10:20:23 AM Info: Starting deployment prerequisites:
Oct 6, 2008 10:20:23 AM Info: Loading selected archives...
Oct 6, 2008 10:20:23 AM Info: Loading archive 'D:\usr\sap\EPT\JC00\SDM\program\temp\temp86DepthVisit.ear'
Oct 6, 2008 10:20:24 AM Info: Selected archives successfully loaded.
Oct 6, 2008 10:20:24 AM Info: Actions per selected component:
Oct 6, 2008 10:20:24 AM Info: Update: Selected development component 'DepthVisit'/'local'/'LOKAL'/'0.2008.10.06.10.20.19'/'0' updates currently deployed development component 'DepthVisit'/'local'/'LOKAL'/'0.2008.09.25.15.49.17'/'0'.
Oct 6, 2008 10:20:24 AM Info: Ending deployment prerequisites. All items are correct.
Oct 6, 2008 10:20:24 AM Info: Saved current Engine state.
Oct 6, 2008 10:20:24 AM Info: Starting: Update: Selected development component 'DepthVisit'/'local'/'LOKAL'/'0.2008.10.06.10.20.19'/'0' updates currently deployed development component 'DepthVisit'/'local'/'LOKAL'/'0.2008.09.25.15.49.17'/'0'.
Oct 6, 2008 10:20:24 AM Info: SDA to be deployed: D:\usr\sap\EPT\JC00\SDM\root\origin\local\DepthVisit\LOKAL\0\0.2008.10.06.10.20.19\temp86DepthVisit.ear
Oct 6, 2008 10:20:24 AM Info: Software type of SDA: J2EE
Oct 6, 2008 10:20:24 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 6, 2008 10:20:24 AM Info: Begin of log messages of the target system:
08/10/06 10:20:24 - ***********************************************************
08/10/06 10:20:24 - Start updating EAR file...
08/10/06 10:20:24 - start-up mode is lazy
08/10/06 10:20:24 - EAR file updated successfully for 63ms.
08/10/06 10:20:24 - Start updating...
08/10/06 10:20:24 - EAR file uploaded to server for 79ms.
08/10/06 10:20:24 - ERROR: Not updated. Deploy Service returned ERROR:
 java.rmi.RemoteException: Cannot deploy application local/DepthVisit..
 Reason: Exception during generation of components of application local/DepthVisit in container webdynpro.; nested exception is:
 com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application local/DepthVisit in container webdynpro.
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deployApplicationDuringUpdate(DeployServiceImpl.java:701)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:666)
 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:320)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.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:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
 Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application local/DepthVisit in container webdynpro.
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:612)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
 ... 12 more
 Caused by: java.lang.NullPointerException
 at com.sap.engine.services.webdynpro.util.Procedures.switchio(Procedures.java:40)
 at com.sap.engine.services.webdynpro.ArchiveParser.extractEntry(ArchiveParser.java:127)
 at com.sap.engine.services.webdynpro.ArchiveParser.process(ArchiveParser.java:101)
 at com.sap.engine.services.webdynpro.PApplication.process(PApplication.java:170)
 at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:838)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
 ... 18 more
 For detailed information see the log file of the Deploy Service.
08/10/06 10:20:24 - ***********************************************************
Oct 6, 2008 10:20:24 AM Info: End of log messages of the target system.
Oct 6, 2008 10:20:24 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 6, 2008 10:20:24 AM Error: Aborted: development component 'DepthVisit'/'local'/'LOKAL'/'0.2008.10.06.10.20.19'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application local/DepthVisit..
Reason: Exception during generation of components of application local/DepthVisit in container webdynpro.; nested exception is:
 com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application local/DepthVisit in container webdynpro.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Oct 6, 2008 10:20:24 AM Info: Starting to save the repository
Oct 6, 2008 10:20:25 AM Info: Finished saving the repository
Oct 6, 2008 10:20:25 AM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Oct 6, 2008 10:20:25 AM Error: -
At least one of the Deployments failed -

Hi,
Building the ear file is not the problem.
The deployment fails.
Seems that somehow I dont have those jars on the server.....
Aviad
Edit: I've done a search on the server and all the relevant jars are there, none is missing.
Whats next?
Edited by: Aviad Levy on Oct 6, 2008 4:41 PM

Deployed processes not showing in BPEL Console

I am working on a processes that uses AQ to interface with a Oracle back end application.
It seemed to work fine, but from a certain moment on it didn't pick up any messages that were qeueued. Except for the first instance of the process. Though the monitor showed it waiting for the response, the process had actually received the response and had proceeded with the next step (in which a file was written to a directory, as I could see). Then it stopped. All subsequent processes stopped after queueing an input message.
After stopping and starting the BPEL Process Manager and OC4J container things went from bad to worse. Now none of the deployed processes are visible in the monitor. However, if I look at a previous instance of a process, it does show up on the dashboard.
I've had a look at the application log of the orabpel OC4J application and it shows a lot of errors (of the same sort) since BEPL Process Manager was stopped. Restarting the Application Server didn't help.
This is the error I'm getting:
05/12/19 14:55:19 MessageDrivenHome::run: dequeue FAILED; attempting to re-acquire JMS session for blocking receive
05/12/19 14:55:19 MessageDrivenHome::run: retry_cnt=0 this.dequeue_retry_cnt=0 this.dequeue_retry_interval=60
Does anybody have a clue about what is wrong?

Some more info on the problem:
I took one of the application servers out of the cluster and began working on it in a standalone state.
The Setup, OracleAS Middle Tier with BPEL:
1. The Application server sits on an internal network that has access to the outside world but restricted incoming access.
2. There is an Apache server running mod_proxy that acts as a reverse proxy for all requests to http://workflow/. http://workflow/ connects the requests to http://servername:7797/, where BPEL is running.
This works to get connectivity to the Application Server. We want the WSDL Location to start with http://workflow/ insead of http://servername:7797/ so we can eventually use a clustered load balancing environment.
I found out that the processes are not showing up in the BPEL Dashboard when I change, soapCallbackUrl and soapServerUrl to http://workflow/. They will not show up until I actually navigate to the WSDL file using teh http://workflow beginning. After which they show up in the BPEL Dashboard. However, on a OC4J_BPEL restart they all disappear again.
Everything works if I use the http://servername:7797/ beginning for WSDLs, but this will not work for the overall implementation.
How can I change soapCallbackUrl and soapServerUrl to http://workflow and still use the BPEL Dashboard?

Can deploy process but not workflow (10.1.3.10 beta)

I tried to deploy several of the demo BPEL processes, but each time the process is deployed successfully, but the workflow is not. Fro example OrderApproval.
I tried setting properties in the build.properties file, but apparently to no avail. Also changing them via the project ant properties did not help.
It looks like the payload JSP did not get deployed -- most of the process works, including the workflow bit, as long as one does not try to look into the worklist entry contents (which gives the 404 Not Found error, same as in the 10.1.2 version when the JSP page is not in the proper directory of hw/worklistexpress).
I noticed some strange behavior in the build properties as stored in the project file (OrderApproval.jpr). There are a lot of equivalent ("fromjdev") entries in the oracle.jdeveloper.ant.AntRunConfiguration hash table. Also, each time after I run a deploy, the value for oc4jinstancename is removed and a corresponding <null/> entry shows up in the file. I tried cleaning up redundant fromjdev entries, but it did not help.
Also hard coding the oc4jinstancename attribute to soademo did not help.
Any suggestions on how to fix the build? See below for a log; I added printing of the deploy attributes to the build.xml file.
Apache Ant version 1.6.5 compiled on June 2 2005
Buildfile: C:\JDevSOA10.1.3.10beta\jdev\mywork\demos\OrderApproval\build.xml
Detected Java version: 1.5 in: C:\JDevSOA10.1.3.10beta\jdk\jre
Detected OS: Windows XP
parsing buildfile C:\JDevSOA10.1.3.10beta\jdev\mywork\demos\OrderApproval\build.xml with URI = file:///C:/JDevSOA10.1.3.10beta/jdev/mywork/demos/OrderApproval/build.xml
Project base dir set to: C:\JDevSOA10.1.3.10beta\jdev\mywork\demos\OrderApproval\bpel
Property ${home} has not been set
[property] Loading C:\JDevSOA10.1.3.10beta\jdev\mywork\demos\OrderApproval\bpel\${home}\samples\common.properties
[property] Unable to find property file: C:\JDevSOA10.1.3.10beta\jdev\mywork\demos\OrderApproval\bpel\${home}\samples\common.properties
Build sequence for target(s) `validateTask' is [validateTask]
Complete build sequence is [validateTask, deployTaskForm, loadproperty, compile, deployProcess, all, ]
validateTask:
[echo] --------------------------------------------------------------
[echo] // Validating workflow
[echo] --------------------------------------------------------------
[validateTask] url is file:/C:/JDevSOA10.1.3.10beta/integration/bpm/support/files/WorkflowTaskDefinition.xsd
[validateTask] Validation of workflow task definitions is completed without errors
Build sequence for target(s) `deployProcess' is [deployProcess]
Complete build sequence is [deployProcess, validateTask, deployTaskForm, loadproperty, compile, all, ]
deployProcess:
[echo] --------------------------------------------------------------
[echo] // Deploying bpel process OrderApproval on localhost and port 8888
[echo] --------------------------------------------------------------
[deployProcess] Deploying process C:\JDevSOA10.1.3.10beta\jdev\mywork\demos\OrderApproval\bpel\..\output\bpel_OrderApproval_1.0.jar
[deployProcess] Successfully deployed the process "OrderApproval" on server "localhost" and port "8888"
Build sequence for target(s) `deployTaskForm' is [deployTaskForm]
Complete build sequence is [deployTaskForm, validateTask, loadproperty, compile, deployProcess, all, ]
deployTaskForm:
[echo] --------------------------------------------------------------
[echo] // Deploying workflow form on localhost and port 8888
[echo] --------------------------------------------------------------
[echo] hostname=localhost httpport=8888 rmiport=23791
[echo] platform=oc4j opmnrequestport=23791
[echo] oc4jinstancename= asinstancename=soademo domain=default rev=1.0
BUILD FAILED
C:\JDevSOA10.1.3.10beta\jdev\mywork\demos\OrderApproval\build.xml:52: Error while deploying the form on server "{0}" Error message :
com.evermind.client.orion.AdminCommandException: Could not connect to the remote server. Please check if the server is down or the client is using invalid host, ORMI port or password to connect: Connection refused: connect
at com.evermind.client.orion.Oc4jAdminConsole.createCannotConnectException(Oc4jAdminConsole.java:175)
at com.evermind.client.orion.Oc4jAdminConsole.executeCommand(Oc4jAdminConsole.java:128)
at com.collaxa.cube.ant.taskdefs.DeployForm.deployOC4J(DeployForm.java:612)
at com.collaxa.cube.ant.taskdefs.DeployForm.deployForm(DeployForm.java:521)
at com.collaxa.cube.ant.taskdefs.DeployForm.deployForms(DeployForm.java:780)
at com.collaxa.cube.ant.taskdefs.DeployForm.execute(DeployForm.java:806)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at oracle.jdevimpl.ant.runner.AntLauncher.launch(AntLauncher.java:321)
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:585)
at oracle.jdevimpl.ant.runner.InProcessAntStarter.runAnt(InProcessAntStarter.java:295)
at oracle.jdevimpl.ant.runner.InProcessAntStarter.mav$runAnt(InProcessAntStarter.java)
at oracle.jdevimpl.ant.runner.InProcessAntStarter$1.run(InProcessAntStarter.java:71)
Caused by: javax.naming.CommunicationException: Connection refused: connect [Root exception is java.net.ConnectException: Connection refused: connect]
at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:258)
at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:51)
at com.evermind.client.orion.Oc4jAdminConsole.executeCommand(Oc4jAdminConsole.java:126)
... 20 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:507)
at java.net.Socket.connect(Socket.java:457)
at java.net.Socket.<init>(Socket.java:365)
at java.net.Socket.<init>(Socket.java:207)
at com.evermind.server.rmi.RMIClientConnection.createSocket(RMIClientConnection.java:645)
at oracle.oc4j.rmi.ClientSocketRmiTransport.createNetworkConnection(ClientSocketRmiTransport.java:58)
at oracle.oc4j.rmi.ClientRmiTransport.connectToServer(ClientRmiTransport.java:78)
at oracle.oc4j.rmi.ClientSocketRmiTransport.connectToServer(ClientSocketRmiTransport.java:68)
at com.evermind.server.rmi.RMIClientConnection.connect(RMIClientConnection.java:609)
at com.evermind.server.rmi.RMIClientConnection.sendLookupRequest(RMIClientConnection.java:153)
at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:137)
at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:249)
... 22 more
at com.collaxa.cube.ant.taskdefs.DeployForm.execute(DeployForm.java:818)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at oracle.jdevimpl.ant.runner.AntLauncher.launch(AntLauncher.java:321)
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:585)
at oracle.jdevimpl.ant.runner.InProcessAntStarter.runAnt(InProcessAntStarter.java:295)
at oracle.jdevimpl.ant.runner.InProcessAntStarter.mav$runAnt(InProcessAntStarter.java)
at oracle.jdevimpl.ant.runner.InProcessAntStarter$1.run(InProcessAntStarter.java:71)
Total time: 2 seconds
Snippet from project file:
<hash n="oracle.jdeveloper.ant.AntRunConfiguration">
<url n="buildfileURL" path="build.xml"/>
<value n="outputLevel" v="3"/>
<list n="propertyNames">
<string v="fromjdev"/>
<string v="fromjdev"/>
<string v="fromjdev"/>
<string v="fromjdev"/>
<string v="user"/>
<string v="password"/>
<string v="type"/>
<string v="host"/>
<string v="port"/>
<string v="fromjdev"/>
<string v="fromjdev"/>
<string v="fromjdev"/>
<string v="fromjdev"/>
<string v="asinstancename"/>
<string v="fromjdev"/>
<string v="fromjdev"/>
<string v="fromjdev"/>
<string v="fromjdev"/>
<string v="fromjdev"/>
<string v="opmn.requestport"/>
<string v="admin.user"/>
<string v="platform"/>
<string v="domain"/>
<string v="oc4jinstancename"/>
<string v="hostname"/>
<string v="http.port"/>
<string v="admin.password"/>
<string v="rmi.port"/>
<string v="rev"/>
</list>
<list n="propertyValues">
<string v="true"/>
<string v="true"/>
<string v="true"/>
<string v="true"/>
<string v="oc4jadmin"/>
<string v="welcome1"/>
<string v="oc4j"/>
<string v="localhost"/>
<string v="8888"/>
<string v="true"/>
<string v="true"/>
<string v="true"/>
<string v="23791"/>
<string v="soademo"/>
<string v="true"/>
<string v="true"/>
<string v="true"/>
<string v="true"/>
<string v="true"/>
<string v="23791"/>
<string v="oc4jadmin"/>
<string v="oc4j"/>
<string v="default"/>
<null/>
<string v="localhost"/>
<string v="8888"/>
<string v="welcome1"/>
<string v="23791"/>
<string v="1.0"/>
</list>
<list n="targetList">
<string v="validateTask"/>
<string v="deployProcess"/>
<string v="deployTaskForm"/>
<string v="deployDecisionServices"/>
</list>
</hash>

When I change the rmi ports to 23793 via the project properties and save, they get updated correctly in the .jpr file. However, the deploy still fails, because somehow JDeveloper resets the values back to 23791 (just as it routinely wipes out the oc4jinstancename) and writes them to the .jpr file.
How can I make the new value 'stick'?
I tried changing the port of the LocalBPELApplicationServer from 23791 to 23793 but got:
Error while getting remote MBeanServer for url: ormi://localhost:23793/default:
Error reading application-client descriptor: Error communicating with server: Connection refused: connect; nested exception is:
 javax.naming.CommunicationException: Connection refused: connect [Root exception is java.net.ConnectException: Connection refused: connect]
When I click on the [+] next to the connection I get this:
oracle.oc4j.admin.jmx.shared.exceptions.JMXRuntimeException: Error while getting remote MBeanServer for url: ormi://localhost:23793/default
 at oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.fetchMBeanServerEjbRemote(CoreRemoteMBeanServer.java:499)
 at oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.<init>(CoreRemoteMBeanServer.java:160)
 at oracle.oc4j.admin.jmx.client.RemoteMBeanServer.<init>(RemoteMBeanServer.java:128)
 at oracle.oc4j.admin.jmx.client.RemoteMBeanServer.getMBeanServer(RemoteMBeanServer.java:158)
 at oracle.oc4j.admin.jmx.client.ClientMBeanServerProxyFactory.getMBeanServer(ClientMBeanServerProxyFactory.java:68)
<snip>
And even then, the deploy process still forces the port to 23791.
I restarted the server and JDeveloper, but the problem persists.

Automate the EAR creation and deployment process

Hi,
I am trying to automate the EAR creation and deployment process. I am following this approach - http://www.oracle.com/technetwork/articles/adf/part4-098813.html
In this approach we use pure ANT without OJDeploy. I am able to Create the EAR file but while deploying to weblogic server manually I get the attached error.
Error is - java.lang.ClassNotFoundException: javax.faces.webapp.FacesServlet
I would like to know, Is this the best practise to automate the EAR Creation and Deployment Process? If not, Please provide me some other best approach.
Thanks in Advance.
Regards
Balaji S

Balaji,
I am the author of that article.
At the time I wrote the article, ojdeploy was not working properly - however, the bugs that I noted at the time have been fixed. If I were writing the article today, my strong recommendation would be to use ojdeploy.
If you insist to use the pure ANT (no ojdeploy) approach, I'd debug your issue this way:
1). Generate the EAR file using the deploy option from the application navigator in JDeveloper. Deploy that EAR file to your WLS server and test to ensure it works. A note that if you are creating an ADF app, you must deploy the JRF to WLS first.
2). Once the EAR from JDev is working, use a tool such as WinZip to expand the JDeveloper-generated EAR file and your ANT-generated EAR file. Compare the two. If you find differences, fix the ANT scripts so that they are the same.
John

Webdynpro application deployment failed.

Our development team working on NWDS to develop some webdynpro application, but they are unable to deploy the application on one of portal.
Error Logs
Jul 29, 2011 8:46:28 AM Info: The SDM client uses an old SDM client API.
Jul 29, 2011 8:46:28 AM Info: -
Starting deployment -
Jul 29, 2011 8:46:28 AM Info: Error handling strategy: OnErrorStop
Jul 29, 2011 8:46:28 AM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Jul 29, 2011 8:46:28 AM Info: Update strategy: UpdateAllVersions
Jul 29, 2011 8:46:28 AM Info: Starting deployment prerequisites:
Jul 29, 2011 8:46:28 AM Info: Loading selected archives...
Jul 29, 2011 8:46:28 AM Info: Loading archive 'E:\usr\sap\P4S\JC00\SDM\program\temp\temp33884warnerbros.com~BusPartnerReports.ear'
Jul 29, 2011 8:46:30 AM Info: Selected archives successfully loaded.
Jul 29, 2011 8:46:30 AM Info: Actions per selected component:
Jul 29, 2011 8:46:30 AM Info: Update: Selected development component 'BusPartnerReports'/'warnerbros.com'/'JDE_P4EPPS2_D'/'20110729054247'/'0' updates
currently deployed development component 'BusPartnerReports'/'warnerbros.com'/'JDE_P4EPPS2_D'/'20110728231626'/'0'.
Jul 29, 2011 8:46:30 AM Info: Ending deployment prerequisites. All items are correct.
Jul 29, 2011 8:46:30 AM Info: Saved current Engine state.
Jul 29, 2011 8:46:30 AM Info: Starting: Update: Selected development component 'BusPartnerReports'/'warnerbros.com'/'JDE_P4EPPS2_D'/'20110729054247'/'0'
updates currently deployed development component 'BusPartnerReports'/'warnerbros.com'/'JDE_P4EPPS2_D'/'20110728231626'/'0'.
Jul 29, 2011 8:46:30 AM Info: SDA to be deployed:
E:\usr\sap\P4S\JC00\SDM\root\origin\warnerbros.com\BusPartnerReports\JDE_P4EPPS2_D\0\20110729054247\temp33884warnerbros.com~BusPartnerReports.ear
Jul 29, 2011 8:46:30 AM Info: Software type of SDA: J2EE
Jul 29, 2011 8:46:30 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 29, 2011 8:46:36 AM Info: Begin of log messages of the target system:
11/07/29 08:46:30 - ***********************************************************
11/07/29 08:46:30 - Start updating EAR file...
11/07/29 08:46:30 - start-up mode is lazy
11/07/29 08:46:31 - EAR file updated successfully for 1641ms.
11/07/29 08:46:31 - Start updating...
11/07/29 08:46:36 - EAR file uploaded to server for 4503ms.
11/07/29 08:46:36 - ERROR: Not updated. Deploy Service returned ERROR:
                     java.rmi.RemoteException: Error occurred while updating ear file ./temp/deploy/work/deploying/BusPartnerReports.ear.
                     Reason: Already started operation with application warnerbros.com/BusPartnerReports in the cluster. No other operation with this
application is allowed at the moment.
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:692)
                          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:330)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
                          at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
                          at
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.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:104)
                          at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
                     For detailed information see the log file of the Deploy Service.
11/07/29 08:46:36 - ***********************************************************
Jul 29, 2011 8:46:36 AM Info: End of log messages of the target system.
Jul 29, 2011 8:46:36 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jul 29, 2011 8:46:36 AM Error: Aborted: development component 'BusPartnerReports'/'warnerbros.com'/'JDE_P4EPPS2_D'/'20110729054247'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while updating ear file ./temp/deploy/work/deploying/BusPartnerReports.ear.
Reason: Already started operation with
application warnerbros.com/BusPartnerReports in the cluster. No other operation with this application is allowed at the moment.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Jul 29, 2011 8:46:36 AM Info: Starting to save the repository
Jul 29, 2011 8:46:36 AM Info: Finished saving the repository for 453 ms.
Jul 29, 2011 8:46:36 AM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Jul 29, 2011 8:46:36 AM Error: -
At least one of the Deployments failed
First two time we received different error and got resolved.
Thanks
Goud

Hi,
As per log, You tried to deploy application when someone was accessing it. You need to ensure that noone is using the application before deploying it. In such situation, webdynpro application goes to stopping/red status on server. You can now resolve this issue in two ways:
1. Restart your portal which will reset all application status to active
2. Ask Administrator to use NWA to stop and start application.
First option will always work!
Nitesh

Deployed processes stopped showing up in BPEL console

Hello,
Our BPEL processes stopped picking up business events; BPEL console dashboard is empty. After, restarting oc4j_soa instance on secondary node, BPEL process picked up business events. After few minutes, BPEL process showed in console.
After one day, BPEL processes disappeared from console.
Following is the error message, I see in soa_err*.log on all nodes after the last successful pick up.
Nov 5, 2010 7:18:57 PM org.collaxa.thirdparty.jgroups.blocks.ConnectionTable$Connection run
INFO: exception is java.net.SocketException: Socket closed
Nov 5, 2010 7:18:57 PM org.collaxa.thirdparty.jgroups.blocks.PullPushAdapter run
WARNING: [<null>] channel closed, exception is ChannelClosedException
10/11/05 19:22:28 oracle.oc4j.rmi.ApplicationStoppedException: Application is not in RUNNING state
10/11/05 19:22:28 at com.evermind.server.ejb.AbstractEJBHome.checkRunningState(AbstractEJBHome.java:732)
10/11/05 19:22:28 at com.evermind.server.ejb.AbstractEJBObject.OC4J_startCall(AbstractEJBObject.java:361)
10/11/05 19:22:28 at ServerBean_RemoteProxy_4bin6i8.init(Unknown Source)
10/11/05 19:22:28 at com.collaxa.cube.admin.CXLoaderServlet.init(CXLoaderServlet.java:60)
Also, EM console does not show any web services for ORABPEL application.
What do I need to do make the deployed process show up in BPEL console?
Regards,
Siva

I ran into a BPEL_OC4J_SOAP_Provider error today and it was related to my proxy. The proxy on my local machine with JDeveloper would allow a WSDL with an unqualified name through. For instance, the machine kronos:7779 would validate, compile, and deploy from my machine. But looking up the WSDL on the server would produce the above described error. When I changed the name of the server to kronos.whatever.com:7779 it worked as expected on the server.

Application deployment issue in WLI 8.5

Hello all,
 
I have created an application via a local instance of weblogic workshop 8.1 and would like to deploy the compiled .ear into a weblogic server domain.
 
During the deployment process, I get an error (see bottom of post).
 
However, I attempt to deploy this .ear file into a weblogic integration domain and deployment is a success.
 
 
Could anyone provide me with a reasoning behind why I can deploy on an integration domain, but not on a server domain?
 
 
Is it possible to keep this deployed application in an integration domain and still have it function, even though it was originally meant to be in a server domain?
What is the different between a server domain vs. an integration domain?
 
 
I am using WLI8.5 sp6 and both the integration and server domains are using the same jrockit jdk.
 
 
Thanks
 
Enrico
 
---console error---
 
[Deployer:149233]An unexpected error was encountered during the deployment process.
[Deployer:149033]preparing application AdminPortalapp on sdp
[Deployer:149033]failed application AdminPortalapp on sdp
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application AdminPortalapp on sdp.: [Deployer:149233]An unexpected error was encountered during the deployment process..
 
 
---domain log error---
 
####<Oct 13, 2006 8:50:29 PM EDT> <Notice> <Security> <test-ws1001> <sdp> <Main Thread> <<WLS Kernel>> <> <BEA-090082> <Security initializing using security realm myrealm.>
####<Oct 13, 2006 8:50:30 PM EDT> <Notice> <WebLogicServer> <sams-ws1001> <sdp> <Main Thread> <<WLS Kernel>> <> <BEA-000327> <Starting WebLogic Admin Server "sdp" for domain "sdp.test.com">
####<Oct 13, 2006 8:50:43 PM EDT> <Notice> <WebLogicServer> <test-ws1001> <sdp> <Main Thread> <<WLS Kernel>> <> <BEA-000360> <Server started in RUNNING mode>
####<Oct 13, 2006 8:50:44 PM EDT> <Notice> <WebLogicServer> <test-ws1001> <sdp> <ListenThread.Default> <<WLS Kernel>> <> <BEA-000355> <Thread "ListenThread.Default" listening on port 7001, ip address 192.168.11.214>
####<Oct 13, 2006 9:39:38 PM EDT> <Warning> <Deployer> <test-ws1001> <sdp> <ExecuteThread: '2' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149004> <Failures were detected while initiating Deploy task for application AdminPortalapp.>
####<Oct 13, 2006 9:39:38 PM EDT> <Error> <Deployer> <test-ws1001> <sdp> <ExecuteThread: '2' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149201> <Failed to complete the deployment task with ID 0 for the application AdminPortalapp.
java.lang.Throwable:
 at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2414)
 at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:884)
 at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:592)
 at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:501)
 at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
>
####<Oct 13, 2006 9:42:12 PM EDT> <Warning> <DRS> <test-ws1001> <sdp> <ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-002506> <The current version 1 for DataIdentifier DataIdentifierID: 1 does not match with incoming version 2 for a one-phase update.>
####<Oct 13, 2006 9:42:12 PM EDT> <Warning> <Deployer> <test-ws1001> <sdp> <ExecuteThread: '1' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149004> <Failures were detected while initiating Deploy task for application AdminPortalapp.>
####<Oct 13, 2006 9:42:12 PM EDT> <Error> <Deployer> <test-ws1001> <sdp> <ExecuteThread: '1' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149201> <Failed to complete the deployment task with ID 1 for the application AdminPortalapp.
java.lang.Throwable:
 at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2414)
 at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:884)
 at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:592)
 at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:501)
 at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)

I was able to recreate the issue on a much smaller scale. I've attached the zipped project folder. This is a brand new project file, I did not copy it from my old one. Follow these steps to see what I'm talking about:
1. Unzip the directory and open the lvproj file.
2. Double click on My Installer in the prject window to open the installer properties.
3. Go to Source Files on the left hand side.
4. On the right side of the source files window, you will see a the files in the directory tree. You should see parse.dll listed in the main directory as well as the data directory.
5. Remove the application from the tree by highlighting one of the files and clicking the red X.
6. Add the application back to the [ProgramFilesFolder]\DLL_test directory. You should see all files added correctly (Help.html in the main dir, parse.dll in the data dir).
7. Click OK
8. Re-open the My Installer properties and go back to the Source Files page. Help.html has been replaced by parse.dll in the main dir yet again.
That should be clear enough to reproduce what I'm seeing. Also, go to the Source File Settings page and you should see that when you highlight parse.dll, you can't select the register COM checkbox. It is only available for Application.exe.
You can open DLL_test.lvproj in notepad and go to the installer section to see how it lists FileInfo[2]. It shows the filename as Help.html, but the tag is parse.dll. This doesn't make any sense.
Attachments:
DLL Test.zip ‏15 KB

Adding file to Application deployment content after client deployment

Hi,
I have been testing deploying Visio 2013 via Application deployment and am having troubles with running an uninstall.
After deploying the software successfully to my test client, I needed to make a change to the uninstall process & have added an new file that is now used during an uninstall.
When running the uninstall on my test client, I can see the correct commandline being used; however it fails because the additional file has not been downloaded to the CCMCache folder on the client.
I have run an 'update content' for the distribution type, cleared the clients cache & re-run the uninstall from Software Center. The client redownloads the source files, however it is still missing the new file that it needs.
Checking on the distribution points, I can see the new file referenced in the SCCMContentLib folder.
I tried removing previous revisions from the Application via the console & now when running the uninstall on the client it fails immediately without downloading the source files. Checking AppEnforce.log, it looks like the uninstall is referencing the
old revision of the Application Deployment still (which didn't contain the additional file, and no longer exists in the revision history).
Can anyone point me in the right direction to get this resolved?
And also, what is the correct procedure for updating/adding files to an already deployed application?
Thanks in advance!

If you're confident that the DP contains the new file, try deleting the deployment and re-doing it (not the deployment type - just the deployment to your test collection).
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

AIA deploy Application deployment FAILED...

Dear All,
Please help me with the following. I am getting error as BUILD Failed during "Deploy Application Deployment" while installing AIA(11.1.1.6.0) on windows 2003 Enterprise edition 32 bit.
Exact error is following:
BUILD FAILED
E:\OBI_HOME\AIA_Home\Infrastructure\Install\AID\AIAExecuteDriver.xml:226:Following error occured while executing this line..
E:\OBI_HOME\AIA_Home\Infrastructure\Install\AID\AIAExecuteDriver.xm:62:java.net.MalFormedURLException. Cannot give port name without hostname.
How can I resolve this issue.
Error in details:
Total time: 19 seconds
'choice' is not recognized as an internal or external command,
operable program or batch file.
Retry Deployment Command Return Value Deployment: 255
SYSTEM ROOT: C:\WINDOWS
Deployment Command Deployment: cmd /c set PATH=E:\\OBI_HOME\modules\org.apache.ant_1.7.1\bin;E:\\OBI_HOME\jdk160_24\bin;%PATH%&& set CLASSPATH=.;E:\\OBI_HOME\wlserver_10.3\server\lib\weblogic.jar;E:\\OBI_HOME\AIA_Home\lib\aia.jar;E:\\OBI_HOME\modules\net.sf.antcontrib_1.1.0.0_1-0b2\lib\ant-contrib.jar;E:\\OBI_HOME\AIA_Home\lib\aia-utils.jar;E:\\OBI_HOME\oracle_common\modules\oracle.mds_11.1.1\mdsrt.jar;E:\\OBI_HOME\oracle_common\modules\oracle.jps_11.1.1\jps-ee.jar;E:\\OBI_HOME\oracle_common\modules\oracle.jps_11.1.1\jps-common.jar;E:\\OBI_HOME\oracle_common\modules\oracle.jps_11.1.1\jps-internal.jar;E:\\OBI_HOME\oracle_common\modules\oracle.jps_11.1.1\jps-unsupported-api.jar;E:\\OBI_HOME\oracle_common\modules\oracle.pki_11.1.1\oraclepki.jar;E:\\OBI_HOME\oracle_common\modules\oracle.idm_11.1.1\identitystore.jar;E:\\OBI_HOME\oracle_common\modules\oracle.webservices_11.1.1\oracle.webservices.standalone.client.jar;E:\\OBI_HOME\Oracle_SOA1\soa\modules\oracle.soa.fabric_11.1.1\oracle-soa-client-api.jar;E:\\OBI_HOME\oracle_common\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;E:\\OBI_HOME\Oracle_SOA1\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;E:\\OBI_HOME\oracle_common\modules\oracle.fabriccommon_11.1.1\fabric-common.jar;E:\\OBI_HOME\Oracle_SOA1\soa\modules\oracle.soa.fabric_11.1.1\fabric-runtime.jar;E:\\OBI_HOME\oracle_common\BC4J\jlib\commons-cli-1.0.jar;E:\\OBI_HOME\oracle_common\jlib\commons-cli-1.0.jar;%CLASSPATH%&& set JAVA_HOME=E:\\OBI_HOME\jdk160_24&& set ANT_HOME=E:\\OBI_HOME\modules\org.apache.ant_1.7.1&& set ANT_OPTS=-Xms512M -Xmx1024M -XX:MaxPermSize=512M&& set AIA_HOME=E:\\OBI_HOME\AIA_Home&& set SOA_HOME=E:\\OBI_HOME\Oracle_SOA1&& set MW_HOME=E:\\OBI_HOME&& set ORACLE_HOME=E:\\OBI_HOME\Oracle_SOA1&& set WL_HOME=E:\\OBI_HOME\wlserver_10.3&& set SystemRoot=C:\WINDOWS&& cd /d E:\\OBI_HOME\AIA_Home\Infrastructure\Install\AID&& ant -f E:\\OBI_HOME\AIA_Home\Infrastructure\Install\AID\AIAInstallDriver.xml -DDeploymentPlan=E:\\OBI_HOME\AIA_Home/aia_instances/AIA_TTL\config\FPInstallDP.xml Deployments -DPropertiesFile=E:\\OBI_HOME\AIA_Home/aia_instances/AIA_TTL\config\AIAInstallProperties.xml
E:\OBI_HOME\AIA_Home\aia_instances\AIA_TTL\.configuration\Aid.Properties
Using existing user key file...
Buildfile: E:\OBI_HOME\AIA_Home\Infrastructure\Install\AID\AIAInstallDriver.xml
[AIAXmlProperty] Decipher value does not exist for the key : oer.server.password
Deployments:
[echo] ======================================
[echo] DeploymentPlan file ="E:\\OBI_HOME\AIA_Home/aia_instances/AIA_TTL\config\FPInstallDP.xml"
[echo] ======================================
Deployments:
[echo]
[echo]
[echo]
[echo] Deployment log -- E:\OBI_HOME\AIA_Home\aia_instances\AIA_TTL\logs/FPInstallDP_Deployments_2012-07-19_10-51-16.log
[echo]
[echo]
[echo] === Executing Deployments of E:\\OBI_HOME\AIA_Home/aia_instances/AIA_TTL\config\FPInstallDP.xml===
[echo]
[echo]
[xslt] Processing E:\OBI_HOME\AIA_Home\aia_instances\AIA_TTL\config\FPInstallDP.xml to E:\OBI_HOME\AIA_Home\aia_instances\AIA_TTL\tmp\AIDExecuteDP_temp_228243584.xml
[xslt] Loading stylesheet E:\OBI_HOME\AIA_Home\aia_instances\AIA_TTL\tmp\AIDExtractxsl_temp_1016106937.xsl
[UpdateDeployedComposites] Connecting to: service:jmx:t3://172.28.18.20:7001/jndi/weblogic.management.mbeanservers.domainruntime
BUILD FAILED
E:\OBI_HOME\AIA_Home\Infrastructure\Install\AID\AIAExecuteDriver.xml:226: The following error occurred while executing this line:
E:\OBI_HOME\AIA_Home\Infrastructure\Install\AID\AIAExecuteDriver.xml:62: java.net.MalformedURLException: Cannot give port number without host name
Total time: 19 seconds
'choice' is not recognized as an internal or external command,
operable program or batch file.
Deployment Command Return Value Deployment: 255
Thanks,
Soumya Sekhar Samanta
Edited by: Soumya Sekhar Samanta on Jul 19, 2012 10:58 AM

Is it possible for you to paste the deployment command that was executed for the above failure? You could try doing a manual install. Before executing the FPInstallDP.xml during the manual install add the following jar to your classpath
${MW_HOME}/oracle_common/jlib/commons-cli-1.0.jar.

NPE when starting application deployed to Glassfish

Hi,
When I starting application deployed to glassfish I get the following error:
[#|2012-09-25T15:02:22.209+0200|FINEST|glassfish3.1.2|oracle.adf.share.http.ServletADFContext|_ThreadID=23;_ThreadName=Thread-2;ClassName=oracle.adf.share.http.ServletADFContext;MethodName=resetThreadContext;|Reset thread|#]
[#|2012-09-25T15:02:22.209+0200|CONFIG|glassfish3.1.2|oracle.adf.model.servlet.ADFBindingFilter|_ThreadID=23;_ThreadName=Thread-2;|ADF web request|#]
[#|2012-09-25T15:02:22.210+0200|WARNING|glassfish3.1.2|javax.enterprise.system.container.web.com.sun.enterprise.web|_ThreadID=23;_ThreadName=Thread-2;|StandardWrapperValve[Faces Servlet]: PWC1406: Servlet.service() for servlet Faces Servlet threw exception
java.lang.NullPointerException
at oracle.adfinternal.view.faces.partition.FeatureHandler._startFeaturesChildElement(FeatureHandler.java:178)
at oracle.adfinternal.view.faces.partition.FeatureHandler.startElement(FeatureHandler.java:76)
at org.allcolor.xml.parser.CShaniSaxParser.parseStartTag(CShaniSaxParser.java:1375)
at org.allcolor.xml.parser.CXmlParser.parseSTARTTag(CXmlParser.java:1405)
at org.allcolor.xml.parser.CXmlParser.parse(CXmlParser.java:682)
at org.allcolor.xml.parser.CShaniSaxParser.parse(CShaniSaxParser.java:767)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
at oracle.adfinternal.view.faces.partition.FeatureUtils._parseFeatures(FeatureUtils.java:146)
at oracle.adfinternal.view.faces.partition.FeatureUtils._parseFeatures(FeatureUtils.java:89)
at oracle.adfinternal.view.faces.partition.FeatureUtils.loadFeatures(FeatureUtils.java:48)
at oracle.adfinternal.view.faces.partition.PartitionManager._createPartitionManager(PartitionManager.java:282)
at oracle.adfinternal.view.faces.partition.PartitionManager.init(PartitionManager.java:108)
at oracle.adfinternal.view.faces.config.rich.RegistrationConfigurator.init(RegistrationConfigurator.java:153)
at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.init(GlobalConfiguratorImpl.java:399)
at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.beginRequest(GlobalConfiguratorImpl.java:205)
at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.getExternalContext(GlobalConfiguratorImpl.java:328)
at org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl$CacheRenderKit.<init>(FacesContextFactoryImpl.java:84)
at org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl.getFacesContext(FacesContextFactoryImpl.java:62)
at com.sun.faces.context.InjectionFacesContextFactory.getFacesContext(InjectionFacesContextFactory.java:121)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:498)
at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1550)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:343)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217)
at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:173)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217)
at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:180)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:256)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:217)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:279)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:331)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:231)
at com.sun.enterprise.v3.services.impl.ContainerMapper$AdapterCallable.call(ContainerMapper.java:317)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:860)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:757)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1056)
at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:229)
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
at java.lang.Thread.run(Thread.java:662)
|#]
The application runs fine on weblogic.
I have no idea how to debug this issue.
Few other applications runs fine on glassfish.
I tested on GlassFish Server Open Source Edition 3.1.2.2, windows 64, JDK 1.6.0_24
Best Regards,
Miroslaw

I fixed the problem myself.
My application contained a xml-apis.jar in which SAX parser has been set to non-Oracle implementation, removing this jar fixes the problem.
Miroslaw

Unable to deploy process

Hi,
I am getting below error if I am trying to deploy the process on the application server.I have included property names in my bpel.xml as below to access wsdl which is having http basic authentication
<partnerLinkBinding name="SyStaffService">
<property name="wsdlLocation">SyStaffService.wsdl</property>
<property name="httpUserPassword">CRYPT{LZvxvb0gzLWAzGQiyaP/5Q==}</property>
<property name="httpUserName">schoolmax</property>
</partnerLinkBinding>
[deployProcess] Deploying process C:\jdevstudio10134\jdev\mywork\HT\STAFFREAD\output\bpel_STAFFREAD_1.0.jar
BUILD FAILED
C:\jdevstudio10134\jdev\mywork\HT\STAFFREAD\build.xml:78: A problem occured while connecting to server "localhost" using port "80": bpel_STAFFREAD_1.0.jar failed to deploy. Exception message is: ORABPEL-05215
Error while loading process.
The process domain encountered the following errors while loading the process "STAFFREAD" (revision "1.0"): Failed to read wsdl.
Error happened when reading wsdl at "C:\OracleSOA\bpel\domains\default\tmp\.bpel_STAFFREAD_1.0_d72966d5a88e6f980eedef77a89defc2.tmp\SyStaffService.wsdl", because "Error reading import of file:/C:/OracleSOA/bpel/domains/default/tmp/.bpel_STAFFREAD_1.0_d72966d5a88e6f980eedef77a89defc2.tmp/SyStaffService.wsdl: Failed to read WSDL from http://sazbird:8080/IntegrationServices/SyStaffService?wsdl: HTTP connection error code is 401".
Make sure wsdl exists at that URL and is valid.
If you have installed a patch to the server, please check that the bpelcClasspath domain property includes the patch classes.
at com.collaxa.cube.engine.deployment.CubeProcessHolder.bind(CubeProcessHolder.java:286)
at com.collaxa.cube.engine.deployment.DeploymentManager.deployProcess(DeploymentManager.java:926)
at com.collaxa.cube.engine.deployment.DeploymentManager.deploySuitcase(DeploymentManager.java:792)
at com.collaxa.cube.ejb.impl.BPELDomainManagerBean.deploySuitcase(BPELDomainManagerBean.java:455)
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:585)
at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
at com.evermind.server.ThreadState.runAs(ThreadState.java:693)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
at DomainManagerBean_RemoteProxy_4bin6i8.deploySuitcase(Unknown Source)
at com.oracle.bpel.client.BPELDomainHandle.deploySuitcase(BPELDomainHandle.java:319)
at com.oracle.bpel.client.BPELDomainHandle.deployProcess(BPELDomainHandle.java:341)
at deployHttpClientProcess.jspService(_deployHttpClientProcess.java:376)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:462)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:400)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:414)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
Total time: 1 second
Thanks for your help,
harsha

Balu,
it seems you are trying to deploy example for B2B. Please check your B2B is up, AQ are up and accessible and you can also check your SOA dehydration DB .
You can check some setup and dexample at: http://www.oracle.com/technology/products/integration/b2b/pdf/B2B_TU_001_B2B_BPEL.pdf
-JMehta

Application Deployment Process

Similar Messages

Maybe you are looking for