IBM WebSphere Portal 7 Clustering : Create DMGR Profile and Agument

Backup and enable portal profile (wp_profile)

1. Following ConfigEngine task will create the backup of the the primary node i.e. wp_profile and also enables the portal profile templates within the WAS profile Management tool. This will let you create the new portal profile in the future.

./ConfigEngine.sh enable-profiles -DWasPassword=wasadmin

 this will create the PofileTemplates directory under the <PortalServer root> and wp_profile backup will be created (portal.car) and saved under <PortalServer_root>/ProfileTemplates/default.portal/configarchives

2. Execute the following ConfigEngine to package all profile templates into single

./ConfigEngine.sh package-profiles -DWasPassword=wasadmin

Creates <PortalServer_root>/profileTemplates/profileTemplates.zip

Creating DMGR and Augmenting the profile

DMGR profile can be create in two ways

a). Install the DMGR on separate server (for this you need install the WAS ND ).
b). Create  DMGR profile on existing WAS server installation (Where portal server installed, I have used this approach , Clustering guide explains to install the ND fresh )

Create DMGR profile

1. WebSphere 64-bit is not compatible with the Profile Management Tool. (The Profile Management Tool is not available on Linux PPC 64-bit, Linux AMD 64-bit, and Windows AMD 64-bit systems.) , So had to create the DMGR node manually using the profile management tool (manageprofiles) from command prompt

http://www-01.ibm.com/support/docview.wss?uid=swg21408010

2. Following will give all available optiones (required /optional ..etc).

manageprofiles.bat -create -templatePath C:\IBM\WebSphere\AppServer\profileTemplates\management -help

3. Execute the following

manageprofiles.bat -create

-templatePath C:\IBM\WebSphere\AppServer\profileTemplates\management

-profilePath C:\IBM\WebSphere\AppServer\profiles\Dmgr01

-hostName sivapc.sivavaka.com

-profileName Dmgr01

-cellName SivaPCCell01

-nodeName SivaPCNode01

-enableAdminSecurity true

-adminUserName wasadmin

-adminPassword wasadmin

C:\IBM\WebSphere\AppServer\bin>manageprofiles.bat -create -templatePath C:\IBM\WebSphere\AppServer\profileTemplates\management -profilePath C:\IBM\WebSphere\AppServer\profiles\Dmgr01 -hostName sivapc.sivavaka.com -profileName Dmgr01 -cellName SivaPCCell01 -nodeName SivaPCNode01 -enableAdminSecurity true -adminUserName wasadmin -adminPassword wasadmin

INSTCONFSUCCESS: Success: Profile Dmgr01 now exists. Please consult C:\IBM\WebSphere\AppServer\profiles\Dmgr01\logs\AboutThisProfile.txt for more information about this profile.

Found the port details in above log file (you need SOAP port details while federating node)

Application server environment to create: Management

Location: C:\IBM\WebSphere\AppServer\profiles\Dmgr01

Disk space required: 30 MB

Profile name: Dmgr01

Make this profile the default: False

Node name: SivaPCNode01

Cell name: SivaPCCell01

Host name: sivapc.sivavaka.com

Enable administrative security (recommended): True

Administrative console port: 9060

Administrative console secure port: 9043

Management bootstrap port: 9809

Management SOAP connector port: 8879

Run Management as a service: False

Augmenting profile (or Configuring DMGR profile to manage portal nodes)

1. Extract the files from "fileForDmgr.zip" file (located under C:\IBM\WebSphere\PortalServer\filesForDmgr)  to "C:\IBM\WebSphere\AppServer" assuming that your DMGR profile is created under the "C:\IBM\WebSphere\AppServer\profiles\Dmgr01" .

NOTE:

1. I had to replace some of the existing files while copying to appserver directory.
2. If the Deployment Manager profile was not created in the default AppServer/profiles/Dmgr01 directory, then the metadata_wkplc.xml file, located in the AppServer\profiles\Dmgr01\config\.repository\metadata_wkplc.xml directory in the zip file, must be copied into the config\.repository subdirectory under the Deployment Manager profile directory.
3. Just make sure DMGR is stopped at this point(execute the stopManager.bat from /profiles/Dmgr01/bin)

2. Execute the following to augment the DMGR profile

manageprofiles.bat -augment -templatePath C:\IBM\WebSphere\AppServer\profileTemplates\management.portal.augment -profileName Dmgr01

C:\IBM\WebSphere\AppServer\bin>manageprofiles.bat -augment -templatePath C:\IBM\WebSphere\AppServer\profileTemplates\management.portal.augment -profileName Dmgr01

INSTCONFSUCCESS: Profile augmentation succeeded.

3. Start the Deployment Manager

C:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin>startManager.bat

4. Verify that the WebSphere Portal administrative users and administrative group exist in the Deployment Manager cell's user registry
1. Add the full user DN in the "Primary administrative user name" filed to avoid the userid conflicts when configured with federated LDAP.

2. Save and restart the deployment manager.

References

1. To create and augment the profile manually.

http://www-10.lotus.com/ldd/portalwiki.nsf/xpDocViewer.xsp?lookupName=IBM+WebSphere+Portal+7+Product+Documentation#action=openDocument&res_title=Preparing_the_WebSphere_Application_Server_Deployment_Manager_on_Windows_wp7&content=pdcontent

2. http://www-01.ibm.com/support/docview.wss?uid=swg21408010
3. www-10.lotus.com/ldd/portalwiki.nsf/xsp/.ibmmodres/domino/openattachment/ldd/portalwiki.nsf/1ce09486e05fc916852577a70072d757/attach/wpv7_clusterguide.pdf


Update

Recently (Mid July 2013) IBM has posted  "Manage Profiles Interactive" tool to create new profiles in WebSphere Application Server (this is useful to create the profile in 64-bit environments)

http://www-01.ibm.com/support/docview.wss?uid=swg21442487