Install 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 WAS specific applications, serve personalized content to users, and record site metrics without requiring an active IBM WebSphere Portal server.

To install or uninstall a stand-alone Personalization Server:

  1. Open a command prompt and change to the was_profile_root/bin directory.

  2. Run the following command to create a WAS profile for the Personalization server:

    Option Description
    Windows™ manageprofiles.bat -create -profileName pzn_profile-profilePath [[Directory structure wp7|was_profile_root]]/pzn_profile-templatePath [[Directory structure wp7|WAS_HOME]]/profileTemplates/default
    UNIX™ ./manageprofiles.sh -create -profileName pzn_profile-profilePath [[Directory structure wp7|was_profile_root]]/pzn_profile-templatePath [[Directory structure wp7|WAS_HOME]]/profileTemplates/default

  3. Change to the WP_PROFILE/ConfigEngine and run the following command to initialize the stand-alone Personalization Server:

    Option Description
    Windows 

      ConfigEngine.bat
 -DPznProfileName=target_profile_name
 action-init-pzn-standalone
 -DPortalAdminId=userID
 -DPortalAdminPwd=foo
 -DWasAdminId=WASuserID -DWasPassword=WASpassword

    UNIX 

      ./ConfigEngine.sh
 -DPznProfileName=target_profile_name
 action-init-pzn-standalone
 -DPortalAdminId=userID
 -DPortalAdminPwd=foo
 -DWasAdminId=WASuserID
 -DWasPassword=WASpassword

  4. Open the WP_PROFILE/ConfigEngine/pzn.properties file and edit the following properties to match new WAS profile to the initialized stand-alone Personalization Server:

      WasSoapPort

        Enter the SOAP_CONNECTOR_ADDRESS value found in the serverindex.xml file of the new WAS profile.

      WpsHostPort

        Enter the WC_defaulthost value found in the serverindex.xml file of the new WAS profile.

      XmlAccessPort

        Enter the port used by the XMLAccess configuration task to connect the XMLAccess server.

      VirtualHostName


      WasUserHome

        Enter the name of the directory where the new WAS profile was created.

      ProfileName

        Enter the name of new WAS profile name.

      CellName

        Enter the name of the new WAS profile cell.

      NodeName

        Enter the name of the new WAS profile node.

      ServerName

        Enter name of the application server for the new WAS profile.

  5. Change to the WP_PROFILE/ConfigEngine and run the following command to install the stand-alone Personalization Server:

    Option Description
    Windows ConfigPzn.bat-DparentProperties=WP_PROFILE/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/ConfigEngine/pzn.properties-DSaveParentProperties=false-DPortalAdminID=portal_uid-DPortalAdminPwd=portal_password-DWasAdminID=WAS_uid-DWasPassword=WAS_password action-install-pzn-standalone }}}

  6. Change to the WP_PROFILE/ConfigEngine and run the following command to remove the stand-alone Personalization Server:

    Option Description
    Windows ConfigPzn.bat-DparentProperties=WP_PROFILE/ConfigEngine/pzn.properties-DSaveParentProperties=false-DPortalAdminId=xyzadmin-DPortalAdminPwd=xyzadminpasssword-DWasAdminId=xyzadmin-DWasPassword=xyzadminpassword action-remove-pzn-standalone }}}
    UNIX ./ConfigPzn.sh -DparentProperties=WP_PROFILE/ConfigEngine/pzn.properties-DSaveParentProperties=false-DPortalAdminId=xyzadmin-DPortalAdminPwd=xyzadminpasssword-DWasAdminId=xyzadmin-DWasPassword=xyadminpassword action-remove-pzn-standalone}}}


Parent

Set up a Personalization server on WAS


Previous

Plan for the Personalization Server

 


+

Search Tips   |   Advanced Search