Getting Started with Prism
This Getting Started Guide has information about installing Prism and changing basic configuration settings. This guide is divided into the following sections:
- Background information about the Prism enterprise hierarchy structure and system requirements.
- Install RIL and Prism on HQ Server (Root Authority) and initialize Prism (RIL-to-Prism initialization)
- Information about installing Prism on intermediate-level Point-of-Authority (POA) servers and store servers and initializing them with data.
- Information about configuring preferences, security and day-to-day replication of data between servers.
About the Prism Enterprise Hierarchy
When installing Prism, it is important to install the servers from the top down, starting with the Root Authority server for the enterprise.
Every Prism enterprise has a single "HQ" system that serves as root authority for the company's servers. Install Prism on this system first. After Prism has been installed on the root authority system and initialized, proceed to install Prism on other servers. If the enterprise has more than 50 stores, an intermediate layer of Point of Authority (POA) servers is required between the HQ and store servers. Each server (except the Root Authority) must join the enterprise via a Tech Toolkit process. When joining a server to the enterprise, you must identify the server's POA. The POA is the upstream server in charge of enterprise data from the downstream server's point of view. When enterprise data is created/edited at the store level, it is communicated up the enterprise chain to the top, enforcing the synchronization of data throughout the enterprise. Changes made at the HQ flow downstream to POA and store servers. The profiles used for data replication determine which data is sent in each direction. For example, the only data that typically needs to flow upstream from stores are transactions, Z-Out reports, customers and perhaps a few other data types. The HQ is initialized with data from RIL (RIL-to-Prism initialization). POA and store servers are initialized with data from the HQ (Prism-to-Prism initialization). If there are fewer than 50 stores, each store can point to the root as the POA. If there are more than 50 stores, an intermediate-level POA must be installed first, and that intermediate-level POA is the POA that stores will point to when joining the enterprise.
Enterprise Structure Rules and Best Practices:
To access or edit a node, the server must be up and running
Install Prism servers from the top down. Install the Prism HQ (root authority) first and initialize. The Root Authority cannot select a POA
Install the first tier of POA servers after the root is initialized
Intermediate-level POAs required if there are more than 50 stores
Any node other than the root authority can leave an enterprise
A superior node can eject a subordinate node that is offline
Nodes can modify the controller data for themselves and any subordinate nodes
To push data out from a server, you must create a profile and assign it to a connection
At Root Authority (Prism HQ) create a separate profile for each subsidiary to prevent each subsidiary from getting overwhelmed with data from other subsidiaries (if data is not needed)
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
Must be on same RIL and Prism versions for Initialization
The Prism Server requires a minimum of 4GB of RAM (8GB is better and 16GB is even better) and therefore must be run on a 64-bit system; a 32-bit system can host the browser used to connect to a server, or host the Proxy, but not the full Prism server.
Enterprise Hierarchy Notes
- A single "HQ" system serves as the root authority for the company's servers.
- Data created at the HQ flows downstream from the HQ to POAs and on to stores.
- Data created at stores flows upstream to POAs and on to the HQ.
- To send data from one store to another store, data first flows upstream to the POA and/or HQ and then downstream to the destination node.
- A server's Point of Authority (POA) is the upstream server in charge of enterprise data (from this server's point of view). In a deployment of fewer than 50 stores, the HQ server can serve as the POA for the store servers. Deployments of more than 50 stores require an intermediate POA level between the HQ and store servers. Data is sent downstream by the HQ to the POA and then from the POA to the store server(s). Data is sent upstream by the stores to the store's designated POA and then from the POA to the HQ.
- At the store level, a profile will be created to communicate daily with the POA (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. When data is created/edited at the store level, it is communicated up the enterprise chain to the top. Store servers are not allowed to replicate data directly with each other; instead, the data must first flow up the hierarchy to the POA and then back down the hierarchy to the target store.
About Joining the Enterprise
All servers other than the Prism HQ server must go through the Join-the-Enterprise process. Joining the Enterprise adds the server as a new node to an enterprise hierarchy. As part of the JTE process, the user must identify each server's POA. The server must have online connectivity to the POA and the user doing the configuration must know the IP addresses or FQDNs. The Prism HQ root does not have a POA.
Initialization is the process of loading a new Prism server with data. In the case of the Prism HQ server, the data that is loaded comes from a source RIL Oracle database using an RIL-to-Prism profile. In the case of a POA or Store server, the data comes from an existing Prism server using a Prism-to-Prism profile.
The amount of time required to initialize Prism will depend on the size of your database, especially the size of inventory and customers. The larger the data set, the more time is required. Please set aside enough time for initialization to complete. Initialize servers in the proper order, starting with the PrismHQ server at the top of the hierarchy and then POAs, and then store servers.
Replication Best Practices
- Install Prism servers from the top down. Install the HQ (root authority) first and initialize, then install child POAs, join each to the enterprise and initialize. After that, install store servers, join each to the enterprise and initialize. Each POA should point to the Prism HQ server; each store server should point to its POA server.
- Install the first tier of POA servers after the root is initialized.
- Edit the default Controller Name and Controller No of POA servers in Tech Toolkit BEFORE you install store servers. Edit the default Controller Name and Controller No of Store Servers before initializing.
- To access or edit a node, the server must be up and running.
- To send data out from a server, you must create a profile and link it to a connection.
- Nodes can modify the controller data for themselves and any subordinate nodes (in Tech Toolkit).
- To initialize a node, the node must be on the same Prism version as the POA.
- Any node other than the root authority can leave an enterprise; a superior node can remove a subordinate node that is offline via the "Remove Subordinate" option in Tech Toolkit
- Before leaving the enterprise, disconnect the server's RIL connection(s) by clearing the "Connected" checkbox in Admin Console > Connection Manager > RIL Dashboard. If a server leaves and then later rejoins the enterprise, the server must rejoin in the same position as before. In other words, once the enterprise structure has been set, it shouldn't be rearranged.
- Avoid generating unneeded traffic by being careful about what data is replicated and where it is sent. For example, if you turn on replication of all resources at every location, it could cause the replication message queues to back up and prevent data from being delivered in a timely manner.
- Prism-to-Prism replication should be the primary form of replication and should be turned on in all directions for all servers. Only the HQ server should replicate data with Retail Pro Integration Layer (RIL). [Note: This recommendation may be modified by the Retail Pro Professional Services team based on the size and complexity of the installation.]
- You cannot send documents directly from one store to another. A POA can create documents and send them to stores, and a store directly under the POA can create documents and send them to the POA; however, two stores under a POA cannot send documents to each other without first going through the POA.
- Certain fields that update quantity and cost are designated as protected fields. These protected fields will update values at a subordinate server when replicated from a POA to a subordinate. When data is replicated from a subordinate to a POA, the protected fields are not updated. See the "Protected Fields" section.
- If you have any special characters in your RIL records, those records will NOT be replicated. Special characters are characters such as: -@ $ * ! " & ~ ' ? ` [ ] \ =.
Maximum Length of Machine Names
The machine name must be 15 characters or less. Machine names of more than 15 characters are not supported at this time. For example, if installing to mymachinename.mycompany.com, the "mymachinename" segment is 13 characters and is supported. If you tried to install to "mylongmachinename.mycompany.com", the segment is 17 characters and not supported.
Install RIL and Prism on HQ Server
This section explains how to install and setup the Prism server on the HQ server machine. The HQ server should be the first server installed. It will serve as the "root" data authority for the enterprise. You can download the needed Prism installation files by logging into your account at my.retailpro.com
On the Prism HQ server, navigate to the location of the downloaded installation files. Launch the Autorun.exe application. You will see a screen for installing individual RIL and Prism components.
|Apache||As a web-based application, Prism requires a web server. The current version of Prism uses Apache 2.4.43.|
|Prism Server||The RP Prism server is the data repository used by web clients. You can install the RP Prism server on the same machine as the RIL Oracle database or a different machine. You have two database options for the Prism Server: Oracle or MySQL.|
|Prism Proxy||The Prism Proxy enables a Prism web client to communicate with printers, cash drawers and other hardware devices that are on a workstation connected to a Prism server. Launch RP Prism via the Proxy.|
|Prism DRS||Install Retail Pro Prism DRS on the machine where the source RIL Oracle is installed. This may be the same machine as the Prism server or a different machine. The Retail Pro Prism DRS program is used for replicating data between an RIL Oracle database and Prism. If you are using MySQL as the database, don't install DRS.|
|Document Designer||The Prism Document Designer enables users to edit the default Prism document designs (e.g. receipt designs) used when printing documents.|
|Technician's Toolkit||The toolkit is installed automatically when you install the Prism server, so most installations won't need to run this installer. This install option enables you to install the toolkit on a Proxy only machine.|
Before installing and initializing the Prism HQ server, review this checklist to make sure your system is optimized for the initialization process.
- Make sure the server machine has adequate number of CPU Cores and Memory (minimum 2 CPU cores and 4GB or RAM). The more CPU cores and memory available, the faster initialization will complete.
- Run Windows Updates and reboot the machine.
1. Install Apache, Prism Server, Prism Proxy and Prism DRS, in that order (Document Designer is optional).
2. Launch the Prism Proxy using the desktop shortcut and log in using sysadmin/sysadmin credentials. Configure the following:
- Admin Console > Installation Defaults: Edit the Controller Name and RIL Address and save the changes.
- Admin Console > Connection Manager > RIL Dashboard: If you added the RIL Address in Installation Defaults, the server name will be available in the dropdown. If you did not add the RIL Address in Installation Defaults, click the "Add a New Connection" button, add the server name, save, and then select the server from the dropdown. Additional tabs on the RIL Dashboard become available.
- Admin Console > Connection Manager > RIL Dashboard > Profiles: Create an RIL-to-Prism initialization profile.
- Admin Console > Connection Manager > RIL Dashboard > Initializations: Initialize the Prism HQ server with data from RIL using the created profile.
- Admin Console > Connection Manager > RIL Dashboard > Connections: Select the RIL connection. Link the RIL-to-Prism Profile to the RIL connection. Click the Plus sign icon and add a Prism-to-RIL profile for sending data back to RIL. Link the Prism-to-RIL profile to the connection
4. Log out and log back in using your Prism username and password.
5. Configure any Prism preferences and permissions that you want to propagate to the POAs or Store servers that will subsequently be installed.
6. Install subsequent servers.
On the Autorun.exe menu, click Apache 2.4.43. The Installer will first check to make sure that you have the required Visual C++ runtime library. Click Yes to install the runtime library. After the required Visual C++ runtime library is installed, the installer's Welcome screen is displayed.
On the Welcome screen, click Next >. The Apache License Agreement is displayed.
On the License Agreement screen, select I accept the agreement. Click Next >.
You must enter an email address during the install.
Click Next >. The Ready to Install screen is displayed.
When the install is complete, click Finish.
Install Prism Server
The Prism Server can be installed using either Oracle or MySQL for the database. When you install the Prism server and select Oracle as the database type, the installer will check to make sure that RIL is already installed. If RIL has not yet been installed, the install will fail. For both Oracle and MySQL, the installer will make sure Apache is installed.
On the Autorun.exe menu, click Prism Server. The Installer launches.
Click Next >. The Server Location screen is displayed. In the Server Name field, enter the FQDN of the server machine. The SSL Port is set to 80. This means that Prism will use HTTP (not HTTPS). (If you have SSL certificates, change the SSL Port to 443 and install the certificates later using the Tech Toolkit SSL Manager.)
Click Next >. The Server Database Connection screen is displayed.
When installing the Prism server, you are prompted to select the type of server to install.
Oracle: The default choice is Oracle . This means that you will be initializing Prism using the data on an RIL (or RP9) Oracle database.
MySQL: Select the MySQL option if you will be using a MySQL database with this Prism server. (Refer to the Prism MySQL Guide document for instructions.)
Click Next>. The Server Identity File screen is displayed.
This checkbox is used when the machine previously had Prism installed and you need to install Prism again. In that case, you need to select the checkbox and navigate to the server identity file. Unless the install you are doing fits into that situation, you can leave the box unchecked and click Next >.
The next screen asks if you have the Erlang programming language installed. The RabbitMQ messaging software that Prism uses is coded in Erlang; therefore Prism requires Erlang to be installed. Select the "No" radio button and click Next >.
Prism uses the RabbitMQ messaging software. The next screen asks if you have RabbitMQ installed. Click No and then click Next.
Confirm the install folder for the RabbitMQ database. Click Next.
Click Install to start the install process. (If you want to double-check the settings, you can click the < Back button to go back and review.) The Prism server takes a few minutes to install.
As you near the end of the installation, you are first prompted to select a default language.
After selecting a language, click Next >.
You are next prompted to select the Regional Settings. This determines things like how dates and large numbers are displayed.
Click Finish when done.
Install Prism Proxy
Click the Prism Proxy button on the Autorun.exe menu. The install program checks if you have Visual C++ installed. If not installed, the program will display a prompt to install Visual C++. Click "Yes" to install if prompted.
The Welcome screen is displayed.
Click Next >.
The server name is automatically populated with the name of the Prism server on the machine.
Click Next >.
Enter the number of proxies that the workstation will use. (Note: Each Proxy will need to be assigned to a separate port on the following screen).
Assign a different port to each proxy. Default = 8080.
Select "Create a desktop icon." This will place an icon on the desktop that you can use to launch Prism. If you forget to create the desktop icon or don't want it, you can always launch Prism from the C:\Program Files (x86\RetailPro\PrismProxy folder.
Click Finish when the installation is complete. Oracle: Proceed to install DRS.
Install Prism DRS
Install the Prism DRS at installations that need to replicate data with an RIL Oracle server. This is typically only the root authority (HQ) server. If the installation will not replicate data to Oracle (e.g. a MySQL installation), then do not install Prism DRS.
Scroll down the list of components and click the Retail Pro Prism DRS button. The DRS installer launches.
Click Next >. The Server Location screen is displayed. The Prism Server Name should be entered automatically.
Confirm the Server Name is correct and click Next >.
When the installation is complete, click Finish.
Start RP Prism
Always launch Prism using the Proxy shortcut (if installed). Windows 10 users must use the right-click "Run as Administrator" option.
Prism launches using the default browser and connects via the Port entered during installation of the Proxy.
Enter your username and password. Click the Login button. The first time you start Prism after installing, log in using the default sysadmin/sysadmin username/password combination. Use these default credentials to initialize. After initialization, clear the browser cache, enable permissions for groups, log out and then log back in using your regular Retail Pro username/password.
Click the Retail Pro button (lower-right corner) and select the desired area from the Prism Menu.
Change Controller Number, Controller Name of HQ Server
After installing the Prism HQ server machine, launch the Prism Proxy and navigate to Admin Console > Installation Defaults. Change the RIL Address to the hostname or IP address of the source RIL Oracle. The Controller Name and RIL Address should not be the same computer name.
Initialize Prism HQ with Data from RIL Oracle
Next, navigate to Admin Console > Connection Manager. If you added the RIL Address in Installation Defaults, then you can select the server from the Server Address dropdown. If you didn't, you will have to click the Add \ Edit Local RIL Server Button and type the Server Address.
The Server Address should match the RIL Address that you entered under Installation Defaults, if you entered it there. Click Save.
Select the server from the drop-down and click the Connect button. Wait a few seconds as the connection is established.
When the connection between the two servers is established. Additional tabs become available on the RIL Dashboard.
Click the Profiles tab. Click the Add button.
The Add Profile screen is displayed. Enter a Name for the profile and select the specific resources that should be sent during initialization. By default all subsidiaries are included. To only initialize the server with data from specific subsidiaries, click the Specific Subs button and make the selections.
Save the profile.
Click the Initializations tab on the RIL Dashboard. Select the RIL server in the dropdown and click Start Initialization.
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.
Initialization can take a long time for larger databases and can sometimes fail to complete successfully. If an initialization fails or is stopped for whatever reason, create a new Sender profile that starts from the resource after the last COMPLETED resource. For example, if the initialization was in the middle of the Inventory resource when the failure occurred, the new Sender profile should include Inventory and the rest of the resources to the bottom of the list. Run initialization again using the new Sender profile.
When you create a new Sender profile and restart, it may take a while to process the first resource (the resource that was being initialized when the failure occurred). This is because the program must do a slower UPDATE operation on each of the resource's records that are already in the tables. Once the program finishes the updates and reaches the unprocessed records for the resource, it switches to the much faster INSERT operation. There currently is no way to restart a failed/stopped initialization from the specific point of failure. The entire resource in which the failure occurred must be sent again.
POA Server Installation and Configuration
Install Prism Components on POA Server
Install the Prism server on the POA machine. The steps are the same as when you installed the Prism server on the HQ machine. Refer to the "Installing Prism server at HQ" section for information.
Change Controller Number, Controller Name of POA Server
At the POA server, launch Prism using the desktop shortcut and log in.
Navigate to Admin Console > Installation Defaults.
Enter the desired Controller Number and Controller Name.
Save the changes.
Add/Join Server to Enterprise
All servers other than the Prism HQ server must go through the Add Server/Join-the-Enterprise process. Joining the Enterprise adds the server as a new node to an enterprise hierarchy. As part of the JTE process, the user must identify each server's POA.
The server must have online connectivity to the POA and the user doing the configuration must know the IP addresses or FQDNs.
1. At the HQ server machine, launch. To access Tech Toolkit, enter the following in the browser address bar:
A list of prism servers is displayed on the left side of the screen. If this is the first POA server and it is yet to join the enterprise, only the HQ's own server will be listed.
Highlight the server and click the hamburger icon. Select Add Server.
2. On the Identity screen, enter the IP Address or FQDN of the server that is joining the enterprise. Enter the username and password that will be used to connect to the server.
Click the arrow button to proceed.
3. Prism will attempt to connect to the new server. Notice that the Controller Number and Controller Name match the Installation Defaults entered on the POA1 server.
On this screen, you can edit the Controller Number and Controller Name, if needed.
Click the arrow button to proceed.
4. When you click the arrow button, the JTE process starts.
As part of the JTE process, core resources are imported. The core resources are certain basic resources that are required for initialization. When the initialization of Core Resources is finished, click the checkmark button to finish.
The server you added is now listed in the menu. The new server's listing is indented to show that is located under the HQ server in the enterprise hierarchy.
Initialize POA Server
At the HQ machine, launch the Prism Proxy using the desktop shortcut and log in.
Navigate to Admin Console > Connection Manager > Prism Dashboard > Profiles.
Create a profile that will be used to initialize the POA server with data.
After adding the Profile, click the Initializations tab. In the From Server field, select the server that will be the data source for the initialization. In this example, the HQ server is the data source.
Click Start Initialization.
Select the Profile that will be used to initialize the new server.
Select the check box for the server to be initialized.
You can monitor the progress.
When the initialization of each POA is complete, proceed to add store servers.
Store Server Installation and Configuration
Install Prism Components on Store Server
The process for installing and configuring a store server is basically the same as for a POA. The only difference is store servers typically only replicate upstream a few selected types of records: e.g., documents, customers and x/z-out reports.
- Oracle database users: Install the Prism components on the Prism server as described in the Installing Prism Components on HQ Server section.
- MySQL database users: Install the Prism components as described in the Prism MySQL Guide.
Configure Controller Number, Controller Name
Launch Prism using the Prism Proxy desktop shortcut.
Navigate to Admin Console > Installation Defaults.
Enter the desired Controller Name and Controller Number. The Controller Number must be unique within the enterprise. Save the changes.
Join the Store Server to Enterprise
At the POA Server, launch Tech Toolkit by pointing the web browser to
Click the POA Server and select Add Server from the menu.
On the Identity screen, enter the IP Address, hostname, or FQDN of the server being added. Enter the username and password that will be used to connect to the server.
Click the arrow button to proceed.
The POA will attempt to connect to the new server using the entered credentials.
If successful, the Verify screen will show the New Server Information. Notice that the Controller Name and Controller Number match the Installation Defaults that were entered at the server.
Enter the POA Login credentials.
Click the arrow button to proceed.
The POA will initialize the new server with core resources. This is a type of "mini-initialization" of certain resources that need to be in place before initialization.
When the initialization of core resources is complete, click the checkmark button.
Refresh the browser.
The Tech Toolkit shows the new server under its POA in the enterprise hierarchy.
The icons next to each server indicate that the new server has a connection to its POA, but not to the HQ.
Log out of Tech Toolkit.
Initialize Store Server (Prism-to-Prism)
At the POA, 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.
Create a profile that will be used to initialize the store server.
At the POA, navigate to Admin Console > Connection Manager > Prism Dashboard > Initializations.
In the From Server field, make sure the correct POA server is selected. (Click in the field to select a different server)
Click Start Initialization.
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.
When initialization is complete, at the store server create a sample transaction to confirm the initialization was successful.
Summary of Profiles Created
|RIL-to-Prism||Initialization of Prism HQ by RIL Oracle||At the HQ, on the RIL Dashboard, create an RIL-to-Prism profile that sends all data to the Prism HQ.|
|Prism-to-RIL||Day-to-Day replication from Prism HQ to RIL Oracle||At the HQ, on the RIL Dashboard create a Prism-to-RIL profile for sending transactions and other documents upstream to the RIL Oracle server.|
|Prism-to-Prism||Initialization of POA or Store Server by Prism HQ||At the HQ, on the Prism Dashboard create a Prism-to-Prism profile for each POA to send data downstream.|
|Prism-to-Prism||Initialization of Store Server by POA||At each POA, on the Prism Dashboard create a Prism-to-Prism profile for initializing store servers with data from the POA.|
|Prism-to-Prism||Day-to-Day Replication with Prism HQ||At each POA, on the Prism Dashboard create a Prism-to-Prism profile for sending transactions and other documents upstream from the POA to the HQ server.|
|Prism-to-Prism||Day-to-Day Replication with Stores under POA's control||At each POA, on the Prism Dashboard create a Prism-to-Prism profile for sending data downstream to the stores under the POA's control. To limit the amount of data replicated to stores, you can create a separate profile for each store and use an Advanced Filter to only send the records needed by that store.|
|Prism-to-Prism||Day-to-Day Replication with POA||At each Prism store, create a profile to send the data created at the store upstream to the store's Point of Authority (POA). This profile only needs to send a few types of data. Specifically, the profile should include the document, customer, zoutcontrol, drawereventhistory and employee resource.|
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.
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.
Additional Getting Started Info
Users are responsible for providing their own SSL certificates to run Prism using HTTPS. You must purchase your own SSL certificates from a certificate authority and then install the certificates using the SSL Manager tool in Tech Toolkit.
Employee Management and Security
When you first install Prism, a single default employee group called the Administrator group is created. This default Prism Administrator group enables users to log in to Prism the first time and initialize the system (default login credentials are sysadmin/sysadmin). When you initialize Prism, employee groups are copied from the Point of Authority (POA) to the new server. The default Administrator group, having served its purpose, is overwritten during initialization.
After initialization is complete and permissions are assigned, you can customize Prism preferences to best meet the needs of your business. Preferences enable retailers to customize various aspects of the program workflow and interface. Configuration of preferences is required for using certain RP Prism features, such as Promotions, Loyalty, EFT, Centrals and Send Sale. Key settings that you will want to define right away include:
• Document sequence numbers
• Tax Method (Sales Tax or VAT)
• Tender Requirements (allowed tenders for payment, change, returns, etc.)
For information see the RP Prism Admin Console document.
Exclude Prism from Anti-Virus Scans
This section provides information about excluding Prism folders from scans performed by anti-virus programs. This includes but is not limited to Windows Defender. If users fail to exclude Prism folders from the scans performed by anti-virus programs, program performance can be severely impacted.
Exclude the following folders from any anti-virus programs.
|Exclude Apache||C:\Program Files (x86)\Apache Software Foundation|
|Exclude RabbitMQ||C:\Program Files (x86)\RabbitMQ Server|
Limitations on Windows 10
- The Proxy must be launched using right-click "Run as Administrator" option.
- Windows World Wide Web Publishing Service must be disabled
Uninstalling RIL and RP Prism
If you need to uninstall RIL and RP Prism, remove each component, including the Apache Server, using the Windows Control Panel or an uninstall program (e.g. Revo Uninstaller). After uninstalling the components, be sure to remove any registry keys related to RIL, RP Prism and Apache. If registry keys remain, you will not be able to reinstall RIL and RP Prism.
For effective communication between web clients and the Proxy, the Proxy should point at a server on the local network. This enables the proxy to fulfill its primary purpose, which is enabling web clients in the POS lanes to communicate with printers and other POS hardware. If you need to change the server to which the Proxy points, first uninstall the Proxy and then reinstall the Proxy, this time pointing to the desired local server.