SSO J2EE client change - dispatcher running, no server connected!

[Former Member]

I need to set up SSO between the portal (SP9) and R/3 to enable users via our bespoke java application to send RFCs. help.sap.com recommended changing the J2EE client on the WAS so tickets issued by the portal would be unique (rather than using the default client 000). I made the change in cluster-data > server > services > com.sap.security.core.ume.service > login.ticket_client via the config tool and stopped and restarted the instance.

The MMC shows the system has started but I'm unable to connect to the portal - Dispatcher running, but no server connected! I restarted the J2EE engine via the WAS (we have WAS 6.4 ABAP + Java), no improvement.

I'm unable to connect to visual administrator. Connection via the dispatcher generates error - connection lost. Connection via the message server generates error - unable to look up connection parameters.

In changed the client value back to the default and restarted but still have the same problems.

1) How do I re establish the connection parameters without re installing the portal?

2) How do I avoid this problem? Should I just use the default client 000 and hope problems do not occur later when tickets are issued?

Thanks

[Former Member]

I changed some parameter in J2EE engine through VA.

Now I have the same problem as you have, are you able to fix it? Please let me know.

Regards

YAsh

[former_member188977]

Hi Natalie,

What can you see in the logs files ?

JC00\j2ee\admin\log\console_logs

Regards.

[Former Member]

I only have time and date stamps in the console_logs???

[Former Member]

Almost sounds like the VA is set to the wrong port. Defaut is 50004.

I had and install that was on Windows 2003. The OS was using 50004, why, I couldn't find. After restarting the server the problem was corrected.

Under the MMC, open up your jave engine instance and right click. Look in the developers trace, it might give more of a clue than what is in the logs.