You can use the following parameters with the manageprofiles command for WebSphere ESB.
For some parameters listed below, for more information, refer to the description of the parameter of the same name in the documentation for the wasprofile command in the WebSphere Application Server information center.
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 an Application Server profile.
Federating when the deployment manager is not availableIf you federate a custom node when the deployment manager is not running or is not available because of security being enabled or for other reasons, the installation indicator in the logs is INSTCONFFAIL 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 wasprofile command. Use the addNode command instead. For more information, refer to the description of the parameter of the same name in the documentation for the wasprofile command in the WebSphere Application Server information center.
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\AppServer\profiles\profile01