Install POA or Store Server

(Note: This information applies to both POAs and Store servers. If using MySQL as the database, refer instead to the MySQL Guide)
After the HQ server has been installed, initialized and configured, proceed to installing individual child POAs or store servers. Depending on the complexity of the setup, there can be one or more levels of child POAs under the Prism HQ server, with store servers installed under the POAs. In a three-level hierarchy (after installing the HQ), install POA servers before the store servers and initialize each POA with data from the HQ server (Prism-to-Prism initialization), then install Store servers and initialize each store server with data from the store's designated POA (Prism-to-Prism initialization). In a two-level hierarchy, simply install the Store servers and point each store server to the HQ server as the POA when joining the enterprise.

At each POA or Store server:
1.    Install Apache, Prism Server and Prism Proxy).
2.    Navigate to Admin Console > Installation Defaults. Edit the Ctrl No and Controller Name to the desired values.
3. Launch the Prism Tech Toolkit. On the left is a list of servers in the enterprise. Select the HQ server and click the menu button. Select "Add Subordinate Server to [server name]"
4. After adding the server to the enterprise, navigate to Admin Console > Connection Manager. Configure the following:

• Prism Proxy > Admin Console > Connection Manager > Prism Dashboard > Connections: Select the connection to the HQ server and connect to the server.
• Prism Proxy > Admin Console > Connection Manager > Prism Dashboard > Profiles: Create a Prism-to-Prism profile. This profile will be used to initialize the server.
• Prism Proxy > Admin Console > Connection Manager > Prism Dashboard > Initialization: Initialize the POA with data from the HQ Prism server using the Prism-to-Prism profile you created.
• Prism Proxy > Admin Console > Connection Manager > Prism Dashboard > Profiles: After initialization is complete, you can go back and create a Prism-to-Prism profile for replicating data from the POA back to the HQ.
• Prism Proxy > Admin Console > Connection Manager > Prism Dashboard > Connections: Select the HQ connection and click Show Unlinked Profiles. Link the Prism-to-Prism Profile to the HQ connection.

4.    At each installation, create any additional profiles that will be needed for Day-to-Day replication and link the profiles to connections.

 Multi-Subsidiary Installations

In a multi-subsidiary environment, first install the server that you want to be the "root authority" for the enterprise. For example, first install Sub 1 as a standalone, making it the root authority. After Sub 1 is installed, install the server for other subsidiaries. These other subsidiary servers will point to the root authority as their POA. Typically, all the non-root subsidiary servers will initialize with data from the same RIL as the root authority. The individual stores at each subsidiary can point to their own subsidiary server as the POA.

Initialize POA or Store Server (Prism-to-Prism)
In smaller deploymentshe store servers will be initialized by the HQ and the HQ will serve as the POA for the store servers. In larger deployments, the store servers will be initialized by the store's POA.
At the machine that will be the source of the data (e.g. the Prism HQ or POA server), launch Prism using the Prism Proxy desktop shortcut and log in. 
Navigate to Admin Console > Connection Manager > Prism Dashboard > Profiles.
Click the Add button.
In the Type field, select Prism to Prism. Enter a user-friendly Name for the profile. In the Resources area, select the resources to include in the Initialization. You can select each resource's checkbox or click the All link to select all resources. In the screenshot below, the Core Resources are not selected. The Core Resources were already copied to the server during the join-the-enterprise process. In the SBS Filter area, click either All Subs or Specific Subs and select a sub.
Click Save.

After creating the Prism-to-Prism profile, you will have two profiles in the list on the dashboard: the profile you just created and the Core Resources profile. The Core Resources profile was created automatically during the JTE process.
On the Prism Dashboard, click the Initializations tab.  The From Server field displays the server that will be the source database for the initialization. Make sure the correct server is selected. Click in the From Server area. A pop-up for selecting a server is displayed. Select the HQ server.
Confirm that the correct "From Server" is now listed.
Click the Start Initialization button.
You will see a screen that enables you to select the servers to initialize and the profile to use for the initialization. Select the checkbox for the server and select the Profile you created in the dropdown. Click the Start button.
You can view progress status for the initialization.

About Day-to-Day Replication
Day-to-Day (D2D) Replication refers to the sending of data on a regular basis between servers. Unlike initialization, which is typically a one-time operation that sends all available data downstream, Day-to-Day replication occurs on a regular basis, in both directions, and sends only a subset of records.
D2D replication is carried out by creating one or more profiles that include the desired resources and then linking each profile to the correct connection. When creating profiles for D2D, you can send only the specific data types needed by the receiving location. This reduces overhead and replication times. Resources that are unlikely to change, like Departments or Vendors, can be excluded, or sent only occasionally. You can use the Advanced Filters feature to apply fine-grained control over the specific records that are replicated. In certain situations, the same profile that is used for initialization can also be used for D2D replication.

About Core Resources
When you join the enterprise, the system performs a type of mini-initialization and copies a group of resources known as the Core Resources from the POA to the subordinate system. As a result, when you go into the Profiles area on the Prism Dashboard, you will see a Core Resources profile already exists. The Core Resources profile is read-only. After JTE, the core resources do not need to be replicated. If you want to replicate the core resources, you must explicitly create a profile that includes the Core Resources.
Core resources can be replicated in both directions.