Skip to Content
avatar image
Former Member

JCo destination/ SLD configuration/ message server GRANT POINTS!

Hi,

I am trying to create JCo Destination, using wizard when I get to the point 3.2 (message server) I do not have my message server listed in the drop down list, althogh it is up running on port 3601.

Here is an error message I ve got at the end.

SLD Data supplier service running and I have HTTP and RFC configuration in place

Thanks Denis

Failed to create new JCO client connection HR_Human_Resouces_Test: com.sap.lcr.api.cimclient.LcrException: CIM_ERR_ALREADY_EXISTS: Instance already exists: SAP_MsgServJCODestination.CreationClassName="SAP_MsgServJCODestination",Name="HR_Human_Resouces_Test",SystemCreationClassName="SAP_J2EEEngineCluster",SystemName="DE1.SystemHome.sbdevsqlsap2" at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.raiseExceptionOnError(SimpleResponseAnalyser.java:120) at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.getIResult(SimpleResponseAnalyser.java:53) at com.sap.lcr.api.cimclient.CIMOMClient.sendImpl(CIMOMClient.java:215) at com.sap.lcr.api.cimclient.CIMOMClient.send(CIMOMClient.java:147) at com.sap.lcr.api.cimclient.CIMOMClient.createInstanceImpl(CIMOMClient.java:660) at com.sap.lcr.api.cimclient.CIMOMClient.createInstance(CIMOMClient.java:642) at com.sap.lcr.api.cimclient.CIMClient.createInstance(CIMClient.java:730) at com.sap.lcr.api.sapmodel.JavaCIMObjectAccessor.createInstance(JavaCIMObjectAccessor.java:44) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:283) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:649) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) 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:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) 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:95) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

6 Answers

  • avatar image
    Former Member
    May 29, 2006 at 05:27 PM

    You need to define the System as a technical system in SLD . Then only the dropdown list is populated.

    Add comment
    10|10000 characters needed characters exceeded

    • Hi

      1) First create in SLD (HTTP://<localhost>:<port>/sld) under system catalog >> technical system

      2) Create JCO , provide all backend configuration (like system id, client, user name & pwd) . you check the connection like ping & test.

      I think it goes well

      Cheers

      Jawahar Govindaraj

  • avatar image
    Former Member
    May 29, 2006 at 07:26 PM

    Jawahar,

    I created Technical system Web AS for Java, Tech system looks good to me, is there a way to test Tech system ?

    Thanks

    BTW I could not create Web AS for ABAP, when I use wizard at the end I get this Error message "Please select at least one product" and there is non

    Any ideas?

    Denis

    Add comment
    10|10000 characters needed characters exceeded

    • Hi

      Which system your connecting ? if it is SAP R/3, then you need to crete under WebAS ABAP.

      For testing the Jco & SLD,

      Go to adming page http://<localhost>:<port> >>click Web Dynpro >>Content admin >> create, maintain, test Jco and also you can Test the SLD connection too

      Cheers

      Jawahar Govindaraj

      PS: Reward points

  • avatar image
    Former Member
    May 30, 2006 at 03:17 PM

    Guys, thanks a lot for ALL of YOU!!!

    I was missing Tech system Web AS for ABAP and I couldn't create it because I didn't import CIM components. So when I imported it I couuld create Tech system and JCo desctination, I still have a problem to connect to Message server, here is what i get when I am trying to test my JCo destination:

    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=sbdevep GROUP=PUBLIC R3NAME=DE1 MSSERV=sapmsDE1 PCS=1 ERROR Group PUBLIC not found TIME Tue May 30 11:02:27 2006 RELEASE 640 COMPONENT LG VERSION 5 RC -6 MODULE lgxx.c LINE 3498 DETAIL LgIGroup COUNTER 1

    I created Public Logon Group using SMLG transaction, and it is activated

    When I created Web AS for ABAP, at the very end when Wizard prompts to choose at least one product from the list I added SAP ECC 5.0, I want to implement ESS 60.1 webdynpro based business package. Do I need to choose any other products from the list for ESS ?

    Any ideas what is missing or might be wrong with Message server connectivity based on the error message above?

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 03, 2006 at 11:24 AM

    I have the similar problem (currently unsolved).

    welcome to jco-destination-sld-configuration-message-server-g

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 14, 2007 at 11:53 AM

    thank u

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 14, 2007 at 12:03 PM

    Hi Denis,

    The below is the Wiki which i have created, please go through the notes.

    Configure SLD for JCo and Creation of JCo Destinations

    To create JCo connections you need to configure SLD (System Landscape Directory) first and then create JCo destinations.

    First let’s see as how to configure SLD.

    Start Visual Administrator.

    To start it

    1) Go to Server Installed path i.e. usr\sap\<systemid>\<systeminstance>\J2ee\admin

    2) Choose go.bat and start it.

    3) Under Global Server Configuration, choose <Serverid>.

    4) Choose Services under it.

    5) Find SLD Data Supplier.

    6) Under System Landscape Directory select HTTP Settings.

    7) Give all the required fields like Host Name, Port Number, User Name and Password.

    8) Similarly choose CIM Client Generation Settings and give Host Name, Port Number, User Name and Password.

    9) You can test the SLD is configured properly or not. Just click CIM Client Test.

    10) Save the settings and close Visual Administrator.

    Now that you have configured SLD through Visual Administrator, we can create JCo Connections. To create JCo connections

    1) You will need Super Administrator permissions to create JCo’s.

    2) Log on to the Portal.

    3) Go to Content Administration &#61664; Web Dynpro

    4) Since we have configured SLD, now we can see a button to “Create JCo Destination”. Click it

    5) Now you can observe Create new JCo Destination on right side panel.

    6) Give the Following Details.

    a) General Data:

    Name: Give the name of JCo

    Client: Give the Client number to which system you want to create JCo for. Click Next.

    b) J2EE Cluster: Check the Use Local J2EE engine. Click Next.

    c) Connection Type: Select Dictionary Meta Data. Click Next.

    d) Application Server Connection: Select the existing Message Server and Logon Group.

    It might sometimes happen that Message Server and Logon Group is not configured to configure them, follow the process

    For Message Server:

    i. Log on to SDL through portal i.e. http://<servername>:<portnumber>/sld

    ii. Choose Technical System. Click it.

    iii. You will observe New Technical System button, click it.

    iv. System Type: Select Web AS ABAP , if you want to connect to R/3 System and incase you are using Java application use Web AS Java

    v. General: Log on to R/3 System through SAP Log on pad. Go to System &#61664; Status, check for SID, Installation Number and Database Host Name.

    vi. Central Servers: Give Host Name and Port Number and Instance Number.

    For Logon Group:

    i. Click on Add New Logon Group, this will open a row in the table.

    ii. Log on to R/3 through Logon pad and get Logon Groups ids and the transaction code is “SMLG”.

    vii. Application Servers: Click on Add Application Server and then give Host Name and Instance Number of R/3 System.

    viii. Clients: Give Client number (System id) and Logical Client Name (which we can get from SMLG code). And click finish.

    7) Message Server Connection:

    i. Name: Give the logon name of R/3 System

    ii. Password & Confirm Password: Give appropriate password of R/3 System.

    8) Click Finish.

    regards

    Anil

    Add comment
    10|10000 characters needed characters exceeded