Skip to Main Content
Return to Navigation

Reconfiguring Replicated Environment Management Components

This section discusses how to:

Reconfiguring an Environment Management Agent

Configuring PSEMAgent in a replicated PS_HOME involves deleting the agent local cache and modifying the PS_HOME location specified within the PSEMAgent configuration files.

Note: New_PS_HOME refers to the directory where PeopleTools is located in yourreplicated environment. If the same PS_HOME location is used by your source and destination environment, you do not need to make any changes.

To reconfigure the agent:

  1. Delete all subdirectories below New_PS_HOME\PSEMAgent\envmetadata\data\

    Note: Don’t delete the matchers.xml file in this location.

  2. Delete the following directories:

    • New_PS_HOME\PSEMAgent\envmetadata\PersistentStorage

    • New_PS_HOME\PSEMAgent\envmetadata\scratchpad

    • New_PS_HOME\PSEMAgent\envmetadata\transactions

  3. Modify StartAgent.bat (Windows), or StartAgent.sh (UNIX).

    Ensure that references to the drive and path of the PSEMAgent directory are correct for the New PS_HOME location.

  4. Modify StopAgent.bat (Windows) or StopAgent.sh (UNIX).

    Ensure that references to the drive and path of the PSEMAgent directory are correct for the New PS_HOME location.

  5. Verify the settings in the agent configuration file: New_PS_HOME\PSEMAgent\envmetadata\config\configuration.properties.

    Properties that specify path locations must be valid for the replicated agent in its new location, but the same hub is still addressed by all agents.

    • hubURL

    • windowsdrivestocrawl

    • unixdrivestocrawl

Reconfiguring the Environment Management Hub

The Environment Management hub is replicated as part of replicating the web server environment. After redeploying PeopleSoft Internet Architecture, clear the cache by performing the instructions below:

Note: New_PIA_HOME is the directory where PeopleSoft Internet Architecture is located in your replicated environment.

To reconfigure the hub:

  1. Delete all subdirectories below New_PIA_HOME\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\data\

    Note: Don't delete the data.txt file in this location.

  2. Delete the following directories:

    • New_PIA_HOME\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\PersistentStorage

    • New_PIA_HOME\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\scratchpad

    • New_PIA_HOME\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\transactions

Reconfiguring the Environment Management Viewer

In the replicated environment, local cache files need to be cleared for the New_PS_HOME\PSEMViewer directory.

Note: New_PS_HOME is the directory where PeopleTools is located in your replicated environment.

To reconfigure the PSEMViewer:

  1. Delete all subdirectories below New_PS_HOME\PSEMViewer\envmetadata\data\

    Note: Don't delete the files in this location, just the subdirectories.

  2. Delete the following directories:

    • New_PS_HOME\PSEMViewer\envmetadata\PersistentStorage

    • New_PS_HOME\PSEMViewer\envmetadata\scratchpad

Updating the GUID Value of Cloned Databases

When copying databases, it is extremely important to delete the GUID value in the new (copied) database. If not deleted, the hub will assume that the old and new environments are the same, leading to confusing environment records. To resolve this, set the value of the GUID field in the PSOPTIONS table to <space> in the cloned database using the SQL tool at your site. The next time an application server connects to the database, the system generates a new, unique GUID for the cloned database.