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?

Similar Messages

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.

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!

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

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.

Error during deploying MDM 7.1 Sp02 bussiness packages in CE7.1 using JSPM

Hello,
I am facing error when i am trying to deploy following MDM sca file in CE7.1 using JSPM
1. BPMDMAPP02_115.sca
2. BPMDMTECH02_115.sca
I have already deployed following SCA file into CE7.1 successfully.
3 .MDMJAVAAPI02_59.sca (deployed success)
is it mandatory that all sca files should be at same path level?currently API is at 59 and App and tech are at 115 .
I am using CE7.1 trail version , i could not find out SDM to deploy sca files,so i am using JSPM to deploy sca files.
Thanks & Regards,
Veeru.

Hi,
Yes, all three should be compatible to MDM server and should be at same patch level.
But i think reason for your deployment error is different.
I found this in SAP note no 1281637
"MDM standard Portal content (iViews) are supported on SAP NetWeaver 2004 and SAP NetWeaver 7.0 (2004s). At this time, there are no plans to migrate the content to be compatible to SAP NetWeaver CE 7.1.
Please Check Note 1281637 - Deployment errors on NW 7.1 CE for MDM portal content
Regards,
Shiv

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

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

Error when using axis framework

Hi.
I created a sync scenario (soap to Jdbc) on PI 7.1
On Sender soap channel i used axis framework for User Token Authentication.
followed the axis faq note and following help.sap link
http://help.sap.com/erp2005_ehp_04/helpdata/EN/45/a4f8bbdfdc0d36e10000000a114a6b/frameset.htm
When i am trying to trigger message from soap client am facing the following error.
Please help............
Error:
<?xml version="1.0" encoding="utf-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<soapenv:Fault>
   <faultcode>soapenv:Server.generalException</faultcode>
   <faultstring>handler is not instantiated; nested exception is:
     org.apache.axis.ConfigurationException: handler is not instantiated
org.apache.axis.ConfigurationException: handler is not instantiated
     at com.sap.aii.adapter.axis.modules.HandlerCore.process(HandlerCore.java:69)
     at com.sap.aii.adapter.axis.modules.HandlerBean.process(HandlerBean.java:75)
     at sun.reflect.GeneratedMethodAccessor517_10002.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
     at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
     at $Proxy2772_10002.process(Unknown Source)
     at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:249)
     at sun.reflect.GeneratedMethodAccessor515_10002.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
     at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
     at $Proxy105_10002.process(Unknown Source)
     at com.sap.aii.adapter.axis.ra.ModuleProcessorEngine.invoke(ModuleProcessorEngine.java:123)
     at com.sap.aii.adapter.axis.web.ServletReceiverCore.doPost(ServletReceiverCore.java:290)
     at com.sap.aii.adapter.axis.web.MessageServlet.doPost(MessageServlet.java:372)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:163)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:82)
     at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:124)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:74)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:425)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
     at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
     at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
     at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
     at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
     at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
     at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
     at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309)
     at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
     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:152)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
</faultstring>
   <detail>
    <ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">hydhtc165182d</ns1:hostname>
   </detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
Edited by: Osman Jabri on Nov 4, 2010 4:24 PM

Osman,
Check out these forum entries:
[Error on SOAP Receiver for Axis; and
[Re: Error in AXIS SOAP Adapter|Re: Error in AXIS SOAP Adapter]
The FAQ has further details as well for your reference: [1039369|https://service.sap.com/sap/support/notes/1039369]
Brad

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

Error while applying LM-tools patch using JSPM

hi all,
I got error while applying LM-Tool patch using JSPM. following is the error log. How can i rectify it. please help.
Mar 29, 2010 12:49:57... Info:
Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info: Statement successf
ully executed: DROP TABLE "BC_MID_TREE"
Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info: Statement successf
ully executed: DROP TABLE "BC_MID_TREE"
Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info: Statement successf
ully executed: CREATE TABLE "BC_MID_TREE"("NODE_ID" RAW(16) NOT NULL, "PARENT_I
D" RAW(16) , "NODE_TYPE" NUMBER(10) DEFAULT 0 NOT NULL, "NAME" NVARCHAR2(30) DE
FAULT ' ' NOT NULL, "TS" TIMESTAMP NOT NULL, "USER_ID" NVARCHAR2(30) )
Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info: Statement successf
ully executed: CREATE TABLE "BC_MID_TREE"("NODE_ID" RAW(16) NOT NULL, "PARENT_I
D" RAW(16) , "NODE_TYPE" NUMBER(10) DEFAULT 0 NOT NULL, "NAME" NVARCHAR2(30) DE
FAULT ' ' NOT NULL, "TS" TIMESTAMP NOT NULL, "USER_ID" NVARCHAR2(30) )
Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info: Statement successf
ully executed: CREATE INDEX "BC_MID_TREE_R" ON "BC_MID_TREE"("PARENT_ID")
Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info: Statement successf
ully executed: CREATE INDEX "BC_MID_TREE_R" ON "BC_MID_TREE"("PARENT_ID")
Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info: Statement successf
ully executed: CREATE UNIQUE INDEX "BC_MID_TREE_U" ON "BC_MID_TREE"("PARENT_ID",
"NAME")
Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info: Statement successf
ully executed: CREATE UNIQUE INDEX "BC_MID_TREE_U" ON "BC_MID_TREE"("PARENT_ID",
"NAME")
Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info: Statement successf
ully executed: ALTER TABLE "BC_MID_TREE" ADD PRIMARY KEY ("NODE_ID") NOT DEFERRA
BLE INITIALLY IMMEDIATE ENABLE VALIDATE
Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info: Statement successf
ully executed: ALTER TABLE "BC_MID_TREE" ADD PRIMARY KEY ("NODE_ID") NOT DEFERRA
BLE INITIALLY IMMEDIATE ENABLE VALIDATE
Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info: Runtime XML of BC_
MID_TREE successfully written
Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info: Runtime XML of BC_
MID_TREE successfully written
Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info: Runtime XML of BC_
MID_TREE successfully written
Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info: Runtime XML of BC_
MID_TREE successfully written
Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info: Next archive objec
t : dbtables/BC_MID_TREE_ITEM.gdbtable
Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info: Next archive objec
t : dbtables/BC_MID_TREE_ITEM.gdbtable
Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info: <<< Analyze table
BC_MID_TREE_ITEM >>>
Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info: <<< Analyze table
BC_MID_TREE_ITEM >>>
Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info: predefined action
is: >>>DROP_CREATE<<<
Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info: predefined action
is: >>>DROP_CREATE<<<
Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info: Action: DROP_CREAT
E
Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info: Action: DROP_CREAT
E
Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info: DROP TABLE "BC_M
ID_TREE_ITEM"
Mar 29, 2010 12:49:57... Info: CREATE TABLE "BC_MID_TREE_ITEM"
Mar 29, 2010 12:49:57... Info: (
Mar 29, 2010 12:49:57... Info: "NODE_ID" RAW(16) NOT NULL,
Mar 29, 2010 12:49:57... Info: "ITEM_ID" RAW(16)
Mar 29, 2010 12:49:57... Info: )
Mar 29, 2010 12:49:57... Info: CREATE INDEX "BC_MID_TREE_ITEM_R" ON "BC_MID_TRE
E_ITEM"
Mar 29, 2010 12:49:57... Info: (
Mar 29, 2010 12:49:57... Info: "ITEM_ID"
Mar 29, 2010 12:49:57... Info: )
Mar 29, 2010 12:49:57... Info: ALTER TABLE "BC_MID_TREE_ITEM"
Mar 29, 2010 12:49:57... Info: ADD PRIMARY KEY ("NODE_ID")
Mar 29, 2010 12:49:57... Info: NOT DEFERRABLE INITIALLY IMMEDIATE ENABLE VALIDAT
E
Mar 29, 2010 12:49:57... Info:
Mar 29, 2010 12:49:57... Info: 12:49:56 2010-03-29 dbs-Info: DROP TABLE "BC_M
ID_TREE_ITEM"
Mar 29, 2010 12:49:57... Info: CREATE TABLE "BC_MID_TREE_ITEM"
Mar 29, 2010 12:49:57... Info: (
Mar 29, 2010 12:49:57... Info: "NODE_ID" RAW(16) NOT NULL,
Mar 29, 2010 12:49:57... Info: "ITEM_ID" RAW(16)
Mar 29, 2010 12:49:57... Info: )
Mar 29, 2010 12:49:57... Info: CREATE INDEX "BC_MID_TREE_ITEM_R" ON "BC_MID_TRE
E_ITEM"
Mar 29, 2010 12:49:57... Info: (
Mar 29, 2010 12:49:57... Info: "ITEM_ID"
Mar 29, 2010 12:49:57... Info: )
Mar 29, 2010 12:49:57... Info: ALTER TABLE "BC_MID_TREE_ITEM"
Mar 29, 2010 12:49:57... Info: ADD PRIMARY KEY ("NODE_ID")
Mar 29, 2010 12:49:57... Info: NOT DEFERRABLE INITIALLY IMMEDIATE ENABLE VALIDAT
E
Mar 29, 2010 12:49:57... Info:
Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info: Statement successf
ully executed: DROP TABLE "BC_MID_TREE_ITEM"
Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info: Statement successf
ully executed: DROP TABLE "BC_MID_TREE_ITEM"
Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info: Statement successf
ully executed: CREATE TABLE "BC_MID_TREE_ITEM"("NODE_ID" RAW(16) NOT NULL, "ITE
M_ID" RAW(16) )
Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info: Statement successf
ully executed: CREATE TABLE "BC_MID_TREE_ITEM"("NODE_ID" RAW(16) NOT NULL, "ITE
M_ID" RAW(16) )
Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info: Statement successf
ully executed: CREATE INDEX "BC_MID_TREE_ITEM_R" ON "BC_MID_TREE_ITEM"("ITEM_ID"
Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info: Statement successf
ully executed: CREATE INDEX "BC_MID_TREE_ITEM_R" ON "BC_MID_TREE_ITEM"("ITEM_ID"
Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info: Statement successf
ully executed: ALTER TABLE "BC_MID_TREE_ITEM" ADD PRIMARY KEY ("NODE_ID") NOT DE
FERRABLE INITIALLY IMMEDIATE ENABLE VALIDATE
Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info: Statement successf
ully executed: ALTER TABLE "BC_MID_TREE_ITEM" ADD PRIMARY KEY ("NODE_ID") NOT DE
FERRABLE INITIALLY IMMEDIATE ENABLE VALIDATE
Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info: Runtime XML of BC_
MID_TREE_ITEM successfully written
Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info: Runtime XML of BC_
MID_TREE_ITEM successfully written
Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info: Runtime XML of BC_
MID_TREE_ITEM successfully written
Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info: Runtime XML of BC_
MID_TREE_ITEM successfully written
Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info: Analysis and adjus
tment of tables successfully executed
Mar 29, 2010 12:49:57... Info: 12:49:57 2010-03-29 dbs-Info: Analysis and adjus
tment of tables successfully executed
Mar 29, 2010 12:49:57... Info: Finished successfully: development component 'tc/
slm/mid/dd'/'sap.com'/'MAIN_APL70P18_C'/'2712380'/'0', grouped by
Mar 29, 2010 12:49:57... Info: Starting to save the repository
Mar 29, 2010 12:49:57... Info: Finished saving the repository
Mar 29, 2010 12:49:57... Info: Starting: Update: Selected development component
'tc/archtech/browser/viewer/locator'/'sap.com'/'MAIN_APL70P18_C'/'2712383'/'0' u
pdates currently deployed development component 'tc/archtech/browser/viewer/loca
tor'/'sap.com'/'MAIN_APL70VAL_C'/'1496536'/'0'.
Mar 29, 2010 12:49:57... Info: SDA to be deployed: /usr/sap/IRX/DVEBMGS02/SDM/ro
ot/origin/sap.com/tc/archtech/browser/viewer/locator/MAIN_APL70P18_C/0/2712383/t
carchtechbrowserviewerlocator.sda
Mar 29, 2010 12:49:57... Info: Software type of SDA: J2EE
Mar 29, 2010 12:49:57... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE A
pplication) *****
Mar 29, 2010 12:49:58... Info: Starting cluster instance processes.
Mar 29, 2010 12:50:03... Info: Starting the instance JC_PRDCIXI_IRX_02 running o
n host PRDCIXI_svc
Mar 29, 2010 12:50:03... Info: Starting the instance JC_PRDCIXI_IRX_02 processes
. The instance is running on host PRDCIXI_svc
Mar 29, 2010 12:50:03... Info: Starting the process dispatcher
Mar 29, 2010 12:50:03... Info: Starting the process server0
Mar 29, 2010 6:49:58 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE App
lication) *****
Mar 29, 2010 6:49:58 PM Error: Aborted: development component 'tc/archtech/brow
ser/viewer/locator'/'sap.com'/'MAIN_APL70P18_C'/'2712383'/'0', grouped by softwa
re component 'LM-TOOLS'/'sap.com'/'MAIN_APL70P19_C'/'1000.7.00.19.0.200904271432
29''/'0':
SDM could not start the J2EE cluster on the host PRDCIXI! The online deployment
is terminated.
A timeout occured during the cluster running verification.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDepl
oyerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Mar 29, 2010 6:49:58 PM Info: Starting to save the repository
Mar 29, 2010 6:49:59 PM Info: Finished saving the repository
Mar 29, 2010 6:49:59 PM Info: Starting: Update: Selected software component 'LM
-TOOLS'/'sap.com'/'MAIN_APL70P19_C'/'1000.7.00.19.0.20090427143229''/'0' updates
currently deployed software component 'LM-TOOLS'/'sap.com'/'MAIN_APL70P14_C'/'1
000.7.00.14.1.20080124101556''/'0'.
Mar 29, 2010 6:49:59 PM Error: Aborted: software component 'LM-TOOLS'/'sap.com'
/'MAIN_APL70P19_C'/'1000.7.00.19.0.20090427143229''/'0':
Failed deployment of SDAs:
development component 'tc/archtech/browser/viewer/locator'/'sap.com'/'MAIN_APL70
P18_C'/'2712383'/'0' : aborted
Please, look at error logs above for more information!
Mar 29, 2010 6:49:59 PM Info: Starting to save the repository
Mar 29, 2010 6:49:59 PM Info: Finished saving the repository
Mar 29, 2010 6:49:59 PM Info: Restoring the state of the instance (JC_PRDCIXI_I
RX_02) process server0 from Stopped to Running
Mar 30, 2010 12:50:00... Error: Received exception when restoring Engine state:
A timeout occured during the cluster state restore verification.
Mar 30, 2010 12:50:00... Error: -
At least one of the Deployments
failed -
Regards,
Priya

Hi Priya,
As per your error message, there is problem with the SDM is not starting after finishing deployment on SAP J2EE Engine Deployment. Development component are not deployed properly due to error message
> SDM could not start the J2EE cluster on the host PRDCIXI! The online deployment is terminated. A timeout occured during the cluster running verification. P
Please check the default timeout and increased as requred.
Please check the below thread to rectify this issue.
SDM Troubleshooting : http://help.sap.com/saphelp_nw04/helpdata/de/76/fb72ec091f4bf8a2d8ba321bb7e8d9/frameset.htm
SDM Troubleshooting : https://cw.sdn.sap.com/cw/docs/DOC-29627:
Hope it helps
Regards
Arun

Unable to Deply using JSPM in PI 7.1

Hi Experts,
Please can any one tell me the process how to deploy *.war in PI 7.1.
I tired to use JSPM tool but unable to deploy (FTP_JDBC_ConnectionValidation_711.zip).
Thanks
Sunil

Hi,
The above notes are for JSPM tool. Just check if the below link is of any use to you.
http://help.sap.com/saphelp_nwpi71/helpdata/en/23/c0e240beb0702ae10000000a155106/frameset.htm
Just a thought, probably the subject of thread is misleading as I am not sure if your particular application has to be deployed using JSPM.
Regards,
Siddhesh S.Tawate
Edited by: siddhesh tawate on May 16, 2009 3:22 PM

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

Axis framework deployment in PI 7_1 using JSPM only

Similar Messages

Maybe you are looking for