Performing the management server installation on zCX

Task 1: To unzip the installation file

Create the file system hierarchy by using the following commands: 

Task 2: To copy the containers to the zCX instance

Copy the Docker containers from the Alpine Docker container by using the following commands: 

Task 3: To load the docker container to the zCX instance

Create the file system hierarchy by using the following commands: 

Task 4: To start the BMC AMI Cloud database container

1. Create a Docker network bridge by using the following command: 

   docker network create -d bridge model9network

2. Start the BMC AMI Cloud PostgreSQL database container by using the following command: 

   docker run -p 127.0.0.1:5432:5432 \
    -v model9db:/var/lib/postgresql/data:z \
   -v model9db_initdb:/docker-entrypoint-initdb.d:z \
   --name model9db --restart unless-stopped \
   --network model9network \
   -e POSTGRES_PASSWORD=model9 -e POSTGRES_DB=model9 -d s390x/postgres:14.5

3. Verify the health status of the container and that it is ready to accept connections by issuing the docker logs model9db command and verifying its output as shown in the example: 

   2023-10-06 06:15:27.770 UTC [48] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
   2023-10-06 06:15:27.777 UTC [49] LOG:  database system was shut down at 2023-10-06 06:15:27 UTC
   2023-10-06 06:15:27.782 UTC [48] LOG:  database system is ready to accept connections

Task 5: To update the BMC AMI Cloud management server parameters file

1. Login to the alpine container by using the following commands:

   docker exec -it dummy sh
   cd /root
   vi conf/model9-local.yml
   #Logout of Alpine container (CTRL+D)

2. Update the default parameters in the model9-local.yml file. 

   Click here to expand...

   The model9-local.yml file, which resides in $MODEL9_HOME/conf/, contains some default parameters, which you can update.

   model9.licenseKey: <license-key>
   
   model9.home: '${MODEL9_HOME}'
   
   model9.security.dataInFlight.skipAgentHostNameVerification: true
   
   model9.security.dataInFlight.truststore.fileName: '${MODEL9_HOME}/keys/model9-backup-truststore.jks'
   model9.security.dataInFlight.truststore.type: "JKS"
   model9.security.dataInFlight.truststore.password: "model9"
   model9.security.dataInFlight.keystore.fileName: '${MODEL9_HOME}/keys/model9-backup-server.p12'
   model9.security.dataInFlight.keystore.type: "PKCS12"
   model9.security.dataInFlight.keystore.password: "model9"
   
   model9.session.timeout.minutes: 30
   
   model9.master_agent.name: "<ip_address>"
   model9.master_agent.port: <port>
   
   # model9.objstore.resources.container.name: model9-data
   # model9.objstore.endpoint.api.id: s3  
   model9.objstore.endpoint.url: https://<object_storage_dns_or_ip>:<object_storage_port>
   model9.objstore.endpoint.userid: <object store access key>
   model9.objstore.endpoint.password: <object store secret>
   model9.objstore.endpoint.password_encrypted: <false|true>
   
   model9.runlogs.expirationScanIntervalMinutes: <min>
   model9.runlogs.maxRetentionPeriodDays: <days>
   
   dataSource.user: postgres
   dataSource.password: model9

   Parameter		Description	Value
   model9.licenseKey		(Required) Valid BMC AMI Cloud license key as obtained in Obtaining the license key When using multiple keys for multiple CPCs, specify one of the keys in the server’s yml file. The agent performs server-initiated actions by using its own defined license. The license key specified for the server is used to display a message about the upcoming license expiration.	License key
   model9.session.timeout.minutes		(Optional) Number of minutes following which an inactive UI session should end	Default: 30
   model9.objstore
   model9.objstore.resources.container.name		(Optional) Container or bucket	Default: model9-data
   model9.objstore.endpoint.api.id		(Optional) Object storage API name	Default: s3 Amazon AWS1: aws-s3 Microsoft Azure: azureblob
   model9.objstore.endpoint.url		(Required) URL address of local or remote object storage. Both HTTP and HTTPS are supported. Using HTTPS for the object storage URL parameter enables data-in-flight encryption.	Default: none Amazon AWS1: https://s3.amazonaws.com​ Google Cloud Storage: https://storage.googleapis.com
   model9.objstore.endpoint.userid		(Required) Access key to object storage	Default: none
   model9.objstore.endpoint.password		(Required) Secret key to object storage	Default: none
   model9.objstore.endpoint.api.s3.calculatemd5		(Optional) Enables MD5 checksum calculation to be included in put Object requests. This parameter is required for Object Lock enabled buckets.	Accepted values: true|false Default: false
   model9.objstore.endpoint.api.s3.v4signatures		(Optional) When using object storage that uses V4 signatures, set this parameter to true in addition to api.id: s3	Accepted values: true|false Default: false Cohesity: true HCP-CS: true
   model9.objstore.endpoint.no.verify.ssl		(Optional) When using the HTTPS protocol, determines whether to avoid SSL certificate verifications	Accepted values: true|false Default: true
   model9.runlogs Warning The following parameters automatically trigger the deletion of run logs from the server. This deletion irrecoverable. The logs are not deleted if at least one of the parameters is set to -1.
   model9.runlogs.expirationScanIntervalsMinutes		(Optional) Determines the frequency of deleting old run logs	Default: -1 (never)
   model9.runlogs.maxRetentionPeriodDays		(Optional) Determines after how many days a run log will expire and can be deleted by the automatic deletion process.	Default: -1 (never)
   dataSource (Should these be here?)
   dataSource.user		Database user name
   dataSource.password		Database password
   dataSource.url		Database URL

   ^{1 When using Amazon S3, see AWS S3 security considerations.} 

Task 6: To start the BMC AMI Cloud server

When the object storage is available and the PostgreSQL container is running, start the server by using the following commands, replacing <zCX-VIPA> with the zCX instance VIPA: