Rational Automation Framework soap.client.props fails on install?
One answer
When installing WAS or Portal. Selecting the the "use soap.client.props" and setting the value to true does NOT work for installs. "use soap.client.props" was designed so that an individual could manage various stand alone servers in a Flexible Management Topology. When using an Administrative Agent, you can hit the admin agent url and it asks what server you want to manage. Then you can select that stand alone server and log in. RAF skips the admin agent and goes to the STD server. You need to use soap.client.props in order for this to work. So that RAF knows how to log in to the stand alone environments without prompts.
When using this value to install WAS or Portal. The initial installation does not set the username and psw in this file. There is no option during a manual install to set the soap.client.props. Therefor RAF does not either. The first action after the install that uses wsadmin will fail with authentication error that results in a NullPointer exception. This is because the username and psw were not set in the soap.client.props on the install.
Soap.client.props is only used for reading existing environments that use the properties defined in soap.client.props to not be prompted by wsadmin.... When managing several stand alone environment using an Administrative Agent in a Flexible Management Topology.
Just something to be aware of!!!
Thanks!
Comments
If this is functionality that you require or want for whatever the reason. There is a custom action blog here --> https://www.ibm.com/developerworks/community/blogs/RAF/entry/creating_custom_actions_to_edit_property_files_within_websphere?lang=en
that explains how to manipulate property files and change this. Although, it's not supported by IBM officially so if it doesn't work figure out how to fix it.
If you have questions or concerns about RAF please use the RAF twitter
www.twitter.com/raf_websphere