Installation Defaults

The Installation Defaults area provides a convenient way to update the Controller Name and other key information stored in the CONTROLLER table. Being able to modify the information in the CONTROLLER table is important during certain operations like restoring Prism from a backup after a system failure. By default, the Controller Name is set to "RPS" and the Ctrl No is set to "1." These defaults should be changed. The Ctrl No must be unique in the enterprise. For example, if the Ctrl No of the ROOT is left at the default "1," then the Ctrl No of the other servers will need to be modified. The Controller Name should be changed from the default RPS to something that makes it easy to identify the server and its role (e.g., POA1). If the server will be using the "Centrals" service, then enter a FQDN or IP Address for the Centrals Server.

Specifically, you can:

• Modify the default Controller Name
• Select a default Subsidiary and Store
• Define the Centrals server address

Controller Name
By default, a new Prism server is assigned a Controller Name of RPS. You can and should rename the Controller to an easily identifiable, unique name before joining the server to the enterprise; otherwise, all installations will have the same name "RPS" and it will be hard to tell installations apart when working with replication or in Tech Toolkit.

Default Subsidiary, Default Store
The selections you make here will affect the Subsidiary and Store to which any NEW proxy installs will be assigned. The subsidiary that is selected determines which stores will be available for selection in the Default Store drop-down.
When a new Proxy is installed, the Controller table gets the Subsidiary and Store values from the current values in Installation Defaults. For example, if Proxy 1 was installed with Installation Defaults set to Sub1Store1, then Proxy 1 will be assigned to Sub1Store1.
What happens if Installation Defaults are changed and after the change a user installs a new Proxy? If a user edits Installation Defaults to Sub2Str2 and then installs another Proxy (multi-Proxy), when Proxy 2 is launched, it will be assigned to Sub2Store2. Proxy 1 will still point to Sub1Str1. To change the Subsidiary and Store assignment in that case, you will have to edit the Workstation record in the Node Selection area. Select which Store will be the default when a user installs the Prism Proxy. The selected Default Subsidiary determines which stores are available for selection in the Default Store drop-down.

Central Address
All machines using Prism Centrals must enter the FQDN, hostname or IP Address of the Centrals server in Admin Console > Installation Defaults. The Centrals server settings in Installation Defaults are not replicated, so be sure to enter the correct Centrals server settings, including Port, Timeout, and Interval at each workstation that will be using centrals. In Prism 2.3 and later, the Central Address field is a dropdown that lists servers joined to the enterprise.
Any Prism server can act as the Centrals Server. Other Prism servers that need Centrals services, will connect to the selected server as the Centrals server using the standard Prism API's. Keep in mind however, that when acting as the Centrals server, the data Centrals can return to any request is limited by the data it has in its local database. For example, if the data from other stores is not being replicated to the Centrals server, it may not be able to find the data it needs to fulfill the request. For this reason, we recommend that the Root Authority be selected as the Centrals server. Alternatively, you can have all data that will be needed by Centrals, replicated to the server of your choice and use that server as the Centrals server.

Port
Centrals server port. The port to use for communication with the centrals server. Default - 50025

Timeout
Centrals server timeout. The number of seconds Prism will attempt to establish a connection to the centrals server. If the connection cannot be established, the system will wait the designated interval time and then try again (up to the designated number of retry attempts). Default = 30

Interval
Resiliency Check Interval. The number of seconds Prism will wait between checks to see if the link to the centrals server has been restored. Default = 10
Sample Installation Defaults