on 05-29-2008 11:09 AM
Hi BI gurus,
I'm still here for call your help with SLD configuration for Java Web Dynpro.
I try to explane my configuration step and I hope that someone can help me:
1- I've BI test (with J2EE instance) installed and netweaver platform on server named 'kali' (ms port 3607, http port 8007), with Infrastructure environment ecc. and i wont to run (trought sap NWDS) a java web dynpro (flight list) who call a bapi in R/3 system test called 'nandi' (ms port 3606 and http port 8006).
2- I've read on a giudeline that I've to configure properly 'SLD Data Supplier' on J2EE Visual Administrator than I open my kali server consolle, go to service --> SLD Data Supplier and, in the tab 'runtime-HTTP Setting' I set host, port for my kali BI instance and on login with my LCR full permission user. Is it correct?
3- in next tab 'CIM Client Generation Settings' I fill the same configuration written above and CIMClient test goes right. Is it correct?
4- Now I open SLD configuration in kali BI system portal (http://kali:port/sld) and, in home, I add new 'Technical Systems'.
Here I fill this parameter:
Web AS ABAP
Web AS ABAP Name (SID): the nandi R/3 SID
Installation Number: the inst. number show on t-code SLICENSE
Database Host Name: nandi
Message Server
Host Name: nandi
Message Server Port (sapmsET6): 3606
Logon Group: SPACE (default)
Central Application Server
Host Name: nandi
Host Name: 06
Application Server List
Host Name: nandi
Instance: 06
Client List
Client Number: 100
Logical Client Name: ET6CLNT100
Installed Products
here what I've to choose like product name??My R/3 system products? (F.e. 'R/3 4.6C' ecc.)
are there any configurations error?
5- Now I open http://kali:port/irj portal page and click on tab 'Content Admin --> Web Dynpro' to create new JCO.
I've 'WD_FLIGHTLIST_RFC_METADATA_DEST' like JCO destination and I choose it for new JCO with client 100.
In J2EE cluster I've select 'Use local J2EE engine ''BW7 on kali''
Conn. Type: Dictionary Metadata
Message server connection: select message server created above (nandi)
Security: fill my nandi (???) username and password
Now when I test my new JCO connection an error occured. It's impossible to resolve message name host (in this case sapmsET6) and JCO connection doesn't work.
What can I do?
All settings are correctly filled?
Please help me, I'm newbie!!!!
Edited by: Andrea Davoli on May 29, 2008 12:53 PM
yes. You have to correct SLD DataSupplier in Visual Administrator.
1) ABAP Tech system seems okay.
1.1) check in %\Windows\System32\Drivers\etc\services file, you have an entry for the Message Server:
sapmsET6 3606\tcp
1.2) Go to T-Code SMLG in R/3, see SPACE logon group as attribute ext-Enabled checked.
2) check your JAVA Technical System, there you need J2EE system entry.
- you can get it from http://<j2ee_sys>:5<nr>00 and go to link System Information, you will get information for Java Technical system.
[System Landscape Directory|http://help.sap.com/saphelp_nw04s/helpdata/en/ee/74b3407e73c57fe10000000a1550b0/content.htm]
[Creating Java Tech System| http://help.sap.com/saphelp_nw04s/helpdata/en/42/b6a21e7b90311de10000000a1553f7/content.htm];
nikhiL
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks nikhiL,
your answer was very helpfull but problem still not solved.
The same message appears when I test JCO connection:
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=nandi GROUP=SPACE R3NAME=ET6 MSSERV=sapmsET6 PCS=1 ERROR service 'sapmsET6' unknown TIME Thu May 29 15:14:58 2008 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -3 MODULE nixxhsl.cpp LINE 776 DETAIL NiHsLGetServNo: service name cached as unknown COUNTER 1
I went in services (linux server) and I've found:
sapms <SID> 3606/tcp
and, as SAP guides say,
sapgw06 3306/tcp
I also try with 3306 but same error appears..
Have you got any ideas?
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.