1. First be sure to disable WebSphere security on the
application server that the client connects to. Follow section 21.1.6 of
the WebSphere 4.0 handbook. The handbook can be accessed at the following
link: http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246176.pdf
2. On the WebSphere server, make a copy of the <WAS
root>/properties/sas.client.props file. Rename the copy to something
else, like sas.javaclient.props. Move this to your java client machine.
You can place the file in any directory on the client machine.
3. In sas.javaclient.props, set
com.ibm.CORBA.securityEnabled=false.
4. You need to point your java application to use this file by setting
this property:
-Dcom.ibm.CORBA.ConfigURL=file:/(drive
letter):/(location)/sas.client.props
If you use a batch file to run your java application, you can add this
property to the batch file used to run the app. WebSphere ships with batch
files you can use as an example: <WAS install>/bin/setupCmdLine.bat
and <WAS install>/bin/adminclient.bat.
If you use WSAD to run your application, the property needs to be added
to the VM Settings under the run-time environment.
5. In order for this to work, the CosNaming parameters in WebSphere
must be set to "Everyone". These are located in the administrative
console, security center, on the Administrative Role tab.
|