Default Adapter with SAP PI 7.1 EHP1

Hi,
Thanks for an overwhelming response to all my questions.
I need some information about the SAP PI 7.1 tool. The information needed is as following
1. How many default adapter we get with SAP PI EHP 1 package?
2. If we need some special adapters which are not a part of the tool, is it possible to develop it?
3. Where can we develop these adapters? In SAP PI only or cane we develop them in java and add the jar file and use it in the process integrator?
Thanks in advance.
Gautam

>
> 1. How many default adapter we get with SAP PI EHP 1 package?
No extra adapter added in PI7.1 EHP1.
> 2. If we need some special adapters which are not a part of the tool, is it possible to develop it?
Yes you can develop a new adapter,depends on your requirement,for that you need to download meta data from service.sap.com.
> 3. Where can we develop these adapters? In SAP PI only or cane we develop them in java and add the jar file and use it in the process integrator?
>
Use NWDS 7.1 ,Eclipse to develo,but NWDS is adviceble one.
Even third party adapters availble,based on your requiremnet we can buy those adapters and deploy in PI.
Regards,
Raj

Similar Messages

How to configure for GPlus Adapter with SAP Phone and SAP CRM

Hi All Basis Adm,
Please consider as an urgent basis i need the information that how to configure GPlus Adapter with SAP Phone and SAP CRM . My server is CRM 5.0 (kernel 7) with Oracle Database. This information is require to connect Webclient to Sap Phone with GPlus Adapter (Genesys Adapter 7.1). If u have any document regarding mentioned above than that will be acceptable.
Regds,
Govinda

Hi Prasad,
In you case, it's a file to file scenario.
Go thro' this link for a solution:-
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
Regards.
Praveen

Sender Mail Adapter with SAP Conversion agent

have some1 used SAP conversion agent on attchment from XI Sender Mail adapter?
it seems to ignore the attchment of the e-mail
the sender configuration module tab is as follows :
1.localejbs/AF_Modules/PayloadSwapBean transform
2.localejbs/sap.com/com.sap.nw.cm.xi/CMTransformBean CM
3.sap.com/com.sap.aii.adapter.mail.app/XIMailAdapterBean mail
The paramters are
transform swap.keyName Content-Disposition
transform swap.keyName Content-Description
transform swap.keyValue attachment
transform swap.keyValue codeco
CM TransformationName ZIM_CODECO_VALIDATIONS
The Convesion Agnet runs prefectly when using the Conversion Agent engine
thx,Shai Rosenzweig

check with tis may helpful for you
http://help.sap.com/saphelp_nw04/helpdata/en/43/4c38c4cf105f85e10000000a1553f6/frameset.htm
Regds
Abhishek

Inqmy resource adapter for SAP with Bea Weblogic Server

          Hi everybody,
          Anybody have tried to use INQMY resource adapter for SAP with Bea weblogic server
          It works well with INQMY server, but with BEA I'm getting a lot of problems creating
          the connections.
          Thanks in advance.
          Xavi.


All,
          Here are the steps we (used for internal testing) had to perform to get
          IN-Q-MY adapter for SAP to work with WebLogic:
          The wli.adapter.inqmy.sapr3.spi package contains extensions to the
          In-Q-My J2EE Connector Architecture classes to overcome some limitations
          in the base implementation classes. To get around these issues, we had
          to extend their R3ManagedConnectionFactory, R3ConnectionManager, and
          R3ConnectionFactory classes.
          * The javax.resource.spi.ManagedConnectionFactory implementation
          does not over-ride the equals and hashCode methods correctly. This
          causes problems with WLS 6.1.
          * There is a bug in their javax.resource.spi.ConnectionManager
          implementation for non-managed uses of the adapter. Consequently, their
          adapter cannot be used in a non-managed scenario.
          * The javax.resource.cci.ConnectionFactory class does not support
          the getConnection() method that does not take any arguments (it throws a
          null pointer exception).
          I am attaching the classes discussed above.
          Cheers,
          Chris
          Torsten Friebe wrote:
          > Hi,
          >
          > does anybody know where to get a trail version - if one exists - of IN-Q-MY
          > application server or the resource adapter?
          >
          > Thanks, regards
          > Torsten
          >
          > "Xavi" <[email protected]> schrieb im Newsbeitrag
          > news:[email protected]...
          >
          >>Hi everybody,
          >>
          >>Anybody have tried to use INQMY resource adapter for SAP with Bea weblogic
          >>
          > server
          >
          >>?
          >>
          >>It works well with INQMY server, but with BEA I'm getting a lot of
          >>
          > problems creating
          >
          >>the connections.
          >>
          >>Thanks in advance.
          >>Xavi.
          >>
          >>
          >
          >
          package wli.adapter.inqmy.sapr3.spi;
          import java.io.Serializable;
          import javax.resource.ResourceException;
          import javax.resource.cci.Connection;
          import javax.resource.cci.ConnectionSpec;
          import javax.resource.spi.ConnectionManager;
          import javax.resource.spi.ConnectionRequestInfo;
          import javax.resource.spi.ManagedConnection;
          import javax.resource.spi.ManagedConnectionFactory;
          import com.inqmy.r3adapter.R3ConnectionSpec;
          import com.inqmy.r3adapter.R3ManagedConnectionFactory;
          * Extends the In-Q-My implementation to allow for getConnection() with no
          * connection spec, i.e. use the default configured connection parameters.
          public class R3ConnectionFactory
          extends com.inqmy.r3adapter.R3ConnectionFactory
          implements com.bea.connector.IProxyMarker {
          private R3ConnectionSpec m_cspec;
          public R3ConnectionFactory(ConnectionManager cm, R3ManagedConnectionFactory mcf)
          throws ResourceException {
          super(cm, mcf);
          String strClientNumber = mcf.getClientNumber();
          if (strClientNumber == null) {
          throw new javax.resource.spi.IllegalStateException("ClientNumber not set for "+mcf);
          String strLanguage = mcf.getLanguage();
          if (strLanguage == null) {
          throw new javax.resource.spi.IllegalStateException("Language not set for "+mcf);
          String strUserName = mcf.getUserName();
          if (strUserName == null) {
          throw new javax.resource.spi.IllegalStateException("UserName not set for "+mcf);
          String strPassword = mcf.getPassword();
          if (strPassword == null) {
          throw new javax.resource.spi.IllegalStateException("Password not set for "+mcf);
          m_cspec = new R3ConnectionSpec(strClientNumber, strLanguage, strUserName, strPassword);
          public Connection getConnection(ConnectionSpec connectionSpec)
          throws ResourceException {
          if (connectionSpec == null) connectionSpec = m_cspec;
          return super.getConnection(connectionSpec);
          package wli.adapter.inqmy.sapr3.spi;
          import java.io.Serializable;
          import javax.resource.ResourceException;
          import javax.resource.spi.ConnectionManager;
          import javax.resource.spi.ConnectionRequestInfo;
          import javax.resource.spi.ManagedConnection;
          import javax.resource.spi.ManagedConnectionFactory;
          * Extends the In-Q-My implementation to over-ride the
          * allocateConnection method to return a CCI connection vs. a ManagedConnection
          public class R3DefaultConnectionManager
          implements ConnectionManager, Serializable {
          public R3DefaultConnectionManager() {}
          public Object
          allocateConnection(ManagedConnectionFactory mcf, ConnectionRequestInfo cri)
          throws ResourceException {
          ManagedConnection mc = mcf.createManagedConnection(null, cri);
          return mc.getConnection(null, cri);
          package wli.adapter.inqmy.sapr3.spi;
          import javax.resource.spi.ConnectionManager;
          import javax.resource.spi.ConnectionRequestInfo;
          import javax.resource.spi.ManagedConnection;
          import javax.security.auth.Subject;
          * Extends the In-Q-My implementation to get around some problems encountered
          * while running on WebLogic:
          * <ul>
          * <li>Must over-ride default implementation of equals and hashCode method</li>
          * <li>Needed to provide my version of the CCI ConnectionFactory</li>
          * <li>Needed to provide my version of the default ConnectionManager for the
          * non-managed scenario use case</li>
          * </ul>
          public class R3ManagedConnectionFactory
          extends com.inqmy.r3adapter.R3ManagedConnectionFactory {
          private int m_iHashCode;
          transient private com.inqmy.r3adapter.R3ConnectionRequestInfo t_cri = null;
          public R3ManagedConnectionFactory() {
          super();
          java.rmi.server.UID uid = new java.rmi.server.UID();
          m_iHashCode = uid.hashCode();
          public Object createConnectionFactory() {
          // need to install our own default connection manager because In-Q-My
          // version causes a ClassCastException in CCI ConnectionFactory
          // getConnection
          return createConnectionFactory(new R3DefaultConnectionManager());
          public ManagedConnection createManagedConnection(Subject subject, ConnectionRequestInfo cri)
          throws javax.resource.ResourceException {
          // need to check for null on the ConnectionRequestInfo object because the
          // In-Q-My R3ManagedConnection ctor does not check for null
          if (cri == null) cri = getDefaultConnectionRequestInfo();
          return new com.inqmy.r3adapter.R3ManagedConnection(this, subject, cri);
          public Object createConnectionFactory(ConnectionManager connectionManager) {
          // need to supply a connection factory that can deal with getConnection
          // that does not take a ConnectionSpec
          try {
          return new R3ConnectionFactory(connectionManager, this);
          } catch (javax.resource.ResourceException re) {
          re.printStackTrace();
          throw new java.lang.IllegalStateException(re.getMessage());
          com.inqmy.r3adapter.R3ConnectionRequestInfo getDefaultConnectionRequestInfo()
          throws javax.resource.spi.IllegalStateException {
          if (t_cri == null) {
          String strClientNumber = this.getClientNumber();
          if (strClientNumber == null) {
          throw new javax.resource.spi.IllegalStateException("ClientNumber not set for "+this);
          String strLanguage = this.getLanguage();
          if (strLanguage == null) {
          throw new javax.resource.spi.IllegalStateException("Language not set for "+this);
          String strUserName = this.getUserName();
          if (strUserName == null) {
          throw new javax.resource.spi.IllegalStateException("UserName not set for "+this);
          String strPassword = this.getPassword();
          if (strPassword == null) {
          throw new javax.resource.spi.IllegalStateException("Password not set for "+this);
          t_cri = new com.inqmy.r3adapter.R3ConnectionRequestInfo(strClientNumber, strLanguage, strUserName, strPassword);
          return t_cri;
          public boolean equals(Object obj) {
          if (obj == null) return false;
          if (obj == this) return true;
          if (!this.getClass().isInstance(obj)) return false;
          R3ManagedConnectionFactory mcf = (R3ManagedConnectionFactory)obj;
          return compare(getClientNumber(), mcf.getClientNumber()) &&
          compare(getLanguage(), mcf.getLanguage()) &&
          compare(getUserName(), mcf.getUserName()) &&
          compare(getPassword(), mcf.getPassword()) &&
          compare(getServerName(), mcf.getServerName()) &&
          compare(getSystemNumber(), mcf.getSystemNumber());
          protected final boolean compare(final Object obj1, final Object obj2) {
          if (obj1 == obj2) return true;
          if (obj1 != null) {
          return obj1.equals(obj2);
          } else {
          if (obj2 == null) {
          return true;
          } else {
          return false;
          public int hashCode() { return m_iHashCode; }

Error in using XI-SOAP adapter, but no error with SAP-BC

Hi,
I am working on RFC->XI->Webmethod (.asp) scenatio.
I am using SOAP adapter.
Whin I am not using "Do not use SOAP Envelop".
I am getting "com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML" Error in SXMB_MONI.
But when I am using "Do not use SOAP Envelop" then I am not getting any error. in SXMB_MONI status showing Successfully Processed. But the responce i am getting is "You are not authorized to view this page // HTTP 401.1 - Unauthorized: Logon Failed"
But same web-service is working fine while connected with SAP-BC.
Please Help why scenario is working with BC, but not with XI.
Thanks & Regards

Hi Bhavesh,
Thanks for reply.
I am getting all success in message monitoring, but still web-services sying they are not getting any message.
I am attaching all 4 logs for one synchronous communication of message monitoring.
I am not able to understand where message going and why XI showing success every where.
********1st(Sent Messages)
Success SOAP: response message leaving the adapter
Success Application attempting to send an XI message asynchronously using connection AFW.
Success Trying to put the message into the send queue.
Success The response message for message cf4fd921-4a74-11db-9312-001279933263(INBOUND) was successfully transmitted to the calling application.
Success The message status set to DLVD.
Success The application sent the message asynchronously using connection AFW. Returning to application.
********2nd (Sent Messages)
Success RFC adapter received sRFC for Z_PA_SAP_TO_Webservice from D02/230. Attempting to send message synchronously
Success Application attempting to send an XI message synchronously using connection AFW.
Success Trying to put the message into the call queue.
Success Message successfully put into the queue.
Success The message was successfully retrieved from the call queue.
Success The message status set to DLNG.
Success The message was successfully transmitted to endpoint http://XYZ.com:8000/sap/xi/engine?type=entry using connection AFW.
Success The application sent the message synchronously using connection AFW. Returning to application.
Success The message status set to DLVD
**********3rd (Received Messages)
Success Using connection AFW. Trying to put the message into the receive queue.
Success The XI response message for message d0372be1-4a74-11db-91d7-001279933263(INBOUND) was successfully returned to the calling application.
Success The message status set to DLVD.
**********4th (Received Messages)
Success The message was successfully received by the messaging system. Profile: XI URL: http://XYZ.com:50000/MessagingSystem/receive/AFW/XI
Success Using connection AFW. Trying to put the message into the request queue.
Success Message successfully put into the queue.
Success The message was successfully retrieved from the request queue.
Success The message status set to DLNG.
Success Delivering to channel: IF_O_502_WebserviceBusService_SOAP_In_02
Success SOAP: request message entering the adapter
Success SOAP: completed the processing
Success SOAP: response message received d0372be1-4a74-11db-91d7-001279933263
Success The message status set to DLVD.
Success The message was successfully delivered to the application using connection AFW.

RFC calls with SAP JCO and IBM resource adapter for SAP - basic tuning

Hi experts,
we are working on a java portal connected to a backend system SAP by calling RFCs.
On our first integration tests, it appears to be quite slow fetching data from SAP by calling the remote functions from the custom portal. We are using SAP JCo 3.0.6 and IBM resource adapter for SAP 7.0.0.3 to integrate SAP with our portal.
Is there any basic tuning to achieve to improve performances or any hint of where to tune in SAP ?
Any help would be greatly appreciated.
Thanks a lot,
Jamal

Hi Jamal,
I understand you have already checked performance issues in the SAP Server. We had some problems with certain RFC calls and it turned out to be a badly developed ABAP sentence.
I'd recommend you to use httpwatch or another tool to check the response times from the browser, so you can point accurately where the is.
Regards
Francisco

Archiving: experience with Oracle's Archive Adapter for SAP

All,
Does anyone have experience to share about Oracle's "Content Database Archive Adapter for SAP Applications"?
Thanks
Guenther

Sasi,
There is a new MySAP adapter with 10.13.1 and above to support ECC 6.0. Please see the following section in the 10.1.3.1 adapter release notes:
12.4.1 MySAP ERP Versions and APIs
The following MySAP ERP platforms are supported by OracleAS Adapter for MySAP
ERP:
■ SAP R/3 Enterprise 47x100
■ SAP R/3 Enterprise 47x200
■ MySAP ERP Central Component (ECC) 5.0, deployed on SAP NetWeaver 2004
■ MySAP ERP Central Component (ECC) 6.0, deployed on SAP NetWeaver 2004s
■ SAP Java Connector (SAP JCo) Version 2.18.
For the current release status of the SAP Java Connector, refer to SAP Note #549268
in the SAP Service Marketplace.
Release versions may vary by product component. In addition, SAP functions may
vary by SAP product version and support package.
Note: The OracleAS Adapter for MySAP ERP supports only the versions listed above.
It is not recommended to use the OracleAS Adapter for MySAP ERP with older
versions of SAP R/3. If you plan to use the adapter with older versions of SAP R/3 for
example SAP R/3 4.6C, prior approval from iWay Software Product Management is
required.

Default Sites and subscriptions with SAP installation package

Hello,
Does anyone knw what are the default Sites and subscriptions provided with SAP installation package - i.e. in client 000, 001.
Rgds
Priyanka

You can go to Tcode SMOEAC and check.
Pls reward points if helpful.
PB

SAP GUI not working with SAP* and DDIC default passwords

Hi SAP Guru's ,
at last I installed the SAP ECC6.0 on Windows 2003 (stand alone) with Oracle 10G database.
I installed the SAP GUI , when I am trying to loging from SAP GUI clients 000 and 001 with SAP* and DDIC user accounts I am naot able to login . please give me the how to configure this .
thanks in advance
Edited by: srinivas kaveti on Apr 4, 2008 9:16 PM

Hi Srinivas,
You should set "login/no_automatic_user_sapstar=0", in the SAP profile. With ECC 6.0, default sapstar user deactivated. You can take a look at OSS note #68048, for detailed information.
Best regards,
Orkun Gedik

Oracle Adapter for SAP that supports Integration with SAP 6.0??

Hi,
I am working currently with Oracle Adapter for SAP with SAP 4.6.
But my company is looking for upgrading the Enterprise SAP system to 6.0.
Do we have Oracle Adapter for SAP that supports SAP 6.0? Please let me know if anyone has already worked on this?
Thanks,
Sasi Bhushan

Sasi,
There is a new MySAP adapter with 10.13.1 and above to support ECC 6.0. Please see the following section in the 10.1.3.1 adapter release notes:
12.4.1 MySAP ERP Versions and APIs
The following MySAP ERP platforms are supported by OracleAS Adapter for MySAP
ERP:
■ SAP R/3 Enterprise 47x100
■ SAP R/3 Enterprise 47x200
■ MySAP ERP Central Component (ECC) 5.0, deployed on SAP NetWeaver 2004
■ MySAP ERP Central Component (ECC) 6.0, deployed on SAP NetWeaver 2004s
■ SAP Java Connector (SAP JCo) Version 2.18.
For the current release status of the SAP Java Connector, refer to SAP Note #549268
in the SAP Service Marketplace.
Release versions may vary by product component. In addition, SAP functions may
vary by SAP product version and support package.
Note: The OracleAS Adapter for MySAP ERP supports only the versions listed above.
It is not recommended to use the OracleAS Adapter for MySAP ERP with older
versions of SAP R/3. If you plan to use the adapter with older versions of SAP R/3 for
example SAP R/3 4.6C, prior approval from iWay Software Product Management is
required.

Error JOB MS.JOB.DELETE in Adapter Engine SAP XI 7.0

Hello,
I am getting an error in JOB that deletes messages from the adapter engine of SAP XI 7.0, can someone help me?
Adapter Engine, message: Fatal DeleteJob (Default Delete Job) failed.(Details: Code: MS.JOB.DELETE, Location: com.sap.aii.af.ra.ms.impl.core.archiving.executor.DeleteExecutor, Reason: com.sap.aii.af.ra.ms.api.DeliveryException: Error removing messages or audit log entries with expired persist duration., Time: 14.08.2008 21:00:05)
Thanks
Zanchetta

Hi Roberto,
We have noticed this behavior after our PI system is upgraded to PI 7.0 Ehp1.
It is caused by JDBC driver after upgrade. This issue is resolved in the following new jdbc driver which is available on the SAP Service Marketplace:
DB2 Driver for ODBC and CLI V9.7 FP3a SB27297.
Hope your issue will be resolved by this fix. If it's not resolved, please open up a message with SAP.
Thanks,
Siva Kumar

Error in Sender AXIS adapter with UsernameToken

Hello,
I'm trying to implement a web service with UsernameToken authentication (legacy >PO>ECC), after research in this forum, some blogs and notes, I've found this approach: Axis Adapter Sender Comm Channel with usernameToken .
I did all steps, but everytime I try to consume the web service, it doesn't work and I get the following error in default trace:
No application classloader can load login module class: com.sap.engine.services.security.server.jaas.DigestLoginModule. Probably application that deployed the login module is stopped and cannot be started.
My system is PO 7.4 SP5.
Do you have any idea?

Hi,
May be below links will help you
1. /people/michal.krawczyk2/blog/2005/12/18/xi-sender-mail-adapter--payloadswapbean--step-by-step
2. Have you used method of ConnectionFactory also??
3. 804102
xi 3.0 mail adapter with pop3 user authentication problem
4. 810238
XI 3.0 Mail Adapter for POP3 may not report some errors
Thanks
Swarup

Mail Sender Adapter with IMAPS

Hi,
I had a Mail Sender Adapter running fine with imap. Our Email Server has changed now to secure protocol. Therefore I need to use the Mail Sender Adapter with IMAPS. If I use imaps://<mailserver>:993 in the channel configuration the Mail Adapter aborts with error "not initialized; mail agent null" and in the default trace it says "failed to initialize the channel: java.io.IOException: illegal protocol for XMBIMAPInitiator: imaps#". If I configure the Mail Adapter with <b>imap</b>://<mailserver>:993 the Mail Adapter starts and says "running", but it does not poll the postbox. In the security.log file there is a warning about untrusted certificates "com.sap.security.core.server.https.SecureConnectionFactory#Plain###Attempting to create outgoing ssl connection without trusted certificates#". I did already import the (CA) Certifcate of the mailserver with key storage service of J2EE Engine in the Trusted area and I configured the J2EE Engine for using SSL (the https access to the J2EE Engine works fine).
What is still missing in XI 3.0 (SP12)? I can access the postbox securely with e.g. Thunderbird using port 993.
Has anyone an idea or had already this issue?
Thanks for any help in advance.
Peter

Hi Sebastian ,
The Mail sender --IMAPS , did it solve your issue because i fcae the same kind of Error in Communication Channel :
exception caught during processing mail message; java.io.IOException: unable to create a socket
Mail sender CC:imaps://NZxxx.dknz.nzcorp.net:993/NZDKINVOICES
-Login Credentials is correct.
-Defualt XI Paramters are correct
-Mail Server is the right one
-Tried in command prompt , N:/telnet NZxxx.dznz.corp.net 143 , but i get response : Could not open connection to the host, on port 143 .Connection Failed
Could you kindly assist
Thanks,
Vara

Exception caught by adapter framework: No configuration / default adapter specified for EDISeparator

Hello Experts,
I am configuring the scenario ( AS2 to EDISeparator and EDISeparator to IDOC ).
Can you please help me with the error below which is from the either the EDISeparator Receiver channel or the EDISeparator Sender channle.
09.06.2014 17:52:18.709
Information
Message is encrypted with 1.3.14.3.2.7 algorithm
09.06.2014 17:52:18.778
Information
AS2 Message is signed with SHA1 (1.3.14.3.2.26) algorithm
09.06.2014 17:52:18.779
Information
AS2 Message message signature is validated, signer ID is X509CertSelector: [ Serial Number: 1624063516 Issuer: CN=Mendelson AS2 TEST,OU=Integration,O=Mendelson,L=Berlin,ST=Unknown,C=GE matchAllSubjectAltNames flag: true ]
09.06.2014 17:52:18.784
Information
AS2 document size is 350 Bytes
09.06.2014 17:52:18.784
Information
Payload charset converted from ISO-8859-15 to ISO-8859-15
09.06.2014 17:52:18.785
Information
B2B EdifactConverterModule : EDI format detected as EANCOM
09.06.2014 17:52:18.785
Information
B2B EdifactConverterModule: Message will be read as ISO-8859-1.
09.06.2014 17:52:18.785
Information
MP: processing local module localejbs/EdifactConverterModule
09.06.2014 17:52:18.785
Information
0}: The module-paramteter "eancom.subversion.prefix" is not set. Using default value "false"
09.06.2014 17:52:18.786
Information
0}: The module-paramteter "eancom..audit" is not set. Using default value "false"
09.06.2014 17:52:18.791
Information
MP: processing local module localejbs/CallSapAdapter
09.06.2014 17:52:18.791
Information
Application attempting to send an XI message asynchronously using connection AS2_http://sap.com/xi/XI/AS2
09.06.2014 17:52:18.792
Information
Trying to put the message into the send queue
09.06.2014 17:52:18.831
Information
Message successfully put into the queue
09.06.2014 17:52:18.831
Information
The application sent the message asynchronously using connection AS2_http://sap.com/xi/XI/AS2. Returning to application
09.06.2014 17:52:18.836
Information
MIC (DeJYUIusqQj6aaYRASdHhAo+4J0=) is calculated using SHA1 algorithm.
09.06.2014 17:52:18.838
Information
The message was successfully retrieved from the send queue
09.06.2014 17:52:18.843
Information
Message status set to DLNG
09.06.2014 17:52:18.845
Information
MDN is succcessfully signed with SHA1 (1.3.14.3.2.26) algorithm
09.06.2014 17:52:18.859
Information
Trying to put the message into the send queue
09.06.2014 17:52:18.912
Information
Message successfully put into the queue
09.06.2014 17:52:18.913
Information
The message was successfully retrieved from the send queue
09.06.2014 17:52:18.918
Information
Message status set to DLNG
09.06.2014 17:52:18.961
Information
Trying to put the message into the send queue
09.06.2014 17:52:19.001
Information
Message successfully put into the queue
09.06.2014 17:52:19.001
Information
The message was successfully retrieved from the send queue
09.06.2014 17:52:19.006
Error
MP: exception caught with message No configuration / default adapter specified for EDISeparator
09.06.2014 17:52:19.006
Information
Delivering to channel: B2BSE00002_O2C_ORDERS_VANS_PO_WRITE_EDISeparator
09.06.2014 17:52:19.006
Information
Message status set to DLNG
09.06.2014 17:52:19.009
Error
Exception caught by adapter framework: No configuration / default adapter specified for EDISeparator
09.06.2014 17:52:19.010
Error
Transmitting the message to endpoint <local> using connection AS2_http://sap.com/xi/XI/AS2 failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: No configuration / default adapter specified for EDISeparator
09.06.2014 17:52:19.015
Information
The asynchronous message was successfully scheduled to be delivered at Mon Jun 09 17:57:19 CEST 2014
09.06.2014 17:52:19.015
Information
Message status set to WAIT

Hello Ruchir Sinha and Dimitri Sannen,
I think I have progressed a bit. Just unsure of the usage of the Module configuration .I now get a new error (see below) and the updated config details are :
Sender Interface :
Receiver Interface :
Sender AS2 config :
Receiver EDISeparator config :
Sender EDISeparator config :
Receiver IDOC config :
IDoc details configured but not added in this document
16.06.2014 11:52:35.414
Information
The message was successfully retrieved from the send queue
16.06.2014 11:52:35.420
Information
Delivering to channel: B2BSE00002_O2C_ORDERS_VANS_PO_WRITE_EDISeparator
16.06.2014 11:52:35.420
Information
MP: processing local module localejbs/ModuleProcessorExitBean
16.06.2014 11:52:35.420
Information
Message entered AF MP exit bean and will now be passed to the JCA adapter
16.06.2014 11:52:35.420
Information
Message status set to DLNG
16.06.2014 11:52:35.433
Information
UNA segment UNA found
16.06.2014 11:52:35.444
Information
Parsed UNB segment 333333333/014 to 111111111/014
16.06.2014 11:52:35.445
Information
Parsed UNH segment ORDERS D96A
16.06.2014 11:52:35.514
Information
Searching sender channel for Eancom message part message with Message type ORDERS, Message version number D, Message release number 96A, Interchange sender identification 333333333, Interchange sender identification code qualifier 014, Interchange recipient identification 111111111, Interchange recipient identification code qualifier 014, Message Subversion EAN008, Message Agency UN
16.06.2014 11:52:35.579
Information
Sender channel (Channel) keys: ObjectId=7abf551ddbb638268f91af80ec1c04c8 values: ToPartySchema= Attributes=(Attributes:Channel:EDISeparator:INBOUND) values: edisep.advanced=false snd.interchangeSenderId=.* snd.tradacommessagetype=.* snd.xpath= snd.xpath.value= snd.filterCondition=equal snd.edifactMessageReleaseNumTxt= snd.tradacomMessageTypeUsingFreeText=false snd.eancomMessageReleaseUsingFreeText=false snd.eancomMessageVersionFreeText= snd.odetteMessageType=.* snd.edifactMessageVersion=.* snd.xml.splitPath=null snd.eancomMessageVersion=.* snd.odetteMessageVersion=.* snd.edifactMessageRelNumUsingFreeText=false snd.otherVersionReleaseIndustryIdentifierCodeEnabled=false adapterStatus=active snd.vdaMessageType=.* snd.eancomCONTRLMessageRelease=3 snd.odetteMessageTypeTxt= snd.tradacommessageversion=.* snd.edifactMessageVerNumUsingFreeText=false snd.edifactMessageTypeUsingFreeText=false snd.xpathUsingFreeText=false snd.interchangeSenderIdCode=.* snd.otherVersionReleaseIndustryIdentifierCode=.* snd.odetteMessageTypeUsingFreeText=false snd.tradacomreccode=.* snd.edifactMessageVersionFreeText= snd.edifactInterchangeRecipientIdentification=.* eoio.sequenceId= snd.edifactMessageTypeTxt= snd.odetteMessageVerNumUsingFreeText=false snd.eancomMessageVerNumUsingFreeText=false snd.interchangeReceiverId=.* snd.eancomMessageRelease=.* snd.tradacomsendername=.* snd.tradacomMessageTypeTxt= snd.vdaLieferantenNummer=.* snd.interchangeReceiverIdCode=.* snd.edifactInterchangeSenderIdentificationCode=.* snd.odetteMessageVersionFreeText= snd.versionReleaseIndustryIdentifierCode=.* snd.edifactInterchangeSenderIdentification=.* snd.edifactMessageType=.* snd.eancomMessageType=.* snd.xpathTxt= snd.vdaMessageTypeTxt= deliverySemantics=eo snd.eancomMessageReleaseTxt= snd.plainmessagetype=.* snd.xml.split=false snd.edifactMessageRelease=.* snd.vdaMessageTypeUsingFreeText=false snd.tradacomrecname=.* edisep.addParameterParams=TableData: edisep.addParameterParams {} snd.encoding=iso885915 snd.vdaKundenNummer=.* snd.tradacomsendercode=.* snd.edifactCONTRLMessageRelease=3 snd.edifactInterchangeRecipientIdentificationCodeQualifier=.* snd.transactionSetIdentifierCode=.* Service=ASJAVA_DX5 Channel=B2BSE00002_O2C_ORDERS_PO_ECC_READ_EDISeparator EngineType=CA Party= TransProt=XI TransProtVers=1.0.0 FromPartySchema= FromPartyAgency= Direction=I MsgProt=EANCOM MsgProtVers=1.0.0 EngineName= AdapterType=EDISeparator AdapterSWCV=06c536e6fafe11e0bb1cea8f0a4290b1 ToPartyAgency= AdapterNamespace=http://sap.com/xi/XI/EDISeparator found. New message ID is f18894a8-f53b-11e3-a748-00001e96c7e2
16.06.2014 11:52:35.586
Error
MP: exception caught with cause javax.resource.ResourceException: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule
16.06.2014 11:52:35.586
Error
Message could not be forwarded to the JCA adapter. Reason: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule
16.06.2014 11:52:35.590
Error
Exception caught by adapter framework: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule
16.06.2014 11:52:35.591
Error
Transmitting the message to endpoint <local> using connection AS2_http://sap.com/xi/XI/AS2 failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule

Java Addin in SAP Netweaver 7.0 EHP1

Hi Experts,
I have a question about Java Add-in in release Netweaver 7.0 EHP1. As I have understood, with SAP Business Suite 7.0 cannot install java add-in in abap system. Is that correct?
I have in a upgrade proces of BW from 3.5 (ABAP, NO-UNICODE to Netweaver 7.0 EHP1 (without unicode conversion). The upgrade has successfully completed, but now I need to install portal components (EP, EP-CORE and BI-JAVA). How can I install this componentes?... If I install a new system Portal, this would have to be UNICODE... so, can I have, in the same server, two system, one NO-UNICODE (BI) and the other UNICODE (Portal)...??
Best Regards
Juan Carlos Barraza

Hi Barraza,
We had this similar issue. So, here are the answers for your questions.
- Yes, correct. As of SAP Business Suite 7.0 one cannot install java add-in in abap system (Note 855534 ).
- You have Abap as Non-unicode on EHP1. So, Java AddIn installation is NOT supported as Java is a Unicode. The only way for you is, to install a separate Java System in the same machine. Yes, you can install 2 or many systems in a server if the server is strong enough. Then connect the Java system to the Abap system, it works. There is a configuration for this connection.
Later, if you want to upgrade the Abap system to EHP4 or upwards, it can also be done without much hassel. Please award if you find my post useful.
Regards,
Mohan.

Default Adapter with SAP PI 7.1 EHP1

Similar Messages

Maybe you are looking for