Installing and removing a stand-alone Personalization Server
You can install a stand-alone Personalization server to a new IBM® WebSphere® Application Server profile, which allows you to deploy WebSphere Application Server specific applications, serve personalized content to users, and record site metrics without requiring an active IBM WebSphere Portal server.
About this task
Procedure
- Open a command prompt and change to the was_profile_root/bin directory.
- Run the following command to create a WebSphere Application
Server profile for the Personalization server:
- Windows
manageprofiles.bat -create -profileName pzn_profile -profilePath was_profile_root\pzn_profile -templatePath AppServer_root\profileTemplates\default
- UNIX
./manageprofiles.sh -create -profileName pzn_profile -profilePath was_profile_root/pzn_profile -templatePath AppServer_root/profileTemplates/default
- Change to the wp_profile_root/ConfigEngine directory and run the following command to initialize the stand-alone Personalization Server:
- Windows
ConfigEngine.bat -DPznProfileName=target_profile_name action-init-pzn-standalone -DPortalAdminId=portal_uid -DPortalAdminPwd=portal_uid_password -DWasAdminId=was_uid -DWasPassword=was_uid_password
- UNIX
./ConfigEngine.sh -DPznProfileName=target_profile_name action-init-pzn-standalone -DPortalAdminId=portal_uid -DPortalAdminPwd=portal_uid_password -DWasAdminId=was_uid -DWasPassword=was_uid_password
- Open the wp_profile_root/ConfigEngine/pzn.properties file and edit
the following properties to match your new WebSphere Application
Server profile to the
initialized stand-alone Personalization Server:
- WasSoapPort
- Enter the SOAP_CONNECTOR_ADDRESS value found in the serverindex.xml file of the new WebSphere Application Server profile.
- WpsHostPort
- Enter the WC_defaulthost value found in the serverindex.xml file of the new WebSphere Application Server profile.
- XmlAccessPort
- Enter the port used by the XMLAccess configuration task to connect the XMLAccess server.
- VirtualHostName
- Enter the name of the new WebSphere Application Server profile virtual host.
- WasUserHome
- Enter the name of the directory where the new WebSphere Application Server profile was created.
- ProfileName
- Enter the name of new WebSphere Application Server profile name.
- CellName
- Enter the name of the new WebSphere Application Server profile cell.
- NodeName
- Enter the name of the new WebSphere Application Server profile node.
- ServerName
- Enter name of the application server for the new WebSphere Application Server profile.
- Change to the wp_profile_root/ConfigEngine directory and run the following command to install the stand-alone Personalization Server:
- Windows
ConfigPzn.bat -DparentProperties=wp_profile_root\ConfigEngine\pzn.properties -DSaveParentProperties=false -DPortalAdminID=portal_uid -DPortalAdminPwd=portal_password -DWasAdminID=WAS_uid -DWasPassword=WAS_password action-install-pzn-standalone
- UNIX
./ConfigPzn.sh -DparentProperties=wp_profile_root/ConfigEngine/pzn.properties -DSaveParentProperties=false -DPortalAdminID=portal_uid -DPortalAdminPwd=portal_password -DWasAdminID=WAS_uid -DWasPassword=WAS_password action-install-pzn-standalone
- Change to the wp_profile_root/ConfigEngine directory and run the following command to remove the stand-alone Personalization Server:
- Windows
ConfigPzn.bat -DparentProperties=wp_profile_root\ConfigEngine\pzn.properties -DSaveParentProperties=false -DPortalAdminId=portal_uid -DPortalAdminPwd=portal_uid_passsword -DWasAdminId=was_uid -DWasPassword=was_uid_password action-remove-pzn-standalone
- UNIX
./ConfigPzn.sh -DparentProperties=wp_profile_root/ConfigEngine/pzn.properties -DSaveParentProperties=false -DPortalAdminId=portal_uid -DPortalAdminPwd=portal_uid_passsword -DWasAdminId=was_uid -DWasPassword=was_uid_password action-remove-pzn-standalone