Use the following parameters with the manageprofiles command for WebSphere Process Server.
The host name can be the long or short DNS name or the IP address of the deployment manager machine.
Specifying this optional parameter directs the manageprofiles command to attempt to federate the custom node into the deployment manager cell as it creates the custom profile. This parameter is ignored when creating a deployment manager profile or a stand-alone process server profile.
Federating when the deployment manager is not available
If you federate a custom node when the deployment manager is not running or is not available, the installation indicator in the logs is INSTCONFFAILED to indicate a complete failure. The resulting custom profile is unusable. You must move the custom profile directory out of the profile repository (the profiles installation root directory) before creating another custom profile with the same profile name.
If you have enabled security or changed the default JMX connector type, you cannot federate with the manageprofiles command. Use the addNode command instead.
install_root/profileTemplates/profile_type/actions/portsUpdate/bin \ /portdef.props
On Windows platforms: Specify the full path
to avoid an ANT scripting limitation that can cause a failure when federating
the profile into a cell. For example: -profilePath C:\IBM\WebSphere\ProcServer\profiles\profile01.
Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)