Upgrade from version 4.2.1.9 to version 4.2.1.10 in Docker

This section describes how customers and partners using OpenIAM on Docker can upgrade 4.2.1.9 to enterprise version 4.2.1.10

Update repository settings

To start the upgrade process, connect to your Linux host where you installed OpenIAM and go to the directory where you installed the OpenIAM Docker compose. By default, this should be:/usr/local/openiam/openiam-docker-compose. Go to that directory and check the status using the command shown below.

cd /usr/local/openiam/openiam-docker-compose
git status

During installation of the previous version, at a minimum, the env.sh file was updated. Output from the command above, which is shown below, will indicate the files which were changed.

On branch [branch name]
Your branch is up to date with 'origin/[release branch name]'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
    modified:   env.sh
    ...[other files if they where modified]

To preserve the customizations create a new branch and add the changes to that branch as shown below. You can name your branches based on your standards or preference. (If this was already done, do not create new branch, but just add and commit changes)

sudo git checkout -b RELEASE-4.2.1.9-changes
sudo git add .
sudo git commit -a -m "4.2.1.9-changes"         // Now you have saved branch with customizations
sudo git checkout -b update_to_RELEASE-4.2.1.10  // New branch to do a merge so you can keep original customized branch safe
sudo git pull
sudo git pull origin RELEASE-4.2.1.10
sudo git merge origin/RELEASE-4.2.1.10

In case conflict arises, follow the article below and jump onto the section related to “How to identify merge conflicts” and “How to resolve merge conflicts using the command line”. https://www.atlassian.com/git/tutorials/using-branches/merge-conflicts

Upgrade docker-compose project

In short, the steps described in the documents mentioned are:

Identify the file with conflict, which will be shown after executing git merge command;
Open the files in editor used and search for <<<<<HEAD ===== >>>>>new_branch
Keep the section required and delete the other section
Execute git commit -m <comment_here>.

Then execute remaining commands.

sudo git merge origin/RELEASE-4.2.1.10

After these steps, verify that env.sh has updated branch.

export OPENIAM_VERSION_NUMBER="4.2.1.10"
export BUILD_ENVIRONMENT="prod"

At this point, you have updated your docker-compose project to Release-4.2.1.10.

Restart application using updated docker-compose project

Now you all set, please run the following commands to update your local images and then start the application.

sudo ./shutdown.sh
sudo ./setup.sh
sudo ./startup.sh

After upgrading execute

watch -n 5 ‘docker ps’

to check the status of all the containers. Wait for the containers to fully startup and then the application will be ready for use.

Validate result of the upgrade process

Once all the services are up and running, login to OpenIAM and navigate to Administration > About OpenIAM.

The build version must be updated to 4.2.1.10.

Note: Please note that you must update connector if you use newer versions of the product. It is recommended to use the latest connector version. All .NET/PS connectors versions as at 5.24.0.0 version are backward compatible.

Upgrade from version 4.2.1.5-4.2.1.8 to version 4.2.1.10 in Docker

Docker Yaml files