To modify the registry xml file manually is not a good approach. Instead we should try to find a better way. But for this I need some more information:
- the WebSphere edition and version (e.g. WAS ND 9.0.5)
- the operating system (Linux, Windows, AIX, z/OS, ...)
- the kind of profile that you want to create
- cell - Deployment manager cell (dmgr and default)
- management - Management. Use in conjunction with the -serverType parameter to indicate the type of management profile.
- secureproxy- Secure proxy
- default - Application server
- managed - Custom
- the error that you are seeing at the end of the profile creation
- errors that you have found in the log files mentioned above
- the lists of profiles that are at the profile registry
Use the following command to create the list:
app_server_root/bin/manageprofiles.sh -listProfiles
where app_server_root is something like /opt/IBM/WebSphere/AppServer
- You should also check if the directory for profile that you want to create already exists, default path: app_server_root/profiles/<profilename>
If it exists, delete the directory before trying again to create the profile
- If you did not create any profile correctly so far, try to delete all profiles with the command
app_server_root/bin/manageprofiles.sh -deleteAll
Then delete all directories where the profiles resided, default is: app_server_root/profiles/<profilename>
After this, try to create the profile using the command line. The command is something like:
app_server_root/bin/manageprofiles.sh -create
-profileName profile_name
-profilePath profile_root
-templatePath template_path
You can find more details about the command at:
https://www.ibm.com/docs/en/was-nd/9.0.5?topic=systems-manageprofiles-command
Hope that helps.
Lars