Running the Docker image

After the image download is completed, you can run the Docker image to start the Maximo Application Framework Configuration application.

Note: Before you run any commands, ensure that the Maximo Application Framework Configuration application container has write permission to the workspace directory.
Run the Docker image downloaded from the IBM Entitled Registry.
docker run -it --privileged -p 3001:3001 -p 3006:3006 -v /home/core/maximo_workspace_directory:/graphite/.workspace -it cp.icr.io/cp/manage/maf-tools:9.0.0
Run the Docker image downloaded from the IBM Open Registry.
docker run -it --privileged -p 3001:3001 -p 3006:3006 -v /home/core/maximo_workspace_directory:/graphite/.workspace -it icr.io/cpopen/maf-tools:9.0.0

Replace the maximo_workspace_directory variable with a working directory on your local system. Specify a port number with a value in the range 3000 - 3050. If you are using a Microsoft Windows system, you have to enable file sharing for your workspace directory.

If you run the Docker image by using a Windows system, you must include the -e parameter.

The following code is an example of the command with the parameter included. 
docker run -it --privileged -p 3001:3001 -p 3006:3006 -v /home/core/maximo_workspace_directory:/graphite/.workspace -it -e CHOKIDAR_USEPOLLING=true cp.icr.io/cp/manage/maf-tools:9.0.0

You can use the GRAPHITE_RELEASE parameter to reduce the size of the application package that you publish back to the Maximo® Manage server. Using this parameter can affect performance of the Maximo Application Framework Configuration application. To improve performance, you can increase the memory that is assigned to the Docker container.

The following code is an example of the command with the parameter included. 
docker run -it --privileged --env GRAPHITE_RELEASE=1 -p 3001:3001 -p 3006:3006 -v /home/core/maximo_workspace_directory:/graphite/.workspace -it cp.icr.io/cp/manage/maf-tools:9.0.0

Maximo Manage requires a valid security certificate to retrieve and publish applications from the Maximo Application Framework Configuration application in production environments. In development or demonstration environments, you can use the NODE_TLS_REJECT_UNAUTHORIZED parameter to bypass system checks for a valid security certificate.

The following code is an example of the command with the parameter included. 
docker run -it --privileged --env NODE_TLS_REJECT_UNAUTHORIZED=0 -p 3001:3001 -p 3006:3006 -v /home/core/maximo_workspace_directory:/graphite/.workspace -it cp.icr.io/cp/manage/maf-tools:9.0.0

Alternatively, for a secure option, you can use a self-signed certificate if you do not want to bypass validation.

The following code is an example of the command using a self-signed certificate. 
docker run -it --privileged -p 3001:3001 -p 3006:3006 -v /Users/maximo/IBM/MAF:/graphite/.workspace -v /home/core//Users/maximo/IBM/MAF/certs:/etc/ssl/certs --env NODE_EXTRA_CA_CERTS=/etc/ssl/certs/maximo.crt -it cp.icr.io/cp/manage/maf-tools:9.0.0

The -v /Users/maximo/IBM/MAF/certs:/etc/ssl/certs parameter defines the directory where the root certificate can be found.

The --env NODE_EXTRA_CA_CERTS=/etc/ssl/certs/maximo.crt parameter sets an environment variable in the Docker container that instructs the node to use the root certificate that was mounted in the directory.

Do not forget to stop the Maximo Application Framework Configuration application Docker container when you are done with your work to free up system resources.