Activating AIS for the End-User Engagement Model

This section describes the process of activating AIM for the AIS End-User engagement model. It explains both the end-user and partner responsibilities.

• AIS Partner Controller Responsibilities
• AIS End-User Responsibilities

AIS Partner Controller Responsibilities

To activate the end-user AIS product, the partner must follow these steps:

1. The partner sends AIM to the end customer.
2. The end customer installs AIM.
3. The end customer requests AIS services from the partner and provides the AIM install ID.
4. The partner requests an end-user license from Juniper Networks.
5. The partner, with AIM administrative privileges creates a new Proxy device group that is contained by a currently defined AIM organization in Settings > Organizations using the following settings:
   • Alias
   • Customer username (up to 128–character username for communication between the end-user and partner AIMs)
   • Customer password (up to 32–character password for communication between the end-user and partner AIMs)
   • Archive location for depositing customer JMBs
6. On the Organizations Credentials page, click Save Credentials.
7. The partner provides the end customer with the following:
   • Name—An alias used to create a proxy device group.
   • User name—A name used to create a proxy device group.
   • User password—A password used to create a proxy device group.
   • AIS license key license file—The aim_licensefile

AIS End-User Responsibilities

To activate AIS, the end user must follow these steps:

1. Request AIS service from your partner.

   The partner sends you the following information:

   • AIM software
   • Partner controller URL for AIM
   • Name
   • User name
   • User password
   • AIS license key license file (aim_license)
2. Install and start AIM.
3. The customer sends the AIM install ID to the partner.
4. Log in to AIM using the default username and password (admin/aimadmin) credentials.
5. The customer copies the aim_license license file to the root AIM install directory (for example/opt/aim).
6. In AIM, the customer navigates to Settings > License Management and clicks Load License File.
7. In AIM, the customer navigates to Setting > Organizations to add a new organization using the information from the partner.
8. Import the aim_license file.
9. In AIM, navigate to Settings > General Settings and adds the partner's URL.

   On the Organizations page, the customer clicks Save Credentials. The action validates the organization credentials at the partner controller. For more information about creating organizations, see Configuring AIM Organizations and Device Groups