Problems creating JCO connector

We are having some problems when attempting to follow the steps indicated in the Post-Installation Slide Deck of RAR version 5.3. In step 4 (Create JCO Connectors) we are not able to create a new JCO connector associated with the given models in the WebDynpro Content Administrator. The "create" button displayed next to each model is disabled and the status indicated is "Status Unknown" (gray color).
When we test the SLD connection it is pointing to the default URL,  while a different URL was specified during installation given an SLD already existed previous to SAP GRC installation.
Any ideas of where we need to be looking in order to fix this?

Hi Pablo,
This happens because your SLD bridge is not configured correctly ,
Please follow the steps as under :
Login to  Visual Administrator.
Expand Navigation menu under J2EE Server Name ,
Expand Services List
Click On SLD Data Suppllier
Click On http settings tab
Enter Host name and port number , user name /password for your system connection.
Click Save.
Click on CIM Client Generation settings tabs
Enter host name port , user account details you entered in http settings tab .
Click Save.
Click Supplier ( data transfer)icon on top of pane to transfer data information you have entered in sld supplier.
A pop up window appears  " trigger SLD data transfer" )
Click = yes.
A pop-up with appear indicating transfer successful.
If this window does not appear , then SLD needs to be configured properly,
launch http://<hostname>:<portnumber>/sld
Click on Administration > Initial setup
Fill in values for :
Object server name :Name of computer <SPACE> 1
E.g AG500900A 1
Gate way host : Name of computer as above.
gateway port : portnumber as used in URL .
Import software catalog check box = OK
Import SLD objects
(close to 95791 objects need to get imported , wait for sometime till they are imported )
After importing is done , refresh once.
This should resolve, however if you still face it then setup technical system at
http://<hostname>:<portnumber>/sld
HOME > Techinical systems .
Click new technical system
Select webas ABAP
the details need to be fetched from SAP R/3 system for which JCO is to be created.
thnks

Similar Messages

  • Problem creating JCo rfcs

    Hi,
    I want to create JCo rfcs in systems.
    But confused between these functionalities :
    1> JCo rfc prvider : This is present in Visual Admin and is used to register J2EE engine as rfc destination.
    2> Maintain JCo connection : This is present in content admin in WebDynpro tool. Here we can provide details.
    Whats the difference between two and which is to be used when?
    Thanks

    Hi,
    JCo RFC Provider Service:
    The RFC is an SAP interface protocol, which simplifies the programming of communication processes between systems. The RFCs enable you to call and execute predefined functions in a remote system, or in the same system. The RFCs manage the communication process, parameter transfer, and error handling.
    In the J2EE Engine the RFC functions are implemented by the JCo RFC Provider service, which is used for processing ABAP to Java requests. A feature is provided for receiving calls from the SAP systems u2013 this is done by registering the J2EE Engine as a RFC destination.
    The JCo RFC Provider Service processes calls from the SAP systems. It dispatches the calls to a stateless session bean, which is registered in the J2EE Engine naming system. By naming convention the JNDI name used is identical to the name of the SAP function module.
    Technically, the service is based on the JCo (SAP Java Connector).
    Please refer the sap help link:
    http://help.sap.com/saphelp_nw04/helpdata/en/6a/82343ecc7f892ee10000000a114084/content.htm
    What is JCo connection and use please refer the following URL:
    http://wiki.sdn.sap.com/wiki/display/Java/JCO+Connection

  • Problems creating JCO Connections

    Hi experts,
    I have a question regarding the JCO Connection creation in Content Administrator.
    My first doubt is if it's necessary to create each JCO Connection for each backend system that I'll run RFC functions?
    If is it true, during Creation I must specify user and password. I have to specify the Backend User and Pass, right?
    Finally, could you explain me why there are several JCO connections created?
    When I create the JCO connection I will be able to invoque Backend RFC functions from, for example, a webdynpro?
    Kind Regards,
    Martin.

    Hi Martin,
    1. Yes, provided you want to use the RFC functionality.
    2. Yes, you would be giving the username and password for the metadata.
    Please refer to [Creating JCo Destinations|http://help.sap.com/saphelp_nw70/helpdata/EN/3a/3b1b40fcdd8f5ce10000000a155106/frameset.htm]
    3.Generally, when you install business packages like ESS MSS etc, there are a bunch of JCO which are installed as well, but all you would have to do is edit its properties and point them to the correct location.
    4. Yes, you can.
    Regards,
    Sandeep Tudumu

  • Problem create jco connection in webdynpro application run time

    Hi There,
    I created webdynpro application using rfc model.
    After deploy the project , i created two jco connection
    for data & meta data this is work o.k (test with no errors). the sld is o.k.
    We are using application server (Single Server) for data
    & message server for meta data (Load Balance).
    During run time there is an error message:
    Error stacktrace:
    com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type com.ness.crm.customerlasttwo01pckg.model.types.Datab could not be loaded: com.sap.dictionary.runtime.DdException:
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:205)
         at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:471)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:771)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:756)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:433)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:371)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:400)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:138)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:746)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
         at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:134)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:374)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
         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.doGet(DispatcherServlet.java:48)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         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:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Caused by: com.sap.dictionary.runtime.DdException:
         at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:225)
         at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:180)
         at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:78)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:64)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:39)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
         at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:234)
         ... 44 more
    <u>Can some one help me with this matter?</u>
    Best regards Nir Shohat.

    Hi Nir,
    We also had same problem but no we won't. Check ur config on SLD again and the try to the test connection from the http://localhost:4444/webdynpro ( WAS 6.4 )server.
    If this connection is OK then deploy some small application n see.
    Is ur's JCo connection working for J2ee application?
    Arnigs

  • Problem creating JCo

    I'm having problems configuring the SLD and creating the JCo.
    I'm using a RFC model from a R3 server that is not on the same network of my WEB AS. I want to configure the SLD using the IP address, but it only accepts the hostname.
    There's a way I can configure the SLD with the IP address??.
    Thank you.

    Hi Joaquin,
    did you solve your problem by yourself and/or was Gregor's answer helpful for you? In the latter case, don't forget to reward some points for Gregor's answer.
    Regards
    Stefan

  • Problem creating logical connector

    Hello,
    I would like to create an Event-driven Process Chain Modeler.
    I started by creating Events and Functions (See the attachement metamodel)
    Then, I started to create also additional connectors.But, I found a problem because I couldn't add the additional connector (AND) in the diagram.
    The design file seems completed to me but I can't see how to I add the connector AND for example to the diagram.
    please could you help me with this
    Thanks

    Thanks for you reply.
    Yes, I understand that adding a DISCONNECT FROM SESSION will cause the recovery to work in the background
    However , I waited 24 hours and no change
    this is my test database , completely idle, so there is no massive recovery going on
    When I issued :
    select timestamp, message from v$dataguard_status
    I got :
    23-MAR-09
    Media Recovery Waiting for thread 1 sequence 76
    and also :
    SQL> SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS
    2 FROM V$MANAGED_STANDBY;
    PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    MRP0 WAIT_FOR_LOG 1 76 0 0
    I did notice that this archive log #76 was not transferred and when I query in the primary DB :
    SQL> select recovery_mode from V$ARCHIVE_DEST_STATUS ;
    RECOVERY_MODE
    IDLE
    UNKNOWN
    IDLE
    IDLE
    IDLE
    IDLE
    IDLE
    IDLE
    IDLE
    IDLE
    Looks like something went wrong during my logical standby configuration, but I cannot figure out what exactly
    The physical satandby was working fine.
    thanks in advance for any help
    Orna

  • SLD problem while creating JCO

    Hi all,
               I am creating JCO from WebDynpro Content Administration for a RFC model but when I go to JCO connections it don't allow me to create. The link is disabled and when I "check SLD" it gives error "Connection to System Landscape Directory (SLD) could not opended successfully"
    can any one help me in this?
    Thanks
    Ninad

    Hi,
    You can check and modify the SLD configuration settings of the J2EE Engine using the Visual Administrator. Log on as an administrator user and double click on Server  ->  Services  ->  SLD Data Supplier.
    Switch to tab CIM Client Generation Settings. If the HTTP connection parameters host, port, user and password are not set, then the SLD is not configured to be used by Web Dynpro applications. Configure the parameters with the values of the central SLD system and save the configuration. Select CIMClient Test to test if the configuration data is correct and the connection to SLD could be established.
    http://help.sap.com/saphelp_nw04/helpdata/en/f4/1a1041a0f6f16fe10000000a1550b0/frameset.htm
    Regards
    Ayyapparaj

  • Error while creating new connector in GRC CUP 5.3

    Hi,
    I am  trying to create a new SAP Connector in CUP 5.3, when i fill in all the fields in the new connection and select  "Test Connection" it says Connection successful and when i save it and look at the Available connectors, i am unable to see my new connector there.
    Does anyone know why is this happening.
    a quick response is appriciated.
    Thanks.
    Edited by: Chaitanya Pallapotu on Jul 14, 2009 9:17 PM

    Hi Chetan,
    I have the same issue when configuring connectors in CUP. I solved it in this way:
    1- Go to RAR(Risk, Analysis and Remediation) --> Configuration --> Connector --> Search
    2- Select one of the connectors and write down the values in the list box of the field JCO Destination.
    3 - Now, go to CUP, and create the connector using the names writed down in step 2.
    CUP will warn you with an error, ignore it,  and then save the connector.
    Note: when creating the connector in CUP, fill the fields, then save/create(here you will have the error msg), then Test Connection, and then save again.
    That works for me!!!
    PD: Always log in to GRC with the same language configured in CUP.
    Hope this works for you!!!

  • Message Servers not appearing when creating JCO Destination

    Hello Experts,
    I had created a  System Object in the Portal system landscape based on System Template (Template) and choosed SAP system with load balancing (to connect to R/3 server).
    Given parameters to Connector, ITS, WAS and User management, when i test the connection test on these settings, All are successful except the connector settings. but when run the transaction code(System Administration -> support-> portal runtime-> SAP Transaction) by selecting this message server, it is executing.
    And i want this message server to be selected when creating JCO destination.
    This System Object is not showing in the message servers dropdown box selection when creating the JCO destinations.
    What may be the issue.
    Could anyone help me in solving this.
    Thanks in advance
    Regards
    Sunil

    Hi,
    Have you checked the Technical systems in the SLD ?   When you click on check sld , you appear an SLD url ,,,
    Typing the same URL in browser and loging inwith SLD USER .... have you seen all the technical system which you want to appear while creating the JCO's ..
    Regards,
    Srini

  • JCO Connector

    Hi,
    Can anyone explain functionlity of JCO Connector ?
    Can we use java code in abap ?
    In which editor ?
    Bye,
    Satya.

    Hi Satyanarayana,
    <b>SAP Java Connector - Excample 1: Simple RFC call
    Scenario
    We will call the RFC function module ZNAS_HIE1_GET_MEMBER_FARM.that returns members that have owned a farm. Input to the function is a farm number, and output is a table of members that have owned the farm and Owner number (Sequence number of owners).
    Class testJCO is excuted and calls class GetMemberFarm method GetMemberFarmFromSap. Input parameters to GetMemberFarm are Farm and Owner number.
    GetMemberFarmFromSap executes RFC ZNAS_HIE1_GET_MEMBER_FARM, that returns a table of members that have owned the farm from the input parameters.
    GetMemberFarmFromSap loops through the table and finds the member where ZZCHCODE (Owner numer), is equal owner number from the input-parameters. and returns the member.
    Code
    Class testJCO
    public class testJco
         public static void main(String[] args)
              GetMemberFarm testGetMemberFarm = new GetMemberFarm();
              String memberFarm= testGetMemberFarm.GetMemberFarmFromSap("0111020155","02");
              System.out.println("Memberfarm: " + memberFarm);
    Class GetMemberFram
    import com.sap.mw.jco.*;  //The JCO
    public class GetMemberFarm {
      public String GetMemberFarmFromSap(String farm, String OwnerNumber)   
      {  String zzmemb ="";
            String memberFarm = "";
         JCO.Repository mRepository;
         JCO.Client mConnection = null;
         JCO.Function myFunction = null;
         //Create Connection to SAP
           try
                mConnection = JCO.createClient("800",           //SAP client
                                            "HFR",       //User ID
                                            "vimmer3",     //Password
                                            "EN",            //Language
                                            "53.205.22.71", //Host
                                            "03");           //System
             mConnection.connect();
             System.out.println("Connection OK");
           catch (Exception ex)
                System.out.println(ex);
          // Create function and parameters
          try
            //Create repository
            mRepository = new JCO.Repository( "GetMember", mConnection );
            //Get a function template from the repository
            IFunctionTemplate ftemplate = mRepository.getFunctionTemplate("ZNAS_HIE1_GET_MEMBER_FARM");
            //Create function
            myFunction = new JCO.Function(ftemplate);
            System.out.println("Function created");
            //Set import parameter
            JCO.Field zzfarm = myFunction.getImportParameterList().getField("ZZFARM");
            zzfarm.setValue(farm);
            System.out.println("Parameters ok");
         catch (Exception ex)       
              System.out.println(ex);
         // Execute function
         try
              mConnection.execute(myFunction);
            System.out.println("RFC Call OK");          
         catch (Exception ex)      
          {  System.out.println(ex); //Exception from function          
         // Handle return table GT_HIERARCHY
         // Loop over the table and find the record that
         // has ZZCHCODE = OwnerNumber from the
         // method parameters, and return Member for the
         // record
         JCO.Table gt_HIERARCHY = null;
         try
              gt_HIERARCHY=myFunction.getTableParameterList().getTable("GT_HIERARCHY");
              //Loop thhrough table and return the member that has
              // changecode (ZZCHCODE) = 02
              for (int i = 0; i < gt_HIERARCHY.getNumRows(); i++)
              {   gt_HIERARCHY.setRow(i);
                  String zzchcode = gt_HIERARCHY.getString("ZZCHCODE");
                  if (zzchcode.equals(OwnerNumber))                        
                       zzmemb = gt_HIERARCHY.getString("ZZMEMB");                   
         catch (Exception ex)      
          {  System.out.println(ex);           
         // Disconnect from SAP
         try
             mConnection.disconnect();  
             System.out.println("Disconnected from SAP");
          catch (Exception ex)
               System.out.println(ex);
          return zzmemb;
    } //public class GetMemberFarm
    Example: 2
    SAP Java Connector - Example 3: Create Salesorder
    This example shows how to make a sales order using the SAP java Connector and BAPI_SALESORDER_CREATEFROMDAT2. First the ABAP code for using the BAPI is shown, and next the Java implementation is shown.
    ABAP Example
    REPORT z_bapi_create_sales_order_test .
    Order header:
    - Order type: OR  Important you must use the german code TA
    - Sales org: 1000
    - Distrb. chan.: 10
    - Division: 00
    - Sold to party: 1032
    - Ship to party: 1032
    - Purch order: DG-19970626-3
    Order item:
    - Material: P-100
    - Qty: 1
    DATA:
    Order partners
    li_order_partners    TYPE STANDARD TABLE OF bapiparnr,
    l_order_partners     LIKE bapiparnr,
    Structures for order header
    l_order_header_in    LIKE bapisdhd1,
    l_order_header_inx   LIKE bapisdhd1x,
    Tables for order items
    li_order_items_in    TYPE STANDARD TABLE OF bapisditm,
    l_order_items_in     LIKE bapisditm,
    li_order_items_inx   TYPE STANDARD TABLE OF bapisditmx,
    l_order_items_inx    LIKE bapisditmx,
    Return table from bapi call
    li_return TYPE STANDARD TABLE OF bapiret2,
    l_return  TYPE bapiret2,
    Sales document number
      l_vbeln LIKE bapivbeln-vbeln,
    Error flag
      l_errflag(1) TYPE c.
    START-OF-SELECTION.
    Build partner information
      CLEAR l_order_partners.
      l_order_partners-partn_role = 'AG'.          "Remember German codes !
      l_order_partners-partn_numb = '0000001032'.
      APPEND l_order_partners TO li_order_partners.
    Build order header
    Update flag
      l_order_header_inx-updateflag = 'I'.
    Sales document type
      l_order_header_in-doc_type    = 'TA'.        "Remember German codes !
      l_order_header_inx-doc_type   = 'X'.
    Sales organization
      l_order_header_in-sales_org  = '1000'.
      l_order_header_inx-sales_org  = 'X'.
    Distribution channel
      l_order_header_in-distr_chan = '10'.
      l_order_header_inx-distr_chan = 'X'.
    Division
      l_order_header_in-division = '00'.
      l_order_header_inx-division = 'X'.
    Purchase order
      l_order_header_in-purch_no_c = 'DG-19970626-300'.
      l_order_header_inx-purch_no_c = 'X'.
    Build order item(s) - Only 1 is used in this example
      l_order_items_in-itm_number = '10'.
      l_order_items_inx-itm_number = '10'.
      l_order_items_in-material = 'P-100'.
      l_order_items_inx-material = 'X'.
      l_order_items_in-comp_quant = '1.000'.
      l_order_items_inx-comp_quant = 'X'.
      APPEND l_order_items_in TO li_order_items_in.
      l_order_items_inx-updateflag = 'I'.
      APPEND l_order_items_inx TO li_order_items_inx.
    CALL Bapi
      CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
           EXPORTING
                order_header_in  = l_order_header_in
                order_header_inx = l_order_header_inx
                testrun          = 'X'
           IMPORTING
                salesdocument    = l_vbeln
           TABLES
                return           = li_return
                order_items_in   = li_order_items_in
                order_items_inx  = li_order_items_inx
                order_partners   = li_order_partners.
    END-OF-SELECTION.
    Check and write Return table
      CLEAR l_errflag.
      WRITE: / 'Sales dcoument: ', l_vbeln.
      LOOP AT li_return INTO l_return.
        WRITE: / l_return-type, l_return-message(50).
        IF l_return-type = 'E'.
          l_errflag = 'X'.
        ENDIF.
      ENDLOOP.
    No errors - Commit
      IF l_errflag  IS INITIAL.
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
      ENDIF.</b>
    Good Luck and thanks
    AK

  • Buttons disabled while creating JCO- SLD configured in solman

    Hi All,
    I have configured SLD in solman.And I have made relevant entries in Visual Administrator also.
    When I try to create jco in my portal,all buttons are disabled.
    I had faced this problem when I had configured SLD in portal itself and that got resolved after I searched through the forum.
    But here I have no clue where i am going wrong.
    Regards
    Akshaya

    Hi,
    Check all these in VA.
    Go to Visual Composer
    1)Make new Connecion
    a)User name->
    b)Host ->
    c)Port->50004
    Goto cluster ->got to server->services->sld Data supplier.
    Set RFC Settings
    a)Gateway Host ->ip of ep
    b)GateWay service/port->sapgw00/3300
    CIM client generation settings
    Host->ip address of ep
    Port ->50000
    user->
    Set Http Settings
    Host->ip of ep
    port->50000
    user->j2ee_admin
    Do these steps  and check the CIM generation has displayed successfully or not.?
    It might helps you.

  • Problem configure JCO

    Hello Dear Expert.
    I am new in Web dynpro Java and I have an application in Web dynpro java which is been used in productive system for a custommer C1 for certain reason  the same custommer need the same application is reeconfigured in other portal Server, when  I
    made deploy in the new Portal Server i got the exception:
         Exception while creating JCo client connection Failed to create new JCO client connection WD_NATTURA_COTIZACIONES_DATA_DEST: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Connection WD_NATTURA_COTIZACIONES_DATA_DEST already exists in the SLD. Please choose another name. at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:263) 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:265) 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.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53) 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: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(AccessController.java:219) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    The problem is that name of CJO is already exist in the SDL, that is correct beacuse this application is going to be used the same SLd in order to connect to the same SAP Systema QAS, Prod respectivelly.
    How can i solve this problem, my intention is to have only 1 application Wd java with two deferents JCO destiny independent to avoid any change in the code afeact the deploy which is in productivo.
    How can i managed this situation.
    Thanks a lot for helping me.

    Hello,
    There is no such option to use two JCo for a single WD Application as per your requirement. You can try with below two things
    1. Create another model with another JCo name. Which took more effort to change the source code wherever you used the Model.
    2. In your Production system delete/deactivate the old JCo (if possible) then deploy your application. Then it will create the JCo same as before. And if other applications are also using the same JCo there should not be any problem once they are newly created.
    Thanks
    Shankha

  • Exception while creating JCO destinations

    Hello,
    I have deevloped a webdynpro application as a local DC and trying to deploy and run it. While doing this step it throws an exception as "NullPointerException" when i click on create JCO connection.
    The error details are like :
    "at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
        at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)"
    Can anyone please help me how to resolve this problem.
    Thanks.
    - points rewarded for helpful solution

    Hi,
    The Following Procedure Follow  To Create JCO Destinations.
    First You Configure SLD Correctly.If You Have ECC And BW.You Maintaing Two WEBAS ABAP Systems.
    You Create WEB AS ABAP System In SLD And Maintain Connection Properties Of ECC.And
    Similarly For BW Also.
    If You Want To Create JCO Destinations.You Go To Login Portal
    Content Administration->Webdynpro->Create JCO Destinatiion
    A.General Data -> Specify Model Name,Client And JCO Pool Configuration
    B.Specify J2EEE Cluster
    C.Destination type
    Data Type-> Application DataModel,Dictionary MetaDataMetadata
    Destination Type->Load Balancing Or Single Server
    D.Specify Either Application Server Or Message Server
    E.SecurityUsername,password,confirm password,language
    F.SummaryWhole Information
    Similarly Metadata Created Follow Same Steps As Above
    After Creating JCO Destinations, Go For Maintain JCO Destination And test The JCO Destinations Works Fine Or Not you Con Test.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/user-interface-technology/webdynpro/wd%20java/portal%20integration/how%20to%20use%20the%20web%20dynpro%20content%20administrator.pdf
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/85a483cb-0d01-0010-2990-c5168f01ce8a
    http://help.sap.com/saphelp_nw04/helpdata/en/77/931440a1c32402e10000000a1550b0/frameset.htm
    The Given Below Links To Help You SLD Cofiguration For J2EE
    http://www.*********************/solution_manager/solution_manager_sld.html
    SLD Configuration
    It's Useful Rewards Points
    Bye
    Thanks
    SubbaRao

  • Problem to JCO after configure ModelData

    Hello dear Experts.
    I have a DC Web dynpor java when i depploy my DC and tray to configure the ModelData at the end of the  asisstant of creating this when i press button finish i got the next error:
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       java.lang.NullPointerException
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
        at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:485)
        at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.updateJCOClientStatus(JCOConnectionsDetails.java:481)
        at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:700)
        at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:664)
        ... 39 more
    If i enter to the Portal content Studio in order to configure this JCO again i got the same exception We have to restart server
    to enter to the JCO maintenance of content portal studio.
    I am sstuck in this problem.
    Thanks for helping me.

    Hi,
    Please look at these links for that
    [Problem to JCO After Configure ModelData|http://www.qnasap.com/problem-to-jco-after-configure-modeldata/] and [Null pointer while maintaining JCO destination|Null pointer while maintaining JCO destination;
    Hope this is help full for you,
    Regards
    Vijay

  • Can not create jco destination  500   Internal Server Error  after sp 13

    hi friends
    i have strange problem in my landscape with webdynpro -
    >Web Dynpro Tool Applications----->Content Administrator  -
    >login as  j2ee_admin  in 
    Web Dynpro Content Administrator  page  when start click on  ceartin Jco destination  i am facing this problem  -
    >6
    1. i can not create any  jco destination .
    2. is there any other  way to create jco destination to back end (arfc connection to retrive the back end data .
    3 . we are using one meta and one model data for all the application in my enviroment we do have some performance issus because one arfc connection is it correct?
    4 . what is best scanario to our applications(bussiness package ) we do have 30 diffrent application can i
    have 30 arfc connections .
    5.with  one arfc how much data can i retive per 1 min is there any performance tunning docment is there for the  ep tunning .
    <6>error is showing like this
    500   Internal Server Error
      SAP NetWeaver Application Server 7.00/Java AS 7.00 
    Failed to process request. Please contact your system administrator.
    [Hide]
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       java.lang.NullPointerException
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
        at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:285)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:250)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:157)
        ... 45 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
    Version null
    DOM version null
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:13:14[UTC], changelist=455669, host=pwdfm101), build date: Sat May 24 22:16:36 PKT 2008
    J2EE Engine 7.00 patchlevel 109044.44
    Java VM IBM J9 VM, version:2.3, vendor: IBM Corporation
    Operating system AIX, version: 5.3, architecture: ppc64
    Session & Other
    Session Locale en_US
    Time of Failure Thu Jul 03 01:56:32 PKT 2008 (Java Time: 1215032192285)
    Web Dynpro Code Generation Infos
    sap.com/tcwdtools
    No information available null
    sap.com/tcwddispwda
    No information available null
    sap.com/tcwdcorecomp
    No information available null
    Detailed Error Information
    Detailed Exception Chain
    java.lang.NullPointerException
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
         at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:285)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:250)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:157)
         at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:236)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
         at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:789)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:296)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:767)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:881)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:313)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         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:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         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(AccessController.java:215)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    thanks in advance  to all the friends spending there valuable time to read this thread
    any  suggtions  are realy help for my issue
    this is very high  priorty issue in our  landscape
    regards
    raja

    thanks to all for helping

Maybe you are looking for

  • Connecting with SQL Server

    Dear All, I m new to JDeveloper and want to make a connection with SQL Server 2008 but in Connection Dialogue with following Settings :- Connection Type: SQL Server UserName: sa Password: ****** HostName: EServer DatabaseName: DBName PortNumber: 1430

  • UTF-8 Support in E-mail ID??

    Is it possible to have UTF-8 compliant alias in Exchange 2013??? I am unable to add a new MB with alias in UTf -8 character. However, if I didn't provide an alias it will accept the logon name as its alias and logon name supports UTf-8. So Indirectly

  • Tab page shortcut

    HI , I have problem creating shortcut for tabe page. In aplication there are six tab pages, and I need to have keyboard shortcut to every tab page.How to create that? At example, if user press ALT+R I want certain tab page to be toppage , or better w

  • Webflows - BEA WebLogic Portal 4.0

    Hello... My name is Miriam Serrano I am working with BEA WebLogic Portal 4.0. My application is clientes, but I have a error with a webflow maquila Not Logged In.. Logged In...as secofi2 Login - No existe informacion de session ...obteniendo perfil d

  • Mailbox not visible in EMC

    Hello. I have a mailbox that is moved from exchange 2010 to Exchange 2013 using Cmdlet Move-mailbox. After moving the mailbox is not visible in the EMC in Exchange 2013. However, it appears using Get-Mailbox cmdlet. Any ideas on why it does not appea