Automating XMLConfig, wscp, or other Script and Batch Files by Disabling Prompts

Technote (FAQ)
Problem
You have enabled security, and you do not want to be prompted for user id and password when using XMLConfig, wscp, or other script and batch files.
Solution
As an example, when you are using XMLConfig scripts and security has been enabled, the default action is to have a prompt presented for your user id and password. This is not convenient when trying to automate your scripts.

In your sas.client.props file, located in the $WAS_HOME\properties directory, change the loginSource parameter fromprompttoproperties:

com.ibm.CORBA.loginSource=properties

Add your user id and password to the following:

com.ibm.CORBA.loginUserid=MyUserid
com.ibm.CORBA.loginPassword=MyPasswd

Websphere® Application Server automatically detects the changes and you should not have to restart any processes.

Note:A side-effect of this change is that you will not be prompted for user id and password when starting the administrative console or any other Java™ client.

One option to fix this side-effect would be to override the CLIENTSAS variable in the XMLConfig.[sh|bat]. The CLIENTSAS variable is originally set with a call to the setupCmdLine.[sh|bat]. This variable can then point to a second copy of sas.client.pros which can contain your user id, password, and login source. This way only your XMLConfig program will not be prompted.












Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Administrative Console (all non-scripting)
Operating system(s): Multi-Platform
Software version: 3.5, 4.0
Software edition: Standard, Advanced
Reference #: 1030974
IBM Group: Software Group
Modified date: 2003-12-08