Issue on Deployment of AXIS framework in PI 7.0 Server.

Hi Experts,
We have a requirement of Using AXIS Framework in Receiver SOAP adapter in PI 7.0.Moreover we need USERNAME token with PasswordDigest.We have deployed aii_af_axisprovider.sda file in PI server with all relevant .jar files.However when we are checking the url http://host:port/XIAxisAdapter/MessageServlet its showing following optional components are missing.
1)XML Security API
2)Apache WSS4J
3)Apache Addressing
However we have used wsdl4j-1.5.1.jar file.We have added entry for wsdl4j-1.5.1.jar in provider.xml as well.However it still showing warning that optional component is missing
Could you please let us know which version we need to deploy for Apache WSS4J in PI server or do we need to do any other configuartion apart from above configuration so that to enable the UserNameToken security with passwordDigest.
Thanks in advance.
Regards
Nilesh.

Hi,
Post the answer for your issue, so that others can have!

Similar Messages

Deployment issue for Axis Framework in PI 7.0 server

Hi Experts,
I have one issue regarding the deployment of AXIS framework for Receiver SOAP adapter in PI 7.0 server.
Moreover i have a requirement to use UserNameToken security with PasswordDigest.
I have deployed aii_af_axisprovider.sda file into PI server with relevant .jar files.
However when i am checking through url http://host:port/XIAxisAdapter/MessageServlet its giving that optional components are missing
1)XMLSecurityAPI
2)Apache WSS4j
3)Apache Addressing
In SAP Note 1039369 its mentioned about to use wss4j-1.5.4.jar,xmlsec-1.4.0.jar,opensaml-1.0.1.jar files.
Now my concern is to enable UserNameToken Security with PasswordDigest which version of Wss4j is required along with xmlsec version and do we need opensaml-1.0.jar file for same requirement.
Is it sufficient if we deploy wss4j-1.5.4.jar and xmlsec-1.3.0.jar to enable the UserName Token secuiry.
Request you all to please confirm the same.
Thanks in advance
Regards
Nilesh

I have the same requirement. Just wanted to know if opensaml-1.0.jar file is required to enable the UserName Token secuiry.

Issue of deploying a fusion Web Application with integrated Weblogic server

Hi,
i'm using Jdev 11.1.1.3.0 to develop a fusion web application, with a model and ViewController Projects.
When i try to deploy this application with the integrated server, i have any issues.
The origin seems to be that it builds an application with 3 profiles. The model application is recognized and deployed as a webapp and not an ADF library as it should be..
[11:00:45 PM] Retrieving existing application information
[11:00:45 PM] Running dependency analysis...
[11:00:45 PM] Deploying 3 profiles...
[11:00:46 PM] Wrote Web Application Module to /home/david/.jdeveloper/system11.1.1.3.37.56.60/o.j2ee/drs/easygestionV2.0/ViewControllerWebApp.war
*[11:00:48 PM] Wrote Web Application Module to /home/david/.jdeveloper/system11.1.1.3.37.56.60/o.j2ee/drs/easygestionV2.0/ModelWebApp.war*
[11:00:48 PM] Wrote Enterprise Application Module to /home/david/.jdeveloper/system11.1.1.3.37.56.60/o.j2ee/drs/easygestionV2.0
[11:00:48 PM] Deploying Application...
<27 déc. 2010 23 h 00 CET> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application easygestionV2.0 is not versioned.>
<JpsDstCredential><setCredential> Impossible de migrer le dossier/la clé d'informations d'identification et de connexion ADF/anonymous#easygesprod. Raison : oracle.security.jps.service.credstore.CredentialAlreadyExistsException: JPS-01007: Les informations d'identification et de connexion avec la correspondance ADF et la clé anonymous#easygesprod existent déjà..
<TrinidadFilter><init>
java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory
     at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:725)
     at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:239)
     at oracle.adfinternal.view.faces.util.rich.ConverterValidatorRegistrationUtils.register(ConverterValidatorRegistrationUtils.java:36)
     at oracle.adfinternal.view.faces.config.rich.RegistrationConfigurator.init(RegistrationConfigurator.java:79)
     at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.init(GlobalConfiguratorImpl.java:400)
     at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.init(RegistrationFilter.java:53)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.init(TrinidadFilterImpl.java:103)
     at org.apache.myfaces.trinidad.webapp.TrinidadFilter.init(TrinidadFilter.java:54)
     at weblogic.servlet.internal.FilterManager$FilterInitAction.run(FilterManager.java:332)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.FilterManager.loadFilter(FilterManager.java:98)
     at weblogic.servlet.internal.FilterManager.preloadFilters(FilterManager.java:59)
     at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1867)
     at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
     at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
     at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
     at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
     at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
     at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
How can i fix the model project to be deployed as an ADf library and not a webapp with the integrated weblogic server ? Because with me it doesn't do it by itself.
Thanks a lot for help

duplicate to Issue of deploying a fusion Web Application with integrated Weblogic server

Axis framework deployment in PI 7_1 using JSPM only

Hi everyone,
we are trying to deploy Axis framework in our 7_1 PI server using JSPM only (as seemingly SDM is no longer available). SAP note only describe how to create SDA file which JSPM doesnot read/understand. Is it true or is there any way to make JSPM read SDA files?
We used SAP MAKE utility with NWDS to convert this SDA into SCA file.
The further deployment showed successful in the JSPM logs however the test servlet throws error with axis.jar
Apache-Axis
Error: required component missing java.lang.NoClassDefFoundError: org/apache/axis/AxisEngine : cannot initialize class because prior initialization attempt failed --- looking for org.apache.axis.AxisEngine in com.sap.aii.af.axisproviderlib/axis.jar; see http://ws.apache.org/axis/
Jakarta-Commons Discovery
Found: org.apache.commons.discovery.Resource at /usr/sap/XXX/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/commons-discovery-0.2.jar
Jakarta-Commons Logging
Found: org.apache.commons.logging.Log at /usr/sap/XXX/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib/commons-logging-1.0.4.jar
Number of Missing Components: 1
Status: Error
We checked the SCA contents. axis.jar and AxisEngine.class files are in there. Also, all the jars are indeed aailable in folder usr/sap/XXX/j2ee/cluster/bin/ext/com.sap.aii.af.axisproviderlib/lib.
Am i missing something? Has anyone seen same error or has a working 710 sca file ?
Regards,
GJ

Hi,
Do u find any solition?

Using the Axis Framework in the SOAP Adapter

Hello experts,
I am currenty checking how I can easily manipulate sender and receiver details and how I could get attachments into XI.
I saw in the sap help that it is possible to use the AXIS framework from the SOAP adapter:
http://help.sap.com/saphelp_nw04/helpdata/en/45/a39e244b030063e10000000a11466f/frameset.htm
As usual, the documentation is of the same quality SAP usually provides.
So my first question would be: This is a moduke to be used from the SOAP adapter right? I am asking because they also wirte about the AXIS adapter and its metadata.
In oder to get it working, I created in the NWDStudio a library project, added my libraries (to the root directory) and deployed it via SDM. Deployment is succesful but its not working.
SAPHelp says I should check for a MessageServlet - I ask myself how that could appear suddenly just by packaging some axis libraries...?
I am using for that the ESA box (NW04s SP6) - I was not able to see whether there are some dependencies to the SP - are they?
Thanks for your support!
Helge

Helge,
Axis is outdated and has some issues ..use Apache Soap instead its much better and easy to use.
http://ws.apache.org/soap/
Regards
Ravi

Regarding Error in AXIS framework

Hi Experts,
I have a requirement of using AXIS framework in Receiver SOAP ADAPTER in PI 7.0 server with UsernameToken security with PasswordDigest.
I have deployed all the relevant .jar files in .sda file and entires have been made in provider.xml.
When ever i am testing my scenario i am getting following error in communication channel monitoring
*Axis: error in invocation: java.net.SocketException: Connection timed out:could be due to invalid address*
Also i am using URL as https://XYZ
Could you please let me know is this error is because of invalid URL,username and password or something else is missing in configuration.
Please help me out on this
Thanks in advance
Anku Chopra

Hi Volker,
I am back.
We had some connectivity issues with HTTP and fortunately it got resolved.
Now as we are moving into HTTPS i am getting following error in SMICM
[Thr 2057]   SSL_get_state() returned 0x00001180 "SSLv3 read client certificate A"
[Thr 2057] *** ERROR during SecudeSSL_SessionStart() from SSL_accept()==SSL_ERROR_SSL
[Thr 2057] SecudeSSL_SessionStart: SSL_accept() failed --
secude_error 536875074 (0x20001042) = "received a fatal SSLv3 bad certificate alert message from the peer"
[Thr 2057] >> -
Begin of Secude-SSL Errorstack -
>>
[Thr 2057] WARNING in ssl3_read_bytes: (536875074/0x20001042) received a fatal SSLv3 bad certificate alert message from the peer
[Thr 2057] << -
End of Secude-SSL Errorstack -
[Thr 2057] <<- ERROR: SapSSLSessionStart(sssl_hdl=0x110f4fb10)==SSSLERR_SSL_ACCEPT
[Thr 2057] *** ERROR => IcmConnInitServerSSL: SapSSLSessionStart returned (-56): SSSLERR_SSL_ACCEPT [icxxconn_mt. 1777]
[Thr 1286] <<- ERROR: SapSSLSessionStart(sssl_hdl=0x110f4fb50)==SSSLERR_SERVER_CERT_MISMATCH
[Thr 1286] *** ERROR => IcmConnInitClientSSL: SapSSLSessionStart failed (-30): SSSLERR_SERVER_CERT_MISMATCH [icxxconn
[[Thr 2828] <<- ERROR: SapSSLSessionStart(sssl_hdl=0x110f4fb50)==SSSLERR_SERVER_CERT_MISMATCH
[Thr 2828] *** ERROR => IcmConnInitClientSSL: SapSSLSessionStart failed (-30): SSSLERR_SERVER_CERT_MISMATCH [icxxconn
[Thr 772] <<- ERROR: SapSSLSessionStart(sssl_hdl=0x110f52770)==SSSLERR_SERVER_CERT_MISMATCH
[Thr 772] *** ERROR => IcmConnInitClientSSL: SapSSLSessionStart failed (-30): SSSLERR_SERVER_CERT_MISMATCH [icxxconn_
[Thr 2057]   SSL_get_state() returned 0x00001180 "SSLv3 read client certificate A"
[Thr 2057] *** ERROR during SecudeSSL_SessionStart() from SSL_accept()==SSL_ERROR_SSL
[Thr 2057] SecudeSSL_SessionStart: SSL_accept() failed --
secude_error 536875074 (0x20001042) = "received a fatal SSLv3 bad certificate alert message from the peer"
[Thr 2057] >> -
Begin of Secude-SSL Errorstack -
>>
[Thr 2057] WARNING in ssl3_read_bytes: (536875074/0x20001042) received a fatal SSLv3 bad certificate alert message from the peer
[Thr 2057] << -
End of Secude-SSL Errorstack -
[Thr 2057]   SSL NI-sock: local=10.120.58.115:44300 peer=10.120.58.115:40671
[Thr 2057] <<- ERROR: SapSSLSessionStart(sssl_hdl=0x110f4fe70)==SSSLERR_SSL_ACCEPT
[Thr 2057] *** ERROR => IcmConnInitServerSSL: SapSSLSessionStart returned (-56): SSSLERR_SSL_ACCEPT [icxxconn_mt. 1777]
Moreover do we need to create any RFC destination in sm59 for HTTP Connections to External Server to enable HTTPS.
Please provide your valuable inputs on this.
Thanks
Anku chopra

AXIS framework in SOAP adapter

Hi,
I am working on PI 7.1. I need to understand about the use of AXIS framework in the SOAP adapter.
Please throw some light on the what exactly is AXIS framework and why is it used while configuring the SOAP adapter.
Also suggest scenarios where AXIS framework is used.
Ihave gone through the SAP help documents and the following link already, but am unable to get the hang of it:
[http://help.sap.com/saphelp_NW04/helpdata/en/45/a4f8bbdfdc0d36e10000000a114a6b/content.htm]
How Tou2026 Set http-Header Parameters using the Axis Framework
[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b092777b-ee47-2a10-17b3-c5f59380957f]
Kindly Help

Hi Yashaswee,
Once you create the SDA archive ( SAP Note 1028961 - How to prepare axisproviderlib.sda for Adapter Framework) you have to deploy it on the J2EE engine of PI.
To check it is correctly deployed or not use the following URL:
http://<systemhost>:<systemport>/XIAxisAdapter/MessageServlet
You will see a screen like this:
An useful case that used the AXIS Framework in the SOAP Adapter to store cookie values is the blog post of Prabhat Sharma:
http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/08/02/pidoc-integration-between-non-sap-system-and-sfsf-bizx--part-i
Regards.
Rodrigo.

Getting Duplicate Object existing issue while deploying the BIAR file

Hi All,
We are trying to deploy BIAR File with XI R2 Command tool InstallEntSdkWrapper. But we are getting Duplicate Object exixting issue while deploying the BIAR file.
Error Message:
[report] [InstallEntSdkWrapper.main] Connecting to CMS plmdevapp31:6400 as administrator
   [report] [InstallEntSdkWrapper.CmsImportFile] Exception: An error occurred at the server :
   [report] Failed to commit objects to server : Duplicate object name in the same folder.
   [report]
   [report] [InstallEntSdkWrapper.main] BIAR File could not be imported
If we are doing any promition with Import Wizard we have an option to "Overwrite object contents" option to overwite exixting objects. It will very helpful if any one suggest how we can achieve this through InstallEntSdkWrapper.
Unfortunately there is no documentation availabe on InstallEntSdkWrapper.
Cheers!

That's a limitation with the XI Release 2 InstallEntSdkWrapper.jar tool.
Sincerely,
Ted Ueda

Issue with Deploying and calling a BPEL process on ALBPM enterprise server

Hi,
I am trying to put in place a POC using Aqualogic BEA products (using ALBPM 5.7, Enterprise Server 5.7, ALSB 2.6, Weblogic App server 9.2). My goal is to put in place a simple BPEL process (using ALBPM) which would call a webservice exposed through ALSB. This BPEL process is initiated by a wrapper BPMN process calling the BPEL process through fuego code.
Though we are able to do the above on a standalone ALBPM studio, When we try to deploy the exported BPM project on the enterprise server and access it through the hiper workspace portal we are getting the following error in the BPM Process Administrator Log of the Engine.
A component failed while executing activity '/Process#Default-1.0/Global' (BP-method Global). Details: The task could not be successfully executed. Reason: 'fuego.connector.ConnectorException: The configuration name [ProcessService] and type [Web Service] is not defined. Detail:The connector must be configured in the appropiate context. '. Caused by: The configuration name [ProcessService] and type [Web Service] is not defined. Detail:The connector must be configured in the appropiate context. fuego.lang.ComponentExecutionException: The task could not be successfully executed. Reason: 'fuego.connector.ConnectorException: The configuration name [ProcessService] and type [Web Service] is not defined. Detail:The connector must be configured in the appropiate context. '. at fuego.server.execution.EngineExecutionContext.invokeMethodAsCil(EngineExecutionContext.java:916) at fuego.server.execution.EngineExecutionContext.runCil(EngineExecutionContext.java:1068) at fuego.server.execution.TaskExecution.invoke(TaskExecution.java:389) at fuego.server.execution.GlobalTaskExecution.invoke(GlobalTaskExecution.java:106) at fuego.server.execution.TaskExecution.executeCIL(TaskExecution.java:481) at fuego.server.execution.TaskExecution.executeTask(TaskExecution.java:655) at fuego.server.execution.TaskExecution.executeTask(TaskExecution.java:616) at fuego.server.execution.TaskExecution.executeTask(TaskExecution.java:442) at fuego.server.execution.GlobalTaskExecution.executeGlobalCIL(GlobalTaskExecution.java:164) at fuego.server.execution.GlobalTaskExecution.executeGlobalCIL(GlobalTaskExecution.java:142) at fuego.server.execution.Global.execute(Global.java:81) at fuego.server.AbstractProcessBean$38.execute(AbstractProcessBean.java:2496) at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:290) at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:462) at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:540) at fuego.transaction.TransactionAction.start(TransactionAction.java:213) at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:117) at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66) at fuego.server.AbstractProcessBean.runGlobalActivity(AbstractProcessBean.java:2491) at fuego.ejbengine.EJBProcessControlAdapter.runGlobalActivity(EJBProcessControlAdapter.java:386) at fuego.ejbengine.EJBProcessControlAdapter_hu750h_EOImpl.runGlobalActivity(EJBProcessControlAdapter_hu750h_EOImpl.java:2877) at fuego.ejbengine.EJBProcessControlAdapter_hu750h_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174) at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:335) at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252) at fuego.ejbengine.EJBProcessControlAdapter_hu750h_EOImpl_921_WLStub.runGlobalActivity(Unknown Source) 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 fuego.papi.impl.AbstractProcessControlHandler.invokeInternal(AbstractProcessControlHandler.java:48) at fuego.papi.impl.j2ee.EJBProcessControlHandler.doInvoke(EJBProcessControlHandler.java:111) at fuego.papi.impl.j2ee.EJBProcessControlHandler.invoke(EJBProcessControlHandler.java:66) at $Proxy77.runGlobalActivity(Unknown Source) 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 fuego.lang.JavaClass.invokeMethod(JavaClass.java:1478) at fuego.lang.JavaObject.invoke(JavaObject.java:185) at fuego.papi.impl.j2ee.EJBExecution.next(EJBExecution.java:200) at fuego.portal.wapi.InteractiveExecution.process(InteractiveExecution.java:157) at fuego.portal.wapi.WebInteractiveExecution.process(WebInteractiveExecution.java:54) at fuego.portal.wapi.InteractiveExecution.process(InteractiveExecution.java:200) at fuego.portal.servlet.ExecutionDispatcher.runGlobalActivity(ExecutionDispatcher.java:659) at fuego.portal.servlet.ExecutionDispatcher.processRequest(ExecutionDispatcher.java:144) at fuego.portal.servlet.ExecutionDispatcher.doPost(ExecutionDispatcher.java:105) at javax.servlet.http.HttpServlet.service(HttpServlet.java:763) at fuego.portal.servlet.AuthenticatedWamServlet.service(AuthenticatedWamServlet.java:1049) at fuego.portal.servlet.SingleThreadPerSession.service(SingleThreadPerSession.java:73) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:223) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at fuego.servlet.multipart.BaseMultipartFilter.doFilter(BaseMultipartFilter.java:57) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3243) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2003) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1909) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:181) Caused by: fuego.connector.ConnectorException: The configuration name [ProcessService] and type [Web Service] is not defined. Detail:The connector must be configured in the appropiate context. at fuego.connector.ConnectorException.connectorNotFound(ConnectorException.java:55) at fuego.connector.ConnectorService.getConnectorInterface(ConnectorService.java:586) at fuego.connector.ConnectorTransaction.getConnectorInterface(ConnectorTransaction.java:618) at fuego.connector.ConnectorTransaction.getResource(ConnectorTransaction.java:254) at fuego.soaptype.WSConfiguration.getInstance(WSConfiguration.java:55) at fuego.soaptype.Endpoint.create(Endpoint.java:42) at fuego.soaptype.WebServiceInstantiator.instantiate(WebServiceInstantiator.java:58) at fuego.component.Component.instantiateDynamic(Component.java:123) at CapGemini.Process.Default_1_0.Instance.CIL_callBPEL(Instance.java:241) at CapGemini.Process.Default_1_0.Instance.CIL_callBPEL(Instance.java:307) 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 fuego.server.execution.EngineExecutionContext.invokeMethodAsCil(EngineExecutionContext.java:907) ... 64 more
Two things here that might help to understand the problem better :
1) As I understand the error is due to some issue while calling the BPEL process from the Fuego code.
The Fuego code which call's the BPEL from the BPMN process is as follows :
helloResponse as String = "someoutput"
helloRequest as String = "someinput"
sessionid as String
// Starting a Session.
// In case you are testing this in the Studio,
// the password must be the same as the user
startSession BPELWSDL.ProcessServiceListenerWSDL.ProcessService
using user = "test",
password = "test"
returning sessionid = result
// createTest is the name of the operation
// in the exposed process.
// In this case the process "ExposedProcess"
// has a web service operation
// called "createTest" that is a "Process Creation" type
// and uses the Begin activity's argument set
callHello BPELWSDL.ProcessServiceListenerWSDL.ProcessService
using sessionId = sessionid,
arg1 = helloRequest
returning helloResponse = result
// Closing the session
discardSession BPELWSDL.ProcessServiceListenerWSDL.ProcessService
using sessionId = sessionid
display "The BPEL's response : " + helloResponse
2) Further, I had catalogued the BPEL's wsdl to the location http://localhost:9000/fuegoServices/ws/ProcessServiceListener?WSDL while running the same in Studio, but while deploying on the enterprise server , I made this point to http://localhost:7001/fuegoServices/ws/ProcessServiceListener?WSDL Is this correct ?
Any thought on this issue would be appreciated.
Regards
Deepak

Hi Deepak,
We are also facing a similar problem, while accessing an external webservice from a BPM process.
Were you able to resolve this issue.
If so, Could you please let us know the procedure that you followed to resolve the issue.
Thanks in Advance,
Krishnaveni.

Any one knows how to use Axis Framework in the SOAP Adapter Modules

How to use Axis Framework in the SOAP Adapter?
How to add custom handler modules?
http://help.sap.com/saphelp_nw04/helpdata/en/45/a4f8bbdfdc0d36e10000000a114a6b/frameset.htm
I went through the above link on help.sap.com. But still could not create a working example.
I have created a wc on some 3ed party app server using apaches axis. I am trying to call that web service from XI using SOAP receiver? I need to add some security related headers to the soap message, SO I am trying to use a handler. I want to know how to configure this handler in SOAP axis adapter module.
Thank you
Moni

Ravi ,
I am trying exactly the same. Hers is the scenario.
ABAP Proxy --> PI (7.0) SP 12 ---> WebService.
Since This is service is secured, means it is using OASIS web servie securyty user name token,
I am trying to use AXIS adapter. and I want to configure HandlerBean in which I want to use apache wss4j api to add the userNameToken. I am looking for some documentation on this.
I need to add SOAP action element too as I can not configure this one on the communication channel.
Thanks for any inputs in this regard.
Moni

Issue after deploying war file???

We are moving from a windows box to a unix box...
We had installed jdeveloper - jdev11113install.exe (along with weblogic server and adf libraries) earlier version on the windows box and deployed a ADF application war file on that box which worked fine.
Now i have installed jdevloper -jdev11115install.jar (along with weblogic server and adf libraries) a newer version. Now if i deploy my adf war file on this weblogic server its not fully functional. I have some bars and charts which dont load on one tab but loads on the other.
Here are my logs :
AdminServer-Diagnostic .log
[2011-05-13T00:59:05.835-07:00] [AdminServer] [WARNING] [J2EE JMX-46041] [oracle.as.jmx.framework.MessageLocalizationHelper] [tid: JMX FRAMEWORK Domain Runtime MBeanServer pooling thread] [userId: <anonymous>] [ecid: 0000IzcNPGiEGRG5yz_AiW1DnEIq000002,0] The resource for bundle "oracle.jrf.i18n.MBeanMessageBundle" with key "oracle.jrf.JRFServiceMBean.checkIfJRFAppliedOnMutipleTargets" cannot be found.
[2011-05-13T01:00:11.288-07:00] [AdminServer] [ERROR] [] [org.apache.beehive.netui.pageflow.internal.AdapterManager] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000IzcNfGTEGRG5yz_AiW1DnEIq000003,0] [APP: consoleapp] ServletContainerAdapter manager not initialized correctly.
[2011-05-13T01:14:04.821-07:00] [AdminServer] [NOTIFICATION] [] [oracle.mds] [tid: [STANDBY].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000015,0] [APP: STUsageApp] "Metadata Services: Metadata archive (MAR) not found."
[2011-05-13T01:14:05.208-07:00] [AdminServer] [NOTIFICATION] [] [oracle.security.jps.wls.util.JpsWlsUtil] [tid: [STANDBY].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000015,0] [APP: STUsageApp] JPS-00126
[2011-05-13T01:15:17.280-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.connection.ConnectionsMXBeanImpl] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000001a,0] [APP: STUsageApp] Registering Connection Runtime MBean
[2011-05-13T01:15:19.989-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.connection.ADFConnectionLifeCycleCallBack] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000001a,0] [APP: STUsageApp] Registered the ADF connection MBean for application STUsageApp
[2011-05-13T01:15:26.200-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.config.ADFConfigLifeCycleCallBack] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000001a,0] [APP: STUsageApp] ADF config mbean registered for STUsageApp.
[2011-05-13T01:17:22.266-07:00] [AdminServer] [NOTIFICATION] [] [oracle.mds] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000027,0] [APP: STUsageApp] MBean: oracle.mds.lcm:name=MDSAppRuntime,type=MDSAppRuntime,Application=STUsageApp already exists
[2011-05-13T01:17:22.275-07:00] [AdminServer] [NOTIFICATION] [] [oracle.mds] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000027,0] [APP: STUsageApp] MBean: oracle.mds.lcm:name=MDSAppRuntime,type=MDSAppRuntime,Application=STUsageApp deregistered
[2011-05-13T01:17:22.278-07:00] [AdminServer] [NOTIFICATION] [] [oracle.mds] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000027,0] [APP: STUsageApp] "Metadata Services: Metadata archive (MAR) not found."
[2011-05-13T01:17:42.347-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.connection.ConnectionsMXBeanImpl] [tid: [STANDBY].ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000029,0] [APP: STUsageApp] Registering Connection Runtime MBean
[2011-05-13T01:17:42.598-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.connection.ADFConnectionLifeCycleCallBack] [tid: [STANDBY].ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000029,0] [APP: STUsageApp] Registered the ADF connection MBean for application STUsageApp
[2011-05-13T01:17:46.568-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.config.ADFConfigLifeCycleCallBack] [tid: [STANDBY].ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000029,0] [APP: STUsageApp] ADF config mbean registered for STUsageApp.
[2011-05-13T01:20:34.868-07:00] [AdminServer] [NOTIFICATION] [] [oracle.mds] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000038,0] [APP: STUsageApp] "Metadata Services: Metadata archive (MAR) not found."
[2011-05-13T01:20:35.142-07:00] [AdminServer] [NOTIFICATION] [] [oracle.security.jps.wls.util.JpsWlsUtil] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000038,0] [APP: STUsageApp] JPS-00126
[2011-05-13T01:21:07.963-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.connection.ConnectionsMXBeanImpl] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000003c,0] [APP: STUsageApp] Registering Connection Runtime MBean
[2011-05-13T01:21:08.177-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.connection.ADFConnectionLifeCycleCallBack] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000003c,0] [APP: STUsageApp] Registered the ADF connection MBean for application STUsageApp
[2011-05-13T01:21:11.460-07:00] [AdminServer] [NOTIFICATION] [] [oracle.adf.mbean.share.config.ADFConfigLifeCycleCallBack] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000003c,0] [APP: STUsageApp] ADF config mbean registered for STUsageApp.
[2011-05-13T01:23:52.056-07:00] [AdminServer] [NOTIFICATION] [] [oracle.jbo.uicli.mom.CpxUtils$Visitor] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000004a,0] [APP: STUsageApp] zip:/usr/Oracle/Middleware/user_projects/domains/base_domain/servers/AdminServer/tmp/_WL_user/STUsageApp/aszvbi/war/WEB-INF/lib/_wl_cls_gen.jar!/st/view/DataBindings.cpx
[2011-05-13T01:23:53.108-07:00] [AdminServer] [NOTIFICATION] [ADFC-54008] [oracle.adfinternal.controller.faces.lifecycle.JSFLifecycleImpl] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000004a,0] [APP: STUsageApp] ADFc: Initializing ADF Page Lifecycle for the JSF environment, LifecycleContextBuilder is 'oracle.adfinternal.controller.application.model.JSFDataBindingLifecycleContextBuilder'.
[2011-05-13T01:23:58.753-07:00] [AdminServer] [WARNING] [] [oracle.adf.share.jndi.ReferenceStoreHelper] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000004c,0] [APP: STUsageApp] Incomplete connection reference object for connection:oc
[2011-05-13T01:25:08.181-07:00] [AdminServer] [WARNING] [] [org.apache.myfaces.trinidad.webapp.ResourceServlet] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-00000000000000d2,0] [APP: STUsageApp] ResourceServlet._setHeaders(): Content type for /bi/jsLibs/engine_20110409.swf is NULL![[
Cause: Unknown file extension
]]

basedomain.log
n.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: javax.naming.NameAlreadyBoundException: AdsTimerManager is already bound; remaining name 'app/webapp/STUsage-ViewController-context-root/15580269/comp/env/tm'
     at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:357)
     at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:317)
     at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:324)
     at weblogic.jndi.internal.WLEventContextImpl.bind(WLEventContextImpl.java:277)
     at weblogic.deployment.BaseEnvironmentBuilder.addTimerManager(BaseEnvironmentBuilder.java:843)
     at weblogic.deployment.EnvironmentBuilder.addResourceReferences(EnvironmentBuilder.java:164)
     at weblogic.servlet.internal.CompEnv.activate(CompEnv.java:138)
     at weblogic.servlet.internal.WebAppServletContext.activate(WebAppServletContext.java:3144)
     at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1493)
     at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:438)
     at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:375)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:95)
     at weblogic.application.internal.flow.ScopedModuleDriver.activate(ScopedModuleDriver.java:194)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:541)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:175)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:167)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:140)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<13-May-2011 1:17:50 o'clock AM PDT> <Error> <Deployer> <server_name> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000002c> <1305274670833> <BEA-149202> <Encountered an exception while attempting to commit the 7 task for the application 'STUsageApp'.>
####<13-May-2011 1:17:50 o'clock AM PDT> <Warning> <Deployer> <server_name> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000002f> <1305274670836> <BEA-149004> <Failures were detected while initiating start task for application 'STUsageApp'.>
####<13-May-2011 1:17:50 o'clock AM PDT> <Warning> <Deployer> <server_name> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-000000000000002f> <1305274670837> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Could not setup environment
     at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1495)
     at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:438)
     at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:375)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:95)
     at weblogic.application.internal.flow.ScopedModuleDriver.activate(ScopedModuleDriver.java:194)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:541)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:175)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:167)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:140)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: javax.naming.NameAlreadyBoundException: AdsTimerManager is already bound; remaining name 'app/webapp/STUsage-ViewController-context-root/15580269/comp/env/tm'
     at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:357)
     at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:317)
     at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:324)
     at weblogic.jndi.internal.WLEventContextImpl.bind(WLEventContextImpl.java:277)
     at weblogic.deployment.BaseEnvironmentBuilder.addTimerManager(BaseEnvironmentBuilder.java:843)
     at weblogic.deployment.EnvironmentBuilder.addResourceReferences(EnvironmentBuilder.java:164)
     at weblogic.servlet.internal.CompEnv.activate(CompEnv.java:138)
     at weblogic.servlet.internal.WebAppServletContext.activate(WebAppServletContext.java:3144)
     at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1493)
     at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:438)
     at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:375)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:95)
     at weblogic.application.internal.flow.ScopedModuleDriver.activate(ScopedModuleDriver.java:194)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:541)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:175)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:167)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:140)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<13-May-2011 1:18:32 o'clock AM PDT> <Warning> <netuix> <server_name> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000030> <1305274712736> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=AppDeploymentsControlPage.>
####<13-May-2011 1:19:47 o'clock AM PDT> <Warning> <Socket> <server_name> <AdminServer> <ExecuteThread: '3' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000011> <1305274787906> <BEA-000450> <Socket 21 internal data record unavailable (probable closure due idle timeout), event received -32>
####<13-May-2011 1:20:34 o'clock AM PDT> <Warning> <J2EE> <server_name> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000038> <1305274834453> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application STUsageApp is not versioned.>
####<13-May-2011 1:21:22 o'clock AM PDT> <Notice> <HTTP> <server_name> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <ed56844b40a119ce:1ebfa2f5:12fe85d6867:-8000-0000000000000042> <1305274882683> <BEA-101352> <There are no active sessions. The webapp module STUsage-ViewController-context-root of application STUsageApp is ready to go into admin mode.>

AXIS Framework in PI 7.1

Hi Friends,
I went through a number of forums to understand AXIS Framework in SOAP Adapter.
But i am still not able to unserstand the basic concept of AXIS Framework .
In which type of real time scenarios should we go for AXIS framework
What are the advantages of using the AXIS framework and in which cases we should not be using the AXIS framework
Can anybody please throw some light on this
Regards,
Loveena

Hi,
Axis stands for Apache extensible Interaction System. The framework is provided by the Apache Software Foundation. You can use Axis version 1.4 in the SOAP adapter.
Refer these Links, you have complete idea about Axis frame work
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b092777b-ee47-2a10-17b3-c5f59380957f
http://help.sap.com/saphelp_NW04/helpdata/en/45/a4f8bbdfdc0d36e10000000a114a6b/content.htm
and also refer this link
http://help.sap.com/saphelp_nwpi71/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
Hope this help.
Regards,
Suryanarayana
Edited by: rama suryanarayana on Aug 7, 2008 1:19 PM

Axis Framework in SOAP Adapter in PI 7.1

Hi Experts,
I am working on PI 7.1 . I just need to know all that I can about Axis Framework in SOAP Adapter
All inputs are welcome.
Many thanks,
Neha

Hi !
have a look on these links
Using the Axis Framework in the SOAP Adapter
http://help.sap.com/saphelp_NW04/helpdata/en/45/a4f8bbdfdc0d36e10000000a114a6b/content.htm
http://help.sap.com/saphelp_nwpi71/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
Have a look at this Pdf
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b092777b-ee47-2a10-17b3-c5f59380957f
Thanks !
Abhishek

File upload with the SOAP Axis Framework

Hi,
my scenario is as follows:
ERP --> PI --> System A (3rd party application)
ERP sends data (IDoc) to the PI and is mapped there to a xml structure expected by A.
IDoc --> PI --> target xml structure
On A runs a Web service (Axis Framework) with a method uploadFile that expects one parameter (client of A) and the file for the upload has to come as attachment (call.addAttachment).
I imported already the wsdl and can see the message uploadFile in the IR. The Axis Framework is also available already in the SOAP adapter.
So I have
IDoc --> PI --> target xml structure
but want to call
PI --> uploadFile(client) \[with the target xml structure as attachment\]
How can I map the parameter to uploadFile and get the mapped xml structure as attachment?
Thanks and regards
Patrick

Hi,
thanks for your answer. The PayloadSwapBean could be a solution for the problem and I will try to use it.
Here is another (simplified) version of my scenario:
I have one source interface with three data fields
SD1
SD2
SD3
This should get mapped to a target interface with two data fields
TD1
TD2
So if a source message arrives at PI a Message Mapping is called and the message gets mapped to the target structure.
The result of this mapping should get the attachment of a Web service call.
In a sample client for this Web service it looks like:
      Service service = new Service();
      Call call = (Call) service.createCall();
      call.setOperationName(new QName(... "uploadFile"));
      call.addAttachmentPart(...);
The target interface of the Web service is the message uploadFile in an imported wsdl file. This interface has one data field
WSD1
and is independent of the other data fields.
For filling WSD1 another mapping is necessary (or maybe not?).
Regards
Patrick

How to create SDA file for using AXIS Framework in the SOAP Adapter

Hi experts,
I have the following question:
How I can create the SDA file aii_af_axisprovider.sda for using the AXIS Framework in the SOAP Adpater described in http://help.sap.com/saphelp_nw04/helpdata/en/45/a4f8bbdfdc0d36e10000000a114a6b/content.htm ?
I have downloaded the files axis.jar, commons-discovery-0.2.jar, commons-logging-1.0.4.jar, commons-net-1.0.0-dev.jar and wsdl4j-1.5.1.jar. But how to create the SDA file aii_af_axisprovider.sda? Which tool I have to use for this? It is enough to compress these 5 jar-files in the sda file or need I further files with further information (meta information etc.)?
Thanks and best regards
Christopher

Hi Christopher,
Check this discussion if you have not checked already.
Re: NTLM Authentication dosent work with XI ?
Regards,
Ravi

Issue on Deployment of AXIS framework in PI 7.0 Server.

Similar Messages

Maybe you are looking for