Unable to login using remote DS Clients

sen_ds8 · Post by **sen_ds8** » Wed Jun 18, 2008 1:54 am

All

We did a clean install of DataStage 8.0 in a Windows 2003 Server inline with the installation manuals.
We were able to login using the DataStage clients installed on the same machine . However when we login from a desktop with this client installation we get the following error.
The suspect is the IIOP host , it is coming out to be localhost and not the server where WAS is running.

Where is this configuration stored ?

Is it an installation issue ?

javax.security.auth.login.LoginException: A communication failure occurred while attempting to obtain an initial context with the provider URL: "iiop://localhost:2809". Make sure that any bootstrap address information in the URL is correct and that the target name server is running. A bootstrap address with no port specification defaults to port 2809. Possible causes other than an incorrect bootstrap address or unavailable name server include the network environment and workstation network configuration.

Any Pointers will be of great use.

DS_FocusGroup · Post by **DS_FocusGroup** » Wed Jun 18, 2008 2:27 am

Are you using the Server's Name to connect from the desktop or localhost? Also, the default port for Information Server is 9080. Did u explicitly specify 2809 during installation? Usually when you connect from a client installed on a separate machine, you need to give the following URL (Web Console for eg):

http://ServerName:9080

sen_ds8 · Post by **sen_ds8** » Wed Jun 18, 2008 3:14 am

Not sure if what you are trying to imply of relevance :

Are you using the Server's Name to connect from the desktop or localhost?

While trying to connect i use hostname:9080 as ATTACH TO DOMAIN. I have tried IP:9080 to make sure there are no issues in resolution of Name to IP.

Also, the default port for Information Server is 9080. Did u explicitly specify 2809 during installation?

Wrong question possibly

A communication failure occurred while attempting to obtain an initial context with the provider URL: "iiop://localhost:2809". Make sure that any bootstrap address information in the URL is correct and that the target name server is running. A bootstrap address with no port specification defaults to port 2809.

Usually when you connect from a client installed on a separate machine, you need to give the following URL (Web Console for eg):
http://ServerName:9080

Yes. Tried this got a Security Exception.

Error Stack:
com.ibm.ws.security.web.WebSecurityException: AuthorizationFailed
at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java(Compiled Code))
at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java(Compiled Code))
at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:424)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3003)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:221)
at com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:210)

deanwalker · Post by **deanwalker** » Wed Jun 18, 2008 4:15 am

Add the server & domain names to your hosts file.

sen_ds8 · Post by **sen_ds8** » Wed Jun 18, 2008 4:22 am

Dean:
Did that did not help.

sen_ds8 · Post by **sen_ds8** » Wed Jun 18, 2008 4:22 am

The actual problem is InitialContext resolution from client points to localhost and not the IIS-SERVER

javax.security.auth.login.LoginException: A communication failure occurred while attempting to obtain an initial context with the provider URL: "iiop://localhost:2809". Make sure that any bootstrap address information in the URL is correct and that the target name server is running. A bootstrap address with no port specification defaults to port 2809. Possible causes other than an incorrect bootstrap address or unavailable name server include the network environment and workstation network configuration.

Need help on this part ![/u]

jasper · Post by **jasper** » Thu Jul 10, 2008 8:15 am

hi,
did you get this working?

We have exactly the same error, but not with the localhost. We did a new installation , got one client connected properly, but another client gave these errors.

Difference here is that on the working PC a local administrator is using this, while on the other PC this is not the case. In previous version we saw this influencing the way datastage works, so we're looking in that direction to solve this.