Step 5 - Install the PingIntelligence for APIs software
Run the following command to setup the deployment. Accept the EULA displayed on the screen for ABS for installation to start.
[pi-api-deployment]# ./bin/start.sh install Please see /opt/pingidentity/pi-api-deployment/logs/ansible.log for more details.
To verify a successful setup, view the ansible.log file. Here is a log file snippet for a successful setup:
[pi-api-deployment]# tail -f logs/ansible.log ==================================================================================== Current Time: Sun Jun 07 06:06:22 EST 2020 Starting setup scripts ==================================================================================== Sun Jun 07 06:06:22 EST 2020: Setting up local environment Sun Jun 07 06:06:22 EST 2020: Installing packages Sun Jun 07 06:06:23 EST 2020: Installing pip and ansible . . PLAY RECAP *** 127.0.0.1 : ok=9 changed=0 unreachable=0 failed=0 192.168.11.143 : ok=25 changed=13 unreachable=0 failed=0 192.168.11.144 : ok=57 changed=39 unreachable=0 failed=0 192.168.11.145 : ok=56 changed=35 unreachable=0 failed=0 Sun Jun 07 06:23:37 EST 2020: Setup successful ====================================================================================
Updated PingIntelligence packages
The automated deployment framework creates the updated package for each PingIntelligence component and stores them in the /opt/pingidentity/pi-api-deployment/software/updated_packages directory. The keys, passwords, and port number in these packages are the ones that you configured using the yml files in the/opt/pingidentity/pi-api-deployment/config directory. You can use these packages to install PingIntelligence components on other instances.
|
The CLI admin password in ASE and ABS is saved in the updated packages. If you want to change the CLI admin password, use the |