Professional Documents
Culture Documents
End To End SLD Configuration and JCo Configuration
End To End SLD Configuration and JCo Configuration
Applies to:
This article applies to Enterprise Portal 7.0. For more information, visit the Portal and Collaboration homepage.
Summary
This document covers what is the process involved to configure R/3 System, Technical System Creation and to configure JCo destinations. Author: Anil Dichpally
Author Bio
Anil Dichpally is working as Senior Consultant in Intelligroup Asia Pvt Ltd, Hyderabad. He has worked on EP, KM and collaboration, Webdyn pro Programming and Java Technologies. He is SDN Moderator for Portal, KM & C and Searching Utilities areas. . He has completed his M.C.A from Osmania University. .
Table of Contents
Introduction .........................................................................................................................................................3 Perquisites ......................................................................................................................................................3 Procedure ...........................................................................................................................................................3 Creating System in SLD................................................................................................................................12 Creating JCo Destination ..............................................................................................................................20 For Jco Meta Data Destination .....................................................................................................................22 For Model Data Jco Destination....................................................................................................................26 Testing the Application..................................................................................................................................26 Related Content................................................................................................................................................27 Disclaimer and Liability Notice..........................................................................................................................28
Introduction
The SAP System Landscape Directory (SLD) is the central information provider in a system landscape. The SLD is a server application that communicates with a client application by using the Hypertext Transfer Protocol (HTTP). The SLD server contains component information, a landscape description, and a name reservation, which are based on the standard Common Information Model (CIM). The CIM standard is a general schema for describing the elements in a system landscape. This standard is independent of any implementation. Perquisites You will need to have system OS (Operating System) level credentials and also the details of backend server which are connecting too.
Procedure
As already mentioned we need to have OS level credentials to the server, so that we can start and stop the server whenever required. 1) Go to the server installed path and start Visual Administrator i.e. C:\usr\sap\<systemid>\<system instance>\admin\Go.bat
3) Minimize the tool bar and click on Connect and then enter the Portal Administrator user credentials so that we can connect to Visual Administrator.
Note: You need to have Portal Administrator access as well as operating system level credentials to configure back end Systems.
5) Click on HTTP Settings tab and set the details as mentioned below Host Name: EP Server Name Port: EP Server Port Number User: Portal Administrator User Id Password: Admin Password After entering the above details click on Save.
6) Select the CIM Client Generation Settings and enter the details same as which we have given for HTTP Settings.
7) After giving the details of CIM Settings now we can test weather we have given the details correct or not and also this will let us know if there are any wrong entries.
Note: Only after you see a pop up where CIM setting is successful then go ahead with further steps.
8) Click on the icon shown below to test the Data Transfer from J2EE to SLD Server.
9) Click on Yes when a pop for Transfer SLD appears. This will create WEB AS java technical system object (system object) of Portal in SLD Server. i.e. it creates an instance of J2EE engine of portal in SLD. 10) Just incase if we want to check the Portal details given, we can do so by using the tab Information.
Creating System in SLD 11) Now accessing SLD server to create Technical Landscape and JCo destination. 12) Log on to Portal with the Portal URL as http://<servername>:<portal number>/SLD and then click in Technical System.
13) Click on New Technical System, which will create a technical system to access the backend system.
Note: Here the backend system can be anything i.e. R/3 server, CRM server or BW Server.
14) Select WEB AS-ABAP, since here we are trying to connect to R/3 Server. Note: Select WEB AS-ABAP for R/3, CRM and BW servers i.e. for SAP components. Select WEB AS-JAVA for XI server.
15) Now enter SID, Installation Number and Host Name, and click Next
These details changes from system to system that you are connecting too. Check the log on pad of the server which you are connecting to get the details of the server which you are connecting.
16) Enter Message Server Port No: 3600 Instance No : 00 (System Number of the server we are connecting)
Note: Message Port number will be 3600 if instance number is 00 Similarly Message Port number will be 3601 if instance number is 01 and so on
17) Select Add Application Server and give Host Name and Instance Number (System Number) of the server which you are connecting too. Click Next.
18) Enter Client and Logical Client Name (LS name created in SM59) Click Next
20) Now select the check boxes for Installed Software Components. And then click on Finish button.
Creating JCo Destination 21) Enter the following URL in the browser to create JCos http://<server name>:<port number>/webdynpro then go to Content Administrator and give the Portal Administrator credentials to log on to portal.
22) Click on the button Maintain JCo Destinations We deploy the application in Netweaver Developer Studio there we will mention the destinations those will be displayed here (right of the screen we observe it) Now we need to select them and we have to create JCo destinations for those applications. For each application we have two destinations Eg: <name> metadata <name> modeldata Let say Destinations: BI_METADATA & BI _MODELDATA
23) Step a: for Meta Data i.e. BI_METADATA, select the destination and then click on Create.
24) Step b: Enter the name of the destination and client number of the server which you are connecting and then click Next.
25) Step c: As we have given the details already when creating Technical Details, the same are refluxed here. Just check the option User local J2EE engine <Instance number of the Portal server> and then click on Next.
26) Step d: Select connection type as Destination Meta Data since we are creating JCo destination for Metadata type.
27) Step e: Select Message Server from the drop down and Logon Group. Message Server will be the server what we have created in SLD Configuration. Logon Group maintain as Space
For Model Data Jco Destination 28) Step f: Enter user id and password of the server which you are connecting too. Here we are connecting to R/3 system Click Next and then Finish to finish the process.
29) Repeat the steps from a to f for Application Data. Testing the Application 30) Go to Local ( all the JCo destinations are stored here) select the application which we have created click on Run button.( on right hand side of the screen).
Related Content
https://www.sdn.sap.com/irj/sdn/nw-sld http://help.sap.com/saphelp_nwmobile71/helpdata/en/45/3fe8ca901f5b3ce10000000a1553f6/content.htm For more information, visit the Portal and Collaboration homepage.