Preparing the servers for initial staging

You must set up your production servers before you move content from the staging server to the production server. The steps remove any release content from these servers to prepare them for the import of the release data. It is assumed that these servers are fresh installed servers. The servers must not contain any customization data. Complete all database and security configurations.

1. Install and configure WebSphere® Portal on the production server. This step includes database and security configurations.
   Attention: Ensure that your database and security configurations match on the staging and production servers.
2. Log on to the production server and delete all existing Web Content Manager Libraries.
   Go to Administration > Web Content Libraries. Click Delete library for each library on the system.

   Attention: Edit any libraries that have the option Prohibit library from being deleted. Clear that option before you delete them.
3. Open a command prompt and change to the wp_profile_root/ConfigEngine directory.
4. Create your virtual portals on the production servers with the same parameters from the staging system. For example, run the following command
   Tip: Run the list-all-virtual-portals task on the source system to retrieve the virtual portal parameter values.
   • AIX® Solaris Linux:

     ./ConfigEngine.sh create-virtual-portal -DWasPassword=password -DPortalAdminPwd=password -DVirtualPortalTitle=VirtualPortalTitle -DVirtualPortalContext=VirtualPortalContext -DVirtualPortalID=VirtualPortalShortID -DVirtualPortalObjectId=VirtualPortalOID

   • IBM® i:

     ConfigEngine.sh create-virtual-portal -DWasPassword=password -DPortalAdminPwd=password -DVirtualPortalTitle=VirtualPortalTitle -DVirtualPortalContext=VirtualPortalContext -DVirtualPortalID=VirtualPortalShortID -DVirtualPortalObjectId=VirtualPortalOID

   • Windows:

     ConfigEngine.bat create-virtual-portal -DWasPassword=password -DPortalAdminPwd=password -DVirtualPortalTitle=VirtualPortalTitle -DVirtualPortalContext=VirtualPortalContext -DVirtualPortalID=VirtualPortalShortID -DVirtualPortalObjectId=VirtualPortalOID

   • z/OS®:

     ./ConfigEngine.sh create-virtual-portal -DWasPassword=password -DPortalAdminPwd=password -DVirtualPortalTitle=VirtualPortalTitle -DVirtualPortalContext=VirtualPortalContext -DVirtualPortalID=VirtualPortalShortID -DVirtualPortalObjectId=VirtualPortalOID

5. For CF05 and below only - Complete the following steps to manually delete the Portal Site library from the virtual portals:
   1. Open a command prompt and change to the wp_profile_root/PortalServer/bin directory.
   2. Run the following task to start a Portal Scripting Interface command prompt:
      • AIX Solaris Linux:

        ./wpscript.sh -username userid -password password

      • IBM i:

        wpscript.sh -username userid -password password

      • Windows:

        wpscript.bat -username userid -password password

      • z/OS:

        ./wpscript.sh -username userid -password password

   3. Run the following command to set the virtual portal as the active context:

      $Portal setvp VirtualPortalContext

   4. Run the following command to log in to the Virtual Portal:

      $Portal login userid password

   5. Run the following command to list the current libraries:

       $DocumentLibrary listall

      The following example is the command result:

      wsadmin>$DocumentLibrary listall
      "portal site"

   6. Run the following command to show the details of the library:

      $DocumentLibrary details "portal site"

      The following example is the command result:

      wsadmin>$DocumentLibrary details "portal site"
      uuid               : TWFuYWdlZCBQYWdlcyBSb290IExpYnJhcnk
      name               : portal site
      title              : Portal Site
      decommandion        :
      enabled            : true
      deletion prohibited: true

   7. Run the following command to set the deletion prohibited flag to false:

      $DocumentLibrary set "portal site" deletionprohibited false

   8. Run the following command to show the details of the library to ensure that it can be deleted:

      $DocumentLibrary details "portal site"

      The following example is the command result:

      wsadmin>$DocumentLibrary details "portal site"
      uuid               : TWFuYWdlZCBQYWdlcyBSb290IExpYnJhcnk
      name               : portal site
      title              : Portal Site
      decommandion        :
      enabled            : true
      deletion prohibited: false

   9. Run the following command to delete the "portal site" library from the virtual portal:

       $DocumentLibrary delete "portal site"

6. Run the following command on the production server to empty the portal contents:
   • AIX Solaris Linux:

     ./ConfigEngine.sh empty-portal -DWasPassword=password -DPortalAdminPwd=password

   • IBM i:

     ConfigEngine.sh empty-portal -DWasPassword=password -DPortalAdminPwd=password

   • Windows:

     ConfigEngine.bat empty-portal -DWasPassword=password -DPortalAdminPwd=password

   • z/OS:

     ./ConfigEngine.sh empty-portal -DWasPassword=password -DPortalAdminPwd=password

   Attention: If you try to access your WebSphere_Portal server after you run the empty-portal task, an error displays on your browser that indicates that no content is available. You can ignore this message. It displays until you import another configuration onto the server.