Creating a Portal application server profile on IBM i

The IBM® WebSphere® Portal installation registers the application server profile template with IBM WebSphere Application Server. You can use the manageprofiles command to create new profiles based on the template. The newly created profile's WebSphere Application Server administrator ID and password are set according to the input given. The portal still has the same security and database configurations, including the portal administrator ID and password, as the initial profile used to run the enable-profiles task. If your initial profile was using the Derby database, a fresh copy is automatically created with the new profile. If your initial profile was configured to use a non-Derby database, then all the database domains of the new profile are identically configured. Likewise, any security configurations (like a stand-alone or federated LDAP) that were made before running the enable-profiles task are preserved with the new profile.

1. Run the following command from the AppServer_root/bin directory:

   manageprofiles -create -templatePath 
   /QIBM/ProdData/WebSphere/PortalServer/V8/Content/Portal/profileTemplates/default.portal
   		-profileName testPortal1
   		-profilePath /QIBM/UserData/WebSphere/AppServer/V8/ND/profiles/testportal1

   Tip: If you have a long command, use the continuation character "\" to avoid seeing the "not found" error message.

   In this example, the portal profile template is installed under the /QIBM/UserData/WebSphere/AppServer/V8/ND/profiles/wp_profile/PortalServer/profileTemplates/default.portal directory. The new profile is testportal1 and is located under the /QIBM/UserData/WebSphere/AppServer/V8/ND/profiles/testportal1 directory.

   You can also use the following parameters:

   • -isDefault: signifies that this profile is to serve as the default profile for the installation
   • -isDeveloperServer: indicates that WebSphere Portal is to be configured for development mode in this profile.
   • -nodeName: provides a node name for the new profile; if not provided, the node name defaults to a value based on the local host name. This parameter is required if federating this profile into a managed cell because this value must be unique from other nodes in the cell.

   See manageprofiles command for a complete list of parameters.
2. Because all database domains are identically configured for each profile, you must modify the database configuration for database domains that cannot be shared or that you do not want to share.