Planning
There are several design considerations when looking to install ASI in your enterprise.
- Architecture and Network design.
- Server specification, storage and repositories.
- Security, Authentication and Access management.
- Software package required
Software
We would recommend that your server(s) are subscribed to standard Linux repositories so that any dependant packages can be automatically downloaded prior to installation. If there are security reasons that don’t allow this on your environment, please contact support for a list of required dependant packages and follow the instructions to create a local Yum repository.
Interlink packaged RPMs can be found on the Interlink Portal Downloads site.
You will need the following packages:
- Java OpenJDK 17
- iss-core 1.4.1+
- iss-asi-events 1.0.0+
Clustering
If you are wanting to manage a clustered BES environment then these steps should be followed on both Primary and Secondary servers.
Transport Layer Security (TLS)
To enable TLS communication between Event Management and ASI, ensure the required certificates are installed in the default locations on your servers.
Networking and Load Balancing
Refer to the Networking page for details of the ports that need to be opened, along with information on how a load balancer should be configured (if applicable).
Server Specifications
This software can only be installed on a server already running BES 3.9.4+
Sudo Rules
The following sudo rules need to be added to enable the ppadmin user to manage the asi-events service. You may also need additional sudo rules to allow your userid to be able so su to the ppadmin user.
ppadmin ALL=(root) NOPASSWD: /bin/systemctl stop iss-asi-events.service, /bin/systemctl start iss-asi-events.service, /bin/systemctl restart iss-asi-events.service, /bin/systemctl status iss-asi-events.service