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. In a two-level hierarchy, you will install individual store servers that should point to the Prism HQ server as the POA. In a three-level hierarchy, you will install one or more child POAs and each child POA should point at the Prism HQ as the POA, and the store servers should point to a child POA.
At each POA or Store server:
[Note: 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, install POA servers first and initialize each POA with data from the HQ server (Prism-to-Prism initialization), then install Store servers and initialize with data from POAs (Prism-to-Prism initialization). In a two-level hierarchy, install the Store servers and point to the HQ server when joining the enterprise.]
1. Install the full Prism stack (Apache, Prism Server, Prism Proxy, Prism DRS).
2. Launch Tech Toolkit and configure the following:
- Tech Toolkit > Connection Manager: Add a connection for the server itself. After adding the connection to the server itself, select it in the Current Connection dropdown.
- Tech Toolkit > Enterprise Manager: Edit the default Controller Number (default = 1) and Controller Name (default = RPS). The Controller Number must be unique.
- Tech Toolkit > Enterprise Manager: Click "Join the Enterprise" and join the server to the Enterprise.
3. Launch the Prism Proxy and 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.
Join POA to the Enterprise
Step 1 - Add Connection for new Server in Tech Toolkit
Launch Prism Tech Toolkit. Log in using the default sysadmin/sysadmin credentials. Add a connection for the server you just installed. This connection will enable the server and its POA to communicate and exchange data. Launch the Tech Toolkit using the desktop shortcut. Windows 10 users must use the right-click "Run as Administrator" option.
Select Toolkit > Connection Manager.
Click the Add button.
Add a Connection for this store server. Select Rest as the Connection Type. Enter a Username and Password. Click OK.
Move the Connection to the top of the list by highlighting the connection and clicking the Up button. Click OK to close the Connection Manager.
Step 2 - Update Controller No, Controller Name
Select the server in the Current Connection dropdown. Click the Enterprise Manager button. Log in using the default sysadmin/sysadmin credentials.
Highlight the server in the list on the left side.
Enter a Controller Name and unique Controller No. Important! The Controller No must be unique within the enterprise.
Save the Changes.
Step 3 - Join the Enterprise
The following prerequisites exist for machines that will participate in a Prism enterprise.
- Must have online connectivity to the POA to manage enterprise data or use enterprise features
- User doing the setup must know the Public/Private addressing information for servers
Click Join the Enterprise.
Define the server that will be the point of authority for this server. By default, Use a custom connection is selected.
Enter the FQDN or IP address of the POA.
Enter a Login name and Password. The login name and password must be entered if a user tries to edit the connection or leave the enterprise.
There is an option to automatically create a connection in the Tech Toolkit Connection Manager for future use. This saves you the trouble of having to go into the toolkit to manually create the connection.
Enter the login credentials that you entered in the setup screen and click OK.
Click Test to make sure the server is connection is good. You will see a dialog announcing that Subsidiary and Store numbering conflicts were found. This is perfectly normal. These will be taken care of later. Click Continue. A check is made to make sure the connection is available.
When the checks are complete, the Execute button is enabled. Click Execute.
When the process is complete, a Success message is displayed. Click OK and then click Close.
The enterprise hierarchy is updated. The server you just added is now listed below the HQ root.
Sub and Store Conflicts
When joining an enterprise, any numbering conflicts with existing subsidiaries or stores are displayed. It is common to have conflicts. In most cases, there is no action that needs to be taken. Later, the Subsidiary and Store numbers can be adjusted at each location to ensure that each server has a unique subsidiary/store combination. The Sub/Store Conflicts dialog tells the user (for example) "Your system includes a Sub 1, Store 001 and you are about to connect to an enterprise that already has a Sub 1, Store 001. Are you sure that's OK?" There will often be this type of conflict in a fresh installation. In most cases, you can ignore the conflict message. Set the store/sub, controller, etc. AFTER joining the enterprise rather than doing it DURING the join process. Click Continue. (The conflicts can be resolved later)
About Server Identity File
A server identity file is a special file that helps a store recover from a hard-drive failure or other catastrophic failure to a server machine. Using the identify server file, the Prism install program will do the work needed so that the machine can claim its former node in the enterprise. If you do not use an identity script to rebuild a controller it will not be able to claim its former node when joining the enterprise. The file contains the necessary SID information to re-install Prism using the same controller, store, subsidiary as before.
Because of the crucial role it plays in restoring a system, you should create the server identity file at the first opportunity. A good time to create the file is when you add the connection (to the server itself) in Technician's Toolkit. After you add the connection, you can then go and export the identity script.
1. Click Export identity script.
2. Select the controller to be exported. Select the type of server: Oracle or MySQL. Change the default export location, if necessary. Click OK. The Prism_Identity_Script.sql is in the user's \Document folder.
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 deployments of fewer than 50 stores, the store servers will be initialized by the HQ and the HQ will serve as the POA for the store servers. In deployments of more than 50 stores, 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. Windows 10 users should use the right-click "Run as administrator" option.
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.
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.