Webservices on WAS6.20 ABAP stack

Hello Everybody,
I know, there is an option available to expose RFCs on WAS6.20 server.
I have tested and it worked fine also.
But, here I am more concerned about usability of this option in the production environments. Can we take use of Web services in WSA6.20 ABAP stack for production?
Have anybody developed any solutions using this approach for production environment or any companies, who has used this approach in the production environments?
One more question:
Can we provide secure connection for the communication between WS client and Web Services?
When I call RFCs through Web Services, it uses http connection. Can I replace http connection by https connection?
Waiting for reply.
Thanks in advance,
Bhavik

Hi Bhavik,
  Consuming webservices in WAS 6.2 is not so easy becos it does not support proxy generation. Nevertheless Thomas Jung has succesfully consumed webservices in 6.2 , for more on that have a look at  <b>BSP a Developer's Journal Part XIV - Consuming WebServices with ABAP</b>  @ </people/thomas.jung3/blog/2004/11/17/bsp-a-developers-journal-part-xiv--consuming-webservices-with-abap>
Again for having secure connection between client and server have a look at the CONFIGURATION section of the same blog.
Hope that answers your questions.
Best regards,Girish
PS: Reward points if reply is useful

Similar Messages

  • Call of an external web service out of the ABAP-Stack

    Hi experts,
    i have to implement a call of an external webservice out of the ABAP-stack. Directly from an ABAP-report, not using any PI/XI.
    The only thing the one implemented the service could give me was a description of the SOAP-call which should take place (see code below). So i should pass some data, call the function 'makeACall', and receive some data. But i have no idea how to use the calls of the include SOAPINCL. Is there any example showing the 'translation' of such a SOAP-message into an ABAP-stack-call?
    Thanks and regards
    Christian
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:XXX="urn:nsf">
    <SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" id="_0">
    <makeACall xmlns="urn:nsf">
         <in xsi:type="xsd:string">
              <BaseApp>
                        <Control>
                             <Plugin><![CDATA[]]></Plugin>
                             <Function><![CDATA[]]></Function>
                             <Configuration><![CDATA[]]></Configuration>
                             <ConfigurationName><![CDATA[]]></ConfigurationName>
                        </Control>
                   <Input>
                        <DetInput>
                             <CustomerData>
                                  <Record><![CDATA[]]></Record>
                                  <Record><![CDATA[]]></Record>
                             </CustomerData>
                             <otherData>
                                  <GroupId><![CDATA[]]></GroupId>
                             </otherData>
                        </DetInput>
                   </Input>
              </BaseApp>
         </in>
    </makeACall>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>

    Hi,
    BAM has a set of default web services. You can implement your own web service call and populate the data object with corresponding codes. For instance, if you would want to monitor 2 web services, create a data object with two columns.
    This web service would run every minute and populate the data object columns with 1/0 depending on the state. You could create a chart from this data object to display the status of the web service.
    Please explore more into how to implement web services using BAM. BAM already has few of them and you need to add yours to this.
    Cheers,
    -AR

  • Can you do webreporting with WAS6.40(only ABAP stack)

    Hi gurus,
    I have one question:
    Is it possible to do webreporting with a WAS6.40(only abap)without a java stack. Only the ABAP stack is installed.
    So design/publish reports with the BEx Web Application designer
    Thanks for your reactions in advance.

    Hi,
    Till BW Version 3.5 it should be possible because the Webreporting Enviroment is fully written in ABAP.
    In BI 2004s i know that same things are written in Java, so i think it will not work.
    Regards
    Marcus

  • A failure occured while importing Java SSO ticket certificate in ABAP stack Exception : FOREIGN_ENQUEUE_LOCK

    Dear All,
    We have completed the fresh installation of Soman7.1.
    Now , We are doing the "Configuration of the Solman" and we are in the Step "Basic configuration ".
    SID:        SMI
    Hostname: Solmantrg
    Solman version: 7.1
    The SSO Setup is failing with below error.
    Message :
    A failure occured while connecting to ABAP stack on solmantrg.thetimes.co.in sys=01 client=001 user=null. Details : 'user' missing
    Details of the Log
    Found SID for SSO ACL entry : SMI
    Found login.ticket_client for SSO ACL entry : 000
    The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tc~webadministrator~solmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
    The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (619 bytes)
    ABAP SSO ticket certificate of SMI was imported in ABAP PSE of solmantrg.thetimes.co.in (client 001)
    The ABAP SSO ticket certificate was successfully imported in ABAP System PSE, and the ACL updated accordingly (SID=SMI LoginTicketClient=001)
    A failure occured while importing Java SSO ticket certificate in ABAP stack
    !! Exception : FOREIGN_ENQUEUE_LOCK(Abap cause=SOLMAN_ADMINE_TABLEE)
    The ABAP instance profile contains the parameter : login/accept_sso2_ticket=1
    The SSO ticket Certificate <CN=SMI> has been successfully imported into Java Keystore
    The com.sap.security.core.server.jaas.EvaluateTicketLoginModule already contained the entry : trustedsys=SMI, 001 trustediss=CN=SMI trusteddn=CN=SMI
    The Authentication template for component sap.com/SQLTrace*OpenSQLMonitors was already set to ticket
    The Authentication template for component sap.com/SQLTrace*SQLTrace was already set to ticket
    The Authentication template for component sap.com/tc~monitoring~systeminfo*monitoring was already set to ticket
    The Authentication template for component sap.com/tc~monitoring~systeminfo*sap_monitoring was already set to ticket
    The Authentication template for component sap.com/com.sap.security.core.admin*useradmin was already set to ticket
    The Authentication template for component sap.com/tc~webadministrator~solmandiag*smd was already set to ticket
    The Authentication template for component sap.com/tc~smd~e2etraceupload*E2EClientTraceUploadW was already set to ticket
    The com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule already contained the entry : trustedsys=SMI, 001 trustediss=CN=SMI trusteddn=CN=SMI
    The Authentication template for component sap.com/tc~smd~EemAdminGateway*EemAdmin_Config1 has been set to evaluate_assertion_ticket
    The Login Module BasicPasswordLoginModule was added to the security component sap.com/tc~smd~EemAdminGateway*EemAdmin_Config1
    A failure occured while connecting to ABAP stack on solmantrg.thetimes.co.in sys=01 client=001 user=null
    !! Exception : 'user' missing
    The ABAP instance profile contains the parameter : login/create_sso2_ticket=2
      Exception
    com.sap.mw.jco.JCO$AbapException: (126) FOREIGN_ENQUEUE_LOCK: FOREIGN_ENQUEUE_LOCK
    at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1512)
    at com.sap.mw.jco.JCO$Client.execute(JCO.java:3937)
    at com.sap.mw.jco.JCO$Client.execute(JCO.java:3570)
    at com.sap.sup.admin.setup.AbapSysRfcAdapter.addTrustedIssuer(AbapSysRfcAdapter.java:276)
    at com.sap.sup.admin.setup.AbapSysRfcAdapter.addTrustedIssuer(AbapSysRfcAdapter.java:249)
    at com.sap.sup.admin.setup.ManagingServices.setupDualStackSSO(ManagingServices.java:752)
    at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:564)
    at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:445)
    at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:674)
    at com.sap.sup.admin.setup.ws.SetupWrapper._diagSetup(SetupWrapper.java:279)
    at com.sap.sup.admin.setup.ws.SetupWrapper.diagSetup(SetupWrapper.java:21)
    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:331)
    at com.sap.engine.services.webservices.runtime.JavaClassImplementationContainer.invokeMethod(JavaClassImplementationContainer.java:76)
    at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:174)
    at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:81)
    at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:90)
    at SoapServlet.doPost(SoapServlet.java:51)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    ========================
    com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'user' missing
    at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:518)
    at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1087)
    at com.sap.mw.jco.JCO$Client.connect(JCO.java:3310)
    at com.sap.sup.admin.setup.CommonServices.getJcoClient(CommonServices.java:773)
    at com.sap.sup.admin.setup.CommonServices.getJcoClient(CommonServices.java:722)
    at com.sap.sup.admin.setup.SolManRfcAdapter.getJ2eeSsoSettings(SolManRfcAdapter.java:649)
    at com.sap.sup.admin.setup.ManagingServices.updateSSOfromURLrepository(ManagingServices.java:790)
    at com.sap.sup.admin.setup.ManagingServices.setupDualStackSSO(ManagingServices.java:773)
    at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:564)
    at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:445)
    at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:674)
    at com.sap.sup.admin.setup.ws.SetupWrapper._diagSetup(SetupWrapper.java:279)
    at com.sap.sup.admin.setup.ws.SetupWrapper.diagSetup(SetupWrapper.java:21)
    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:331)
    at com.sap.engine.services.webservices.runtime.JavaClassImplementationContainer.invokeMethod(JavaClassImplementationContainer.java:76)
    at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:174)
    at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:81)
    at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:90)
    at SoapServlet.doPost(SoapServlet.java:51)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    In strustsso2, cerficate date is valid only.
    kindly help us to fix this SSO_Setup issue
    Thanks and Regards,
    Gayathri.K

    Hi ,
    Thanks for the above reply.
    I have executed the Step 2.3 AND 2.4 and i started the SSO Setup again. Still i am getting below error
    Message
    A failure occured while importing Java SSO ticket certificate in ABAP stack
    Details Of the Log
    Found SID for SSO ACL entry : SMI
    Found login.ticket_client for SSO ACL entry : 000
    The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tc~webadministrator~solmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
    The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (619 bytes)
    ABAP SSO ticket certificate of SMI was imported in ABAP PSE of solmantrg (client 001)
    The ABAP SSO ticket certificate was successfully imported in ABAP System PSE, and the ACL updated accordingly (SID=SMI LoginTicketClient=001)
    A failure occured while importing Java SSO ticket certificate in ABAP stack
    !! Exception : FOREIGN_ENQUEUE_LOCK(Abap cause=SOLMAN_ADMINE_TABLEE)
    The ABAP instance profile contains the parameter : login/accept_sso2_ticket=1
    The SSO ticket Certificate <CN=SMI> has been successfully imported into Java Keystore
    The com.sap.security.core.server.jaas.EvaluateTicketLoginModule already contained the entry : trustedsys=SMI, 001 trustediss=CN=SMI trusteddn=CN=SMI
    The Authentication template for component sap.com/SQLTrace*OpenSQLMonitors was already set to ticket
    The Authentication template for component sap.com/SQLTrace*SQLTrace was already set to ticket
    The Authentication template for component sap.com/tc~monitoring~systeminfo*monitoring was already set to ticket
    The Authentication template for component sap.com/tc~monitoring~systeminfo*sap_monitoring was already set to ticket
    The Authentication template for component sap.com/com.sap.security.core.admin*useradmin was already set to ticket
    The Authentication template for component sap.com/tc~webadministrator~solmandiag*smd was already set to ticket
    The Authentication template for component sap.com/tc~smd~e2etraceupload*E2EClientTraceUploadW was already set to ticket
    The com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule already contained the entry : trustedsys=SMI, 001 trustediss=CN=SMI trusteddn=CN=SMI
    The Authentication template for component sap.com/tc~smd~EemAdminGateway*EemAdmin_Config1 has been set to evaluate_assertion_ticket
    The Login Module BasicPasswordLoginModule was added to the security component sap.com/tc~smd~EemAdminGateway*EemAdmin_Config1
    The ABAP instance profile contains the parameter : login/create_sso2_ticket=2
    Exception
    com.sap.mw.jco.JCO$AbapException: (126) FOREIGN_ENQUEUE_LOCK: FOREIGN_ENQUEUE_LOCK
    at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1512)
    at com.sap.mw.jco.JCO$Client.execute(JCO.java:3937)
    at com.sap.mw.jco.JCO$Client.execute(JCO.java:3570)
    at com.sap.sup.admin.setup.AbapSysRfcAdapter.addTrustedIssuer(AbapSysRfcAdapter.java:276)
    at com.sap.sup.admin.setup.AbapSysRfcAdapter.addTrustedIssuer(AbapSysRfcAdapter.java:249)
    at com.sap.sup.admin.setup.ManagingServices.setupDualStackSSO(ManagingServices.java:752)
    at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:564)
    at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:445)
    at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:674)
    at com.sap.sup.admin.setup.ws.SetupWrapper._diagSetup(SetupWrapper.java:279)
    at com.sap.sup.admin.setup.ws.SetupWrapper.diagSetup(SetupWrapper.java:21)
    at sun.reflect.GeneratedMethodAccessor2202.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:331)
    at com.sap.engine.services.webservices.runtime.JavaClassImplementationContainer.invokeMethod(JavaClassImplementationContainer.java:76)
    at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:174)
    at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:81)
    at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:90)
    at SoapServlet.doPost(SoapServlet.java:51)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Also , i have checked the note # 1008474   Diagnostics Setup Wizard uses wrong ABAP client.
    As mentioned in above note, i have checked in visual admin all settings are maintained correctly.
    RFC destination WEBADMIN & SOLMANDIAG is also working fine.
    please tel why i am getting Foreign Enquelock
    Regards,
    Gayathri.K

  • Publishing a Web ABAP Service with ABAP stack

    Hi,
    We are only running ABAP Stack (we don't have Java Stack) in a SAP ECC 6.0 version.
    We have a RFC (or BAPI), for instance BAPI_CUSTOMER_GETDETAIL.
    How could we publish a Web ABAP Service?
    Thanks.
    Regards,
    Marta.

    Hi,
    I think this could be possible,
    refer below links
    Working With Web Services From ABAP
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a4433436-0301-0010-f2a9-9281ad574054
    ABAP Web Services in the Real World
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/244e7923-0a01-0010-5887-fe0b0c6dbb8d
    Journal Part XIII: Developing ABAP WebServices
    /people/thomas.jung3/blog/2004/11/15/bsp-150-a-developer146s-journal-part-xiii-developing-abap-webservices
    SAP Network Blog: BSP a Developer's Journal Part XIV - Consuming WebServices with ABAP
    /people/thomas.jung3/blog/2004/11/17/bsp-a-developers-journal-part-xiv--consuming-webservices-with-abap
    Thanks
    Swarup

  • Unique ID in ABAP stack across all Envrionment.

    In ABAP Stack is there any table which uniquely identifies one interface mapping across all environments. The requirement is to get a unique ID in ABAP stack (this needs to be hard-coded in an ABAP mapping) which is common in all environment.
    There is a table SXMSPFADDRESS which is the master table for addresses in XI i.e. Party, Service, Interface and namespace, and has key address id that is used at many places in XI runtime. But the addressID is different in different environment and hence cant be used.

    Hi,
    maybe start with a description of the issue and we will try to help with some other idea ?
    Regards,
    Michal Krawczyk

  • How to get a dynamic receiver determination based on a table an SAP PI ABAP Stack

    Hello folks,
    currently I get stuck dealing with a problem about the receiver determination. Let me first describe the Problem: We are using to different SAP ERP- backend system in our test enviroment. But only of this systems is marked as current "actuall" test system. Every once in a while we need to switch between these two systems and mark the other one as the actual test system.
    This is the point were it get's a little bit time consuming for me: We have about 50 interfaces were I need to change the receiver from test system A to test system B or vice versa. So I thought about creating a more dynamic way to determine the actual test system:
    Therefore I have created a table on the ABAP stack of our PI (7.31 double stack) with just one field that holds the current test system. Now I would like to create a dynamic receiver determination where I call the RFC-function RFC_READ_TABLE. But how can I acess a table from the grapchical mapping of the pi which is stored on the PI?
    Is there mybe another fundamental way to retrieve the actuall test system within the mapping?

    You can go for enhanced receiver determination, where in you can determine the receiver system using a graphical mapping.
    Now in that graphical mapping, use the standard function " RFC Look up" and make a call to bapi and get the actual receiver system.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40b64ca6-b1e3-2b10-4c9b-c48234ccea35?QuickLink=index&…
    Step by Step guide to Explain Enhanced Receiver Determination - Application Server Infrastructure - SCN Wiki

  • How to restart single application server(ABAP Stack)without effecting users

    Hi Experts,
    I Want to restart  one application server(ABAP Stack) in my clustered environment with out effecting endusers. I believe can be done it by transfering users request to other application servers. Please let me know the steps to perform this activity.
    Cheers
    DV

    Hi,
    Yes, you need to wait for the users to disconnect from the app server and remove the server from the logon groups.
    You should also remove the batch processes with an operation mode switch.
    Beware also if you have HTTP applications and you use a web dispatcehr for load balancing.
    Regards,
    Olivier

  • SAP BW Bex 7.3 Queries not working with Enterprise Portal (EP) 7.3 ABAP stack only

    SAP BW Bex 7.3 Queries not working with Enterprise Portal (EP) 7.3 ABAP Stack
    Dear Portal Gurus,
    we want to integrate SAP BW Bex Queries 7.3 into an Enterprise Portal 7.3 EP ABAP Stack only installation.
    1) We have Done SSO between EP And BI System
    2) System Object is Created
    3) When we trying to create Iview of BEX 7.3 report, its executing that report on BI server, we don't have java stack on BI System
    4) We have updated the required table in Bi system for executing the report on EP
    5) RFC is OK, System Object Test is OK, Report is working independently from Business Explorer, but not working from EP
    There no irj services available on BI system, as it is only ABAP stack.
    Can anybody help us in achieving our requirement
    Thanks in advance
    Michael Wecker

    Hi Michael,
    To integrate portal with BI you need to perform BI Portal integration steps.
    Refer to a document link below for guidance purpose.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0a5216a-349c-2a10-9baf-9d4797349f6a?overridelayout=t…
    Ensure that you have performed all these relevant steps.
    Hope this helps.
    Regards,
    Deepak Kori

  • Calling a web service In Netweaver 7.0 abap stack through an external alias

    Hello,
    In CRM 2007 (Netweaver 7.0 abap stack SP 16), we have defined a web service from a module function using the wizard and configuring it with SOAMANAGER.
    This web service works great when calling it with the "official" URL, something like :
    http://host.domain:port/sap/bc/srt/rfc/sap/zwebservice/client/zoperation/zbinding
    We would like to use a more simple URL. So with SICF, I have created an external alias /zwebservice which points to the "official" URL.
    The problem is that it does not work. I get every time an HTTP 500 error code and an error Message
    u201CThe configuration of the http server is missingu201D.
    Do you think that it is possible to call a web service through an external alias ?
    Thanks in advance for any ideas or solution !
    Olivier

    Seems that no one has tried it...
    I close the question.

  • Installing Java add-in on ABAP Stack

    Hello Gurus,
    We have recently upgrade from SAP R/3 4.7 ext. 20 SR2 to ECC 6.0 SR3 on Solaris platform using Oracle 10g. We are on Non-unicode system and on Single Stack i.e. AS ABAP only.
    Now as new requirement comes up in organization, we need to install additional Java Stack on upgraded system. Please help me in provide some details to proceed further.
    1. Advantages of JAVA Stack (is there any performance issues after installing Java Stack?).
    2. How to install Java Stack with ABAP stack in Cluster Environment.
    Early response is highly appreciated.
    Regards,
    Kshitiz Goyal

    > We have recently upgrade from SAP R/3 4.7 ext. 20 SR2 to ECC 6.0 SR3 on Solaris platform using Oracle 10g. We are on Non-unicode system and on Single Stack i.e. AS ABAP only.
    >
    > Now as new requirement comes up in organization, we need to install additional Java Stack on upgraded system. Please help me in provide some details to proceed further.
    There are two issues here:
    a) double stack instances are deprecated, they shouldn't be installed any more. Install the Java instance as a separate SID, at best on a separate machine (or on a separate Solaris zone on the same machine). See Note 855534 - Dual Stack and SAP Business Suite 7
    b) Java stacks with non-Unicode backends are not supported (see Note 975768 - Deprecation of Java features with non-Unicode Backend)
    You may be able to technically install the Java AddIn with "some special DVD" but because your backend is non-Unicode this configuration would be unsupported.
    I highly suggest you first convert your system to Unicode before trying to connect them to a Java system.
    Markus

  • What are the pros and cons of installing java+abap stack for portal?

    Hi all,
      1.What are the pros and cons of installing java+abap stack for portal?
      2.what effect it does on the ume options to be choosen??
      3.for the purpose of integration of r3,bw and crm on portal and crm 4.0 60.2.3 business package which option of stack(java or abap or both)will be good option and which ume option while installation should be choosen?
    regards
    Rajendra

    Hi Rajendra,
    The NetWeaver Installation Master Guide offers some good scenarios on the pros and cons:
    https://websmp201.sapag.de/~sapidb/011000358700005412792005E.pdf
    In a nutshell:
    ABAP+JAVA
    Pros
    - Decrease # of servers required to administer the portal
    - Less costly
    Cons
    - Upgrades could be dependent on ABAP and Java release level
    - Additional load on the server due to ABAP stack
    - Limited scalability
    JAVA and ABAP on separate server
    Pros
    - Improved performance
    - Allows each system to be single-use purpose therefore downtime does not affect other components
    - More scalable
    Cons
    - Adds complexity to landscape
    - Additional costs
    Regards,
    Thomas Pham

  • Issue in portal after abap stack upgrade

    Hi,
    Except travel and expenditure, everything is working fine after abap stack upgrade.  we have restarted abap and portal 3-4 times, we use abap ume. we are  getting error:
    Portal runtime error.
    An exception occurred while processing your request. Send the exception ID to your portal administrator.
    Exception ID: 18:57_27/02/12_0004_16184750
    defaulttrace:
    \#39;&lt;System.Access.WAS.protocol&gt;://&lt;System.Access.WAS.hostname&gt;/sap/bc/webdynpro/&lt;WebDynproNamespace&gt;/&lt;WebDynproApplication&gt;/;sap-ext-sid=&lt;ESID[url_ENCODE]&gt;?sap-ep-iviewhandle=007&lt;ESID[HASH]&gt;&amp;sap-wd-configId=&lt;WebDynproConfiguration&gt;&amp;sap-ep-iviewid=&lt;IView.ShortID&gt;&amp;sap-ep-pcdunit=&lt;IView.PCDUnit.ShortID&gt;&amp;sap-client=&lt;System.client&gt;&amp;sap-language=&lt;Request.Language&gt;&amp;sap-accessibility=&lt;User.Accessibility[SAP_BOOL]&gt;&amp;sap-rtl=&lt;LAF.RightToLeft[SAP_BOOL]&gt;&amp;sap-ep-version=&lt;Portal.Version[url_ENCODE]&gt;&amp;sap-wd-tstamp=&lt;$TimeStamp&gt;&amp;&lt;FPNInfo[IF_false PROCESS_RECURSIVE]&gt;&amp;sap-explanation=&lt;User.Explanation[SAP_BOOL]&gt;&amp;&lt;StylesheetIntegration[IF_true PROCESS_RECURSIVE]&gt;&amp;&lt;Authentication&gt;&amp;&lt;DynamicParameter[PARAMETER_MAPPING PROCESS_RECURSIVE]&gt;&amp;&lt;ForwardParameters[QUERYSTRING]&gt;&amp;&lt;ApplicationParameter[PROCESS_RECURSIVE]&gt;&\#39;; the problem occured at position 310. Cannot process expression &lt;System.client&gt; because Invalid System Attribute:
    System:    &amp;\#39;SAP_LocalSystem&amp;\#39;,
    Attribute: &amp;\#39;client&amp;\#39;.
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         ... 29 more
    #1.5 #00144FF922BF006B00000028000021AF0004B9F256577D3A#1330350388639#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#J2EE_ADM_EDJ#73##ERPDEV_EDJ_16184750#J2EE_ADM_EDJ#d2df5090614511e1cbb100144ff922bf#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Java###07:16_27/02/12_0004_16184750
    [EXCEPTION]
    #1#com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &\#39;&lt;System.Access.WAS.protocol&gt;://&lt;System.Access.WAS.hostname&gt;/sap/bc/webdynpro/&lt;WebDynproNamespace&gt;/&lt;WebDynproApplication&gt;/;sap-ext-sid=&lt;ESID[url_ENCODE]&gt;?sap-ep-iviewhandle=007&lt;ESID[HASH]&gt;&amp;sap-wd-configId=&lt;WebDynproConfiguration&gt;&amp;sap-ep-iviewid=&lt;IView.ShortID&gt;&amp;sap-ep-pcdunit=&lt;IView.PCDUnit.ShortID&gt;&amp;sap-client=&lt;System.client&gt;&amp;sap-language=&lt;Request.Language&gt;&amp;sap-accessibility=&lt;User.Accessibility[SAP_BOOL]&gt;&amp;sap-rtl=&lt;LAF.RightToLeft[SAP_BOOL]&gt;&amp;sap-ep-version=&lt;Portal.Version[url_ENCODE]&gt;&amp;sap-wd-tstamp=&lt;$TimeStamp&gt;&amp;&lt;FPNInfo[IF_false PROCESS_RECURSIVE]&gt;&amp;sap-explanation=&lt;User.Explanation[SAP_BOOL]&gt;&amp;&lt;StylesheetIntegration[IF_true PROCESS_RECURSIVE]&gt;&amp;&lt;Authentication&gt;&amp;&lt;DynamicParameter[PARAMETER_MAPPING PROCESS_RECURSIVE]&gt;&amp;&lt;ForwardParameters[QUERYSTRING]&gt;&amp;&lt;ApplicationParameter[PROCESS_RECURSIVE]&gt;&\#39;; the problem occured at position 310. Cannot process expression &lt;System.client&gt; because Invalid System Attribute:
    System:    &amp;\#39;SAP_LocalSystem&amp;\#39;,
    Attribute: &amp;\#39;client&amp;\#39;.
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:235)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:541)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:430)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    #1.5 #00144FF922BF006A0000001E000021AF0004B9F25959F274#1330350439133#com.sap.mw.jco#sap.com/tcwddispwda#com.sap.mw.jco#ESSEMP2#288##ERPDEV_EDJ_16184750#ESSEMP2#907dd803614911e1968500144ff922bf#SAPEngine_Application_Thread[impl:3]_6##0#0#Info##Plain###[WD JCO API] WebDynproExtension.addClientPool(SAP_R3_SelfServiceGenerics_ESSEMP2_EN_useSSO_(J2EE16184700)ID1578814350DB10044082816827940554End_9513223) with lang 'EN' and languages vector {EN,EN}#
    #1.5 #00144FF922BF0062000016D7000021AF0004B9F26C7D264E#1330350760207#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736980#Plain###Error! The following problem(s) occurred  during request processing:#
    #1.5 #00144FF922BF0062000016D9000021AF0004B9F26C7D286A#1330350760208#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736980#Java###Error! Request failed due to failure of child requests#1#Request failed due to failure of child requests#
    #1.5 #00144FF922BF0062000016DB000021AF0004B9F26C7D2DAC#1330350760209#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Java###Request failed due to failure of child requests
    [EXCEPTION]
    #1#Request failed due to failure of child requests
         at com.sap.tc.cbs.server.dao.impl.Request.checkForFailedChildRequests(Request.java:494)
         at com.sap.tc.cbs.server.dao.impl.Request.capture(Request.java:398)
         at com.sap.tc.cbs.server.proc.RequestHandler.process(RequestHandler.java:138)
         at com.sap.tc.cbs.server.proc.RequestHandler.run(RequestHandler.java:121)
         at com.sap.tc.cbs.server.rt.threads.PerpetualRunnable.run(PerpetualRunnable.java:109)
    #1.5 #00144FF922BF006200001777000021AF0004B9F26FD235FC#1330350816114#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736988#Plain###            Error! The following problem(s) occurred  during request processing:#
    #1.5 #00144FF922BF006200001779000021AF0004B9F26FD23863#1330350816114#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eed5c7ef614411e1996800144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 207,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736988#Plain###            Error! The following error occurred during request processing:The build failed due to wrong or incomplete arguments, passed to the build tool.
    Please check CBS service parameters against manual.#
    #1.5 #00144FF922BF006600001720000021AF0004B9F26FFE4EC5#1330350819004#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##f556c50a614411e19dc200144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 208,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736987#Plain###            Error! The following problem(s) occurred  during request processing:#
    #1.5 #00144FF922BF006600001722000021AF0004B9F26FFE50DC#1330350819004#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##f556c50a614411e19dc200144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 208,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736987#Plain###            Error! The following error occurred during request processing:The build failed due to wrong or incomplete arguments, passed to the build tool.
    Please check CBS service parameters against manual.#
    #1.5 #00144FF922BF005F0000179B000021AF0004B9F2714FA0E9#1330350841110#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eeb712eb614411e1926f00144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 206,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736989#Plain###Error! The following problem(s) occurred  during request processing:#
    #1.5 #00144FF922BF005F0000179D000021AF0004B9F2714FA2FC#1330350841111#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eeb712eb614411e1926f00144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 206,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBSRequestLog/RequestProcessing/id1736989#Java###Error! Request failed due to failure of child requests#1#Request failed due to failure of child requests#
    #1.5 #00144FF922BF005F0000179F000021AF0004B9F2714FA854#1330350841111#com.sap.tc.cbs.server.proc.RequestHandler##com.sap.tc.cbs.server.proc.RequestHandler####n/a##eeb712eb614411e1926f00144ff922bf#Thread[SAPEngine_System_Thread[impl:5]_Group - 206,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Java###Request failed due to failure of child requests
    [EXCEPTION]
    #1#Request failed due to failure of child requests
         at com.sap.tc.cbs.server.dao.impl.Request.checkForFailedChildRequests(Request.java:494)
         at com.sap.tc.cbs.server.dao.impl.Request.capture(Request.java:398)
         at com.sap.tc.cbs.server.proc.RequestHandler.process(RequestHandler.java:138)
         at com.sap.tc.cbs.server.proc.RequestHandler.run(RequestHandler.java:121)
         at com.sap.tc.cbs.server.rt.threads.PerpetualRunnable.run(PerpetualRunnable.java:109)
    cbs.5:
    #1.5 #00144FF922BF006E00009D0900000EEE0004B9E196C2E0E9#1330278454976#/Applications/CBS/Service##com.sap.tc.cbs.server.rt.sync.AccessOrc####n/a##446ca3fd5c7b11e195a000144ff922bf#Thread[CBS AccessQueue Orchestrator,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Plain###Access orchestrator failure#
    #1.5 #00144FF922BF006E00009D1100000EEE0004B9E196C49580#1330278455088#/Applications/CBS/Service##com.sap.tc.cbs.server.rt.sync.AccessOrc####n/a##446ca3fd5c7b11e195a000144ff922bf#Thread[CBS AccessQueue Orchestrator,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Plain###Access orchestrator failure#
    #1.5 #00144FF922BF006E00009D1900000EEE0004B9E196C664FD#1330278455207#/Applications/CBS/Service##com.sap.tc.cbs.server.rt.sync.AccessOrc####n/a##446ca3fd5c7b11e195a000144ff922bf#Thread[CBS AccessQueue Orchestrator,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Plain###Access orchestrator failure#
    #1.5 #00144FF922BF006E00009D2100000EEE0004B9E196C81B65#1330278455319#/Applications/CBS/Service##com.sap.tc.cbs.server.rt.sync.AccessOrc####n/a##446ca3fd5c7b11e195a000144ff922bf#Thread[CBS AccessQueue Orchestrator,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Service#Plain###Access orchestrator failure#
    #1.5 #00144FF922BF00310000000000000DA90004B9F0155B9416#1330340708455#/Applications/CBS/Administration##com.sap.tc.cbs.service.CBSFrame#######SAPEngine_System_Thread[impl:5]_82##0#0#Info#1#com.sap.tc.cbs.service.CBSFrame#Java###Starting CBS service on node ...#1#16184750#
    Pls suggest

    Hi James Bond
    From the exception above, it can be seen that the AppIntegrator iView is trying to run on the "SAP_LocalSystem" where it should be running on a "real" backend system.
    Please check what is the System alias in this iView and make sure it points on a backend system which has the same alias in the Portal System landscape.
    Hope that helps,
    Robin Hood.

  • Issue in registering ABAP stack into SLD

    Hi all
    The issue is as shown below. I appreciate your help.
    Environment: SLD host-Windows Server 2003, Oracle 10g, WAS JAVA 640 SP19
    CRM ABAP+JAVA 640 host - unix, Oracle
    I was able to register CRM JAVA stack in SLD from Visual Administrator>SLD Data Supplier. The CIM Client Test was successfull.
    When i try to register the CRM ABAP stack from tcode RZ70, i get an error as below:
    SLD DS start program
        0: sapsrm_CRM_05                             : Execute program: SLDAPPL_SERV
        0: sapsrm_CRM_05                             : Execute program: SLDBCSYS
        0: sapsrm_CRM_05                             : Execute program: SLDCLIENT
        0: sapsrm_CRM_05                             : Execute program: SLDCOMPSYS
        0: sapsrm_CRM_05                             : Execute program: SLDDBSYS
        0: sapsrm_CRM_05                             : Execute program: SLDGWSRV
        0: sapsrm_CRM_05                             : Execute program: SLDINSTSC
        0: sapsrm_CRM_05                             : Execute program: SLDINSTSP
        0: sapsrm_CRM_05                             : Execute program: SLDIPSERV
        0: sapsrm_CRM_05                             : Execute program: SLDMSGSRV
        0: sapsrm_CRM_05                             : Execute program: SLDASSOC
        0: sapsrm_CRM_05                             : Collection of SLD data finished
        0: sapsrm_CRM_05                             : Data collected successfully
        0: sapsrm_CRM_05                             : RFC data prepared
        0: sapsrm_CRM_05                             : Used RFC destination: SLD_UC
        0: sapsrm_CRM_05                             : RFC call failed: / CPIC-CALL: 'ThSAPECMINIT' : cmRc=17 thRc=236#SAP gateway connection failed. Is SAP gateway started?
        0: sapsrm_CRM_05                             : Existing periodic jobs removed. Number: 1
        0: sapsrm_CRM_05                             : Program scheduled: 20080506 222324
        1: sapsrm_CRM_05                             : Event-controlled job already exists; scheduling not necessary
    I came to know from other forums in sdn that we need to install/configure separate gateway if the SLD is on a standalone JAVA engine.
    Also, in SM59 SLD_UC, SLD_NUC, SAPSLDAPI are failing with the same error of "RFC call failed: / CPIC-CALL: 'ThSAPECMINIT' : cmRc=17 thRc=236#SAP gateway connection failed. Is SAP gateway started?"
    Please suggest how to resolve this. Please let me know if you need more details.
    Thanks already
    Edited by: Rahul Paul Patchigondla on May 6, 2008 9:57 AM

    Rahul,
    as RK already stated: the SLD has to connect to an SAP gateway, such is running on an ABAP system.
    You may initially try to use the SAP gateway from the CRM ABAP stack. Therefore you will have to adjust the SLD to use that SAP gateway. On 6.40 SLD: Administration / Data supplier bridge / RFC gateway: Server (host name) and Service (combination of sapgw and instance number of CRM ABAP system).
    After that, in CRM SM59 SLD_UC, SLD_NUC, SAPSLDAPI will have to be adjusted accordingly.
    Regards, Boris

  • System Copy from ABAP Stack to ABAP+Java Stack

    Hi,
    Is it possible to system copy (homogeneous or heterogeneous) from a system based on ABAP Stack to a system based on ABAP+Java Stack? Is it the normal system copy procedure or something aditional is required to do. Pl. advise. Thanks
    regards
    Edited by: Abdus Samad on Oct 24, 2008 8:13 AM

    It depends on what you want to copy, a system copy will always wipe out the existing target. But if you want to only copy data, you might be able to do a client copy. You can start with this SAP note: [552711 - FAQ: Client copy|https://service.sap.com/sap/bc/bsp/spn/sapnotes/index2.htm?numm=552711]
    Regards Michael

Maybe you are looking for