configuring ESS on portal

[Former Member]

Hi ,

I am following the below mentioned thread to configure ESS on portal .

I have a few quesions though .

1) It asks me to go to the visual administrator and choose SLD bridge from services and maitain parameters for HTTP connection . This is required to be done after SLD is configured . I have configured the SLD and set up the technical system in it . Now when I login to visual administrator there are two nodes "dispatcher" and "server" . If you expand both the nodes you get a node "SLD data supplier" which I believe is the same as "SLD bridge" that the above mentioned thread is refering to .I need to know in which of these nodes , "server" or "dispatcher" , i am required to maintain the HTTP parameter settings ?

2) The thread then asks me to take the help of

http://help.sap.com/saphelp_erp2004/helpdata/en/38/e8584c2a664547b60442646bee23b6/frameset.htm

and set up the required JCO connections . I use the URL

The URL is http://<host>:<port>/webdynpro/dispatcher/sap.com/tc_wdtools/Explorer

to access webdynpro content administrator . It asks me to press "maintain jco destinations" button to make a new connection . This button appears greyed out in my screen . The only button that is active is "check sld connection" . When I press the buton it shows me a windown with all the fields greyed out and three buttons which say "test connection", "start sld" and "close" .When I press "test connection" nothing happens . When I press "start sld" it shows me a waiting/processing sign and nothing appears after that .

In the detailed navigation I have two nodes

- sap.com

- system defined content

I open the second node and then comes the node "jco destinations " .Below this appears the message "no connection to SLD" . As far as I think this is because data supplier bridge has not been started by me and this is the reason why I am not seeing the connection to SLD . Am i correct or do you think there is some other issue ?

I need help in my first quesion which I believe will resolve my second problem . Please let me know if there are any other suggestions .

Regards

Anupam Jaiswal

[Former Member · Accepted solution]

Hey Guys ,

I am stuck up on the JCO destinations now .I am logged in to the Web Dynpro Content Administrator. I am using the following link to do the same .

http://help.sap.com/saphelp_erp2004/helpdata/en/38/e8584c2a664547b60442646bee23b6/frameset.htm

There under the topic " Setting Up SAP Java Connector (JCo) Connections " it asks to create the required jco destinations which will be

JCo connection for metadata: SAP_R3_HumanResources_MetaData.

JCo connection for application data: SAP_R3_HumanResources

During the step

Configure the JCo connection for the metadata:

it asks to "Enter a user in the SAP ECC system that you have created for the authorization check of the JCo connection." Which is this user ?

From this it seems that I need to do something at the R3 end as well to configure the ESS on portal to the R3 at the backend . Could someone please guide me through the process on the R3 side .

Also when I made a jco connection and tested it , it gave me the following error message

"com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=59 GROUP=PUBLIC R3NAME=DEV MSSERV=sapmsDEV PCS=1 ERROR service 'sapmsDEV' unknown TIME Tue Mar 14 15:25:21 2006 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 MODULE ninti.c LINE 505 DETAIL NiPGetServByName2: service 'sapmsDEV' not found SYSTEM CALL getservbyname_r COUNTER 1 "

Is this because I have not done the required at the R3 side or is it because of something else ?

Regards

Anupam

[Former Member · Accepted solution]

Hey Anupam,

Try creating a user in ECC system (using <b>su01</b> transaction) with <b>SAP_ALL</b> authorization.. with password 'init' (say)

Login manually (using Logon pad) and change the pwd.. [<i>you have to change the initial password.. very important</i>]

Try giving the user name and the changed password in this Jco configuration

Plz try and tell me... I am positive that this will work..

Hope it helps!

Regards,

SK.

PS: Plz Consider rewarding points if helpful!

[Former Member · Accepted solution]

SK ,

didn't work . I created a user "j2ee_admin" in ECC and did what you said . I gave the same user while creating the jco connection . When I tested it failed with the same error .

Regards

Deepak Singh

[Former Member · Accepted solution]

Hi Anupam

You have to set the service name in the path as shown below.

c:winntsystem32driversetcservices file.

Make sure that the service name and port no are correctly copied there

It should be in the format

sapms<SID> 3600/tcp

Also check the below links for further details.

Regards

Yoga

[Former Member · Accepted solution]

Hi Yoga ,

I think it helped though I am getting a different error now . The error now is

"com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=kdev GROUP=PUBLIC R3NAME=DEV MSSERV=sapmsDEV PCS=1 <b>ERROR Group PUBLIC not found</b> TIME Fri Mar 17 13:01:51 2006 RELEASE 640 COMPONENT LG VERSION 5 RC -6 MODULE lgxx.c LINE 3498 DETAIL LgIGroup COUNTER 1 "

Where should I go to resolve this problem ? I think there needs something to be done on the R3 side . If I am correct then what exactly should I do on R3 ?

Regards

Anupam

[Former Member · Accepted solution]

Hey Yoga ,

One more thing . The service entry that you talked about , does it need to exist on the R3 system as well or just the EP server ?

Regards

Anupam

[Former Member]

Hi Anupam,

If the group Public is not showing up(during the JCO creation), try running the transaction SMLG on the R3 side. This would enable the group 'public'.

As far as Deepak's query goes the roles are present in the package as i have deployed the same. I dont know what the exact cause of the problem but you can try deleting the contents which were created when you deployed the package and re-deploy the package.

Regards,

Prathamesh

[Former Member]

Prathmesh ,

Are you saying that by just running the transaction SMLG the public group would be activated or there is something more to be done . I am not an R3 guy so could you please guide me as to what exactly needs to be done in that transaction ?

Regards

Anupam

[Former Member]

Hi Anupam,

Connect to the R/3 server for which you are trying to create the JCO. Run the transaction SMLG. It will show u the existing logon groups. carry out the following steps if the 'PUBLIC' group is not present in the list of logon groups.

Click on the create button. In the pop-up, type the logon as 'PUBLIC'. For the instance, select the F4 help and choose the existing instance number. Click on copy and click save. Try running the transaction /nsmlg and now it should show the logon group 'PUBLIC'.

When you create the JCO connection, it should now show the logon group 'PUBLIC'.

Regards,

Prathamesh.

Plz reward points for helpful answers:-))

[Former Member]

Guys ,

I need to understand something . In the thread

http://help.sap.com/saphelp_erp2004/helpdata/en/38/e8584c2a664547b60442646bee23b6/frameset.htm

It is mentioned...

"download the Business Package for Employee Self-Service (mySAP ERP) 60.2 from the iViewStudio and install it."

I did the same and got two files

1) BPERP4ESS0_0-10003146.zip (contains BPERP4ESS0_0.sca)

2) BPERP4ESS01_0-10003146.sca

I deployed the first file through SDM . When I go to deploy the second file it says that all the latest contents have already been deployed so cannot deploy this one .

Now I log into the portal and see under content administration > migrated content > EP 5.0 . Everything is present there but for the roles . Why am i not able too any roles for ESS or is it that no roles and send with this business package and we have to kake them ourselves .

Though the above mentioned thread says to use "com.sap.pct.ess.employee_self_service" role for ESS which makes me believe that roles come along with the package .

What do you think can be the problem ?

Regards

Deepak Singh

[Former Member]

Hi Anupam,

1)I need to know in which of these nodes , "server" or "dispatcher" , i am required to maintain the HTTP parameter settings ?

>>>>>>>>>>>> In Visual Admin >>> "Server" >>> services >>> SLD data supplier >>> Runtime >>> HTTP settings

2)I wonder why buttons are greyed out?? Did you check out the standard documentation of ESS/MSS ??

Hope it helps!

Regards,

SK.

PS: Plz consider rewarding points if helpful!

[Former Member]

Hi SK ,

Which standard documentation are you talking about ? I think I have the required link from SAP help which I have mentioned in my thread . Is there something else which is standard ? Can you give me some link for the same ?

Regards

Anupam

[Former Member]

Hi Anupam,

If you are following help.sap.com, i guess that should suffice the purpose.

Regards,

SK.

[Former Member]

Hey SK ,

I have configured the SLD data supplier parameters in server node as suggested by you but now there is another problem .

My SLD page is accessible on the port 50000 with the URL http://<host>:<port>/sld

In SLD I have already defined the technical system for portal and the R3 server which I wish to bring into my landscape and have also started the "data supplier bridge". Now when I go to define the JCO destinations with the URL http://<host>:<port>/webdynpro/dispatcher/sap.com/tc_wdtools/Explorer

the status is the same . The buttons are greyed out . When I press the button "check SLD connection " it opens a window in which i see the parameters of the SLD used . There is a discrepency here . The port shown here for SLD cis 50004 but the SLD page is accessible on 50000. Where do you think I can change the settings for this port . I cannot change these settings there on the window as the fields are non editable .

Need your help with the same .

Regards

Anupam

[Former Member]

Hey ,

I think I could find a solution to the problem . It was picking the settings from the CIM client generation tab in visual administrator. I changed the same to 50000 and it worked .

Regards

Anupam