Introduction

...

1. Click on the Access navigation tab.

2. Click on the User Access Groups, Floor Access Groups or Guest Access Groups link.

3. In the Actions bar, click on Add Access Group. The following screen is displayed:

   

4. Enter a Name and a Description.

   

5. Select the Risk Levels during which this group will have access: Low, Guarded, Elevated, High or Severe (the current risk level is always displayed at the top of the Primis screen)
   For more information on Risk Levels see the Alert Level Managementsection.

6. Select a Controlled Area for this group.

7. Select a Schedule for the Controlled Area. If that controlled area is not going to be accessed by that User Access Group, leave the schedule as Always Off.

8. If you need an additional line for extra Controlled Areas and/or Schedules, click the + button beside the current line. To delete a line, click the x button.

9. Click Save.

Global User Access Groups

...

1. Create a new Controlled Area with the elevator reader.

2. In the new Controlled Area’s Floor tab, select all the associated Floor Areas; specify the desired activation time and click +.

...

Create a Floor Access Group

...

1. Configure the firewall to allow incoming connections on port 31415.

2. Login to the Primis administration software using the system user.  Call Identiv Support if you need the system password.  

3. Click on the System navigation tab.

4. On the left, click on the Administration link.

5. Click on the System Parameters sub link.
   

   

6. Click on the siteEngine.ini file to edit it.

7. Edit the line that reads DBMode=single and change it to DBMode=master principal
   

   Image RemovedImage Added

8. Click Save.

9. Select and edit a different System Parameters file called start.ini

10. Edit the line that reads #sds.service=no and change it to sds.service=yes
    

    Image RemovedImage Added

11. Click Save and Reboot the server.

12. Once the system is rebooted, log back in with the system user and go to the System tab.

13. In the scope pane on the left, click on Utilities.

14. Click DB Replication.
    

    

15. Fill in the text boxes on the screen. 

    1. Host Name: This is the IP address of the master principal server.

    2. Sync Name: Name for the configuration. Enter something that will identify the master principal server. This field must be alpha-numeric.

    3. Sync Protocol: Select http or https. In order to use https, additional configurations are required to install SSL certificate on the master principal and slave replica server.

    4. Sync Port Number: Select the TCP port number that slave replica servers will be connecting to.  The TCP port number selected must be configured in the firewall to allow incoming connection. The Primis server is preconfigured to support port 31415, additional configurations on the server are required if other port number is used.

16. Click the Save button.  The master principal node configuration will be displayed in the Master Principal Node section. The Delete button of the master principal node allows users to remove the master principal configuration from the server. It will be disabled if there are slave replica nodes attached to the masterprincipal. The Stop Replication button allows users to stop the database replication process. The Restart Replication button allows users to restart the database replication process. The Refresh Server Cache button allows users to refresh the Primis server cache to the slave replica nodes.
    

    Image RemovedImage Added

Configuring

...

Replica Server

1. Login to the Primis administration software using the system user.  Call Identiv Support if you need the system password.  

2. Click on the System navigation tab.

3. On the left, click on the Administration link.

4. Click on the System Parameters sub link.
   

   

5. Click on the siteEngine.ini file to edit it.

6. Edit the line that reads DBMode=single and change it to DBMode=slave replica
   

   Image RemovedImage Added

7. Click Save.

8. Select and edit a different System Parameters file called start.ini

9. Edit the line that reads #sds.service=no and change it to Change to sds.service=yes
   

   Image RemovedImage Added

10. Click Save and Reboot the server.

11. Once the system is rebooted, log back in with the system user and go to the System tab.

12. In the scope pane on the left, click on Utilities.

13. Click DB Replication.
    

    

14. Fill in the text boxes on the screen.

    1. Master Principal Node Registration URL: The URL that the slave replica server will be connecting to for data replication. The URL should be set to the Sync URL configured on the master principal server.

    2. Sync Name: Name for the configuration. Enter something that will identify the slave replica server. This field must be alpha-numeric.

15. Click the Attach button. The slave replica node configuration will be displayed in the Node section. The Detach button allows users to remove the node from the data replication. Detaching a slave replica node is a two steps process, refer to the Detaching Slave Replica Server section below for details. The Stop Replication button allows users to stop the database replication process. The Restart Replication button allows users to restart the database replication process.
    

    

16. To verify the slave replica server is configured properly, login to the master principal server and go to the System tab. Click on Utilities on the left and select DB Replication.  The client node should be listed.
    

    Image RemovedImage Added

17. To verify that the configuration is good, add a controlled area on the master principal node and verify that it appears on the slavereplica.

Detaching

...

Replica Server

Detaching a slave replica server from the master principal server is a two steps process.

1. Logon to the slave replica server with the system user and go to the System tab.

2. In the scope pane on the left, click on Utilities.

3. Click DB Replication.
   

   Image RemovedImage Added

4. Click the Detach button to detach the node from the masterprincipal.

5. Logon to the master principal server with the system user and go to the System tab.

6. In the scope pane on the left, click on Utilities.

7. Click DB Replication.

8. Find the client node and click the Delete button to detach the slave replica server.
   

   Image RemovedImage Added

Microsoft Active Directory (AD) Integration

...

 To remove a Certificate Policy OID:

Click theX button next to the OID.

...

Extended Key Usage Extensions

...

To remove an extended key usage extension constraint:

Click the X button next to the OID.

...

PKI Fault Options

...