Hi,

Questions first: I need to change the name of an existing profile, in a ND v7.0 cell. Can anyone suggest how to do this?

Background

I am trying to move a Deployment Manager from a dedicated host (Host A) to co-exist with an Application Server from the same cell. This will mean Dmgr01 / Node01AppSrv01 on Host X and Node02AppSrv01 on Host Y. It will free up one physical server.

I have done this in a test environment using (a) changing the hostname on a profile and (b) using manageprofile.sh backup / restore commands with some minor tweaks around the Dmgr ports and wsadmin.properties updates.

All went well in test but in target environment I discovered that even though the path defined for AppSrv01 on Host X is '/opt/IBM/WebSphere/AppServer/profiles/AppSrv01 the 'manageprofiles.sh -listProfiles' command indicates that the profile is actually called 'dmgr'. In fact on all the hosts (Host A, X & Y) the profiles are the same name, 'dmgr'. I assume that they were built using the customised option in the Profile Management Tool, or something similar to have the profilename and profilepath different. This means that I can't export import dmgr into Host X or Y as it says the profile already exists.

Anyone suggest a fix?

Thanks

Paul

Hi Paul,

  Take a look to the next file.

  /opt/IBM/WebSphere/AppServer/properties/profileRegistry.xml

  In this file you have profile names and paths.

  If you change something is as you own risk, because is not supported to change profileNames.

  Hope this helps,

Regards

Hi Gabriel,

Thanks for the assistance. Since this is a Production node I don't want to 'hack' this so I managed to work around the problem by:

1. Removing the node (which related to the profile I needed to move on 001) from the cell
2. Deleting the profile locally from 001
3. Creating the new profile locally on 001, using a new name
4. Federated the new node back into the cell
5. Since the cluster config was still intact at dmgr level I simply added members to the cluster and bound them to the new profile. They inherited the configuration settings automatically from the cluster so this is why I didn't have to backup the settings from the original application servers
6. Then using the instructions at http://www.ibm.com/support/knowledgecenter/SSAW57_8.0.0/com.ibm.websphere.nd.doc/info/ae/ae/tagt_hostname.html I moved the Dmgr profile to 001 and reconfigured the application comms ports
7. Only thing missing then was to update the wsadmin.properties file for each profiles in the cell as it was pointing at the old dmgr host name
8. Finally I regenerated and propogated the plugin

Hope this helps someone.

Fearo