You can configure OpenPages® to meet your business requirements.
About this task
- Scale down to a single replica
- Make the configuration changes
- Restart the application server
- Backup the configuration
- Scale back up to the number of replicas you need for the application server
- WebSphere Liberty configuration files
- Application configuration files
- JAR files for custom triggers
- Custom JSPs, along with their images and CSS files
You can make many other configuration changes. For more information, see the OpenPages documentation.
Log in to your Red Hat® OpenShift® cluster as a
oc login OpenShift_URL:port
- Change to the project where OpenPages is installed:
oc project <Project>
- If you use multiple replicas for the application server, scale down to a single
oc scale --replicas=1 sts/openpages-<instance_name>-sts
To find the name of the instance, run
oc get stsand look for a name that starts with
- In the application server pod, open a terminal window.
oc exec -it openpages-<instance_name>-sts-0 -- /bin/bash
- Make your changes.
The following table lists some of the configurations that you can make. For more information, see the OpenPages documentation.
- Restart the application server.
server stop server start
- Back up your OpenPages
cd /opt/ibm/OpenPages/aurora/bin ./OPBackup.sh /opt/ibm/OpenPages/openpages-backup-restore app-cp4d nosrvrst
A backup .zip file is created in /opt/ibm/OpenPages/openpages-backup-restore. The filename includes a timestamp.
The backup is restored automatically when you add more replicas or when the application server pod restarts (planned or unplanned restarts). The application server pod restart process uses the .zip file with the most recent timestamp.
- Scale up to the number of replicas you want to use for the application server.
oc scale --replicas=<number> sts/openpages-<instance_name>-sts