Manage a Semarchy xDM instance in GCP

Upgrade Semarchy xDM

Review the pre-upgrade instructions before upgrading your instance(s) of Semarchy xDM.

Stop all applications and user connections to Semarchy xDM during the upgrade:

No application should access the Semarchy xDM services and APIs.
No user should access the Semarchy user interfaces for design-time or data management operations.
No user or application should access the repository or data locations' database schemas.

Contact your database administrator and middleware administrator to ensure Semarchy xDM remains unavailable throughout the upgrade process.

To upgrade Semarchy xDM:

Navigate to the folder containing Kubernetes descriptor files for the active and passive deployments.
Update both the descriptor files to use the new Semarchy xDM image to upgrade to. For more information, see Docker Hub page.
Run the following command to delete the active application server deployment:
```
$ kubectl delete deployment.apps/semarchy-appserver-active
```
Run the following command to delete the passive application server deployment:
```
$ kubectl delete deployment.apps/semarchy-appserver-passive
```
Repeat the deployment steps 8 and 9 to apply the new deployments for the active and passive application servers.
Upgrade the repository and upgrade the data locations.

GCP resources

GCP GKE

For more information on upgrading the GKE cluster control plane, see Best practices for upgrading clusters.

GCP Cloud SQL

For more information on upgrading the Amazon Aurora cluster, see Upgrade the database major version.

Backup

Semarchy xDM

For more information on backing up your installation of Semarchy xDM, see Upgrade procedure steps.

GCP GKE

For more information on managing backups for GCP GKE, see Backup for GKE.

GCP Cloud SQL

for more information on managing backups with Cloud SQL, see About Cloud SQL backups.

Maintenance and troubleshooting

Semarchy xDM

The following is a non-exhaustive list of commands useful for monitoring and troubleshooting Semarchy xDM:

Get the pods running on the active application server.
```
$ kubectl get pods -l app=semarchy-appserver-active
```
Get the pods running on the passive application servers.
```
$ kubectl get pods -l app=semarchy-appserver-passive
```
Get details for a specific pod.
```
$ kubectl describe pod _<pod_name>_
```

Get logs for the active application server.

$ kubectl logs -l app=semarchy-appserver-active

Get logs for the passive application servers.

$ kubectl logs -l app=semarchy-appserver-passive

Get details for the active application server deployment.

$ kubectl get deployments -l app=semarchy-appserver-active

Get details for the passive application server deployment.

$ kubectl get deployments -l app=semarchy-appserver-passive

Additionally, the platform offers REST API readiness probes to monitor the application status.

Kubernetes deployments and pods

for more information on maintaining and managing Kubernetes deployment and pods, see Cluster administration.

GCP resources

GCP GKE

for more information on troubleshooting Amazon EKS, see GKE troubleshooting.

GCP Cloud SQL

For more information on troubleshooting Amazon Aurora instances, GCP storage troubleshooting.

License and support

For more information, see Semarchy xDM system requirements.

Additional services on GCP

Secrets

Semarchy xDM supports Key Management Services and Secrets Manager to store the platform’s sensitive configuration items such as credentials, API keys, or passwords and to implement rotating system credentials.

GCP Cloud Key Management

For more information on configuring GCP Cloud Key Management, see Configure a key management service.

GCP Secrets Manager

For more information on configuring GCP Secrets Manager, see Configure external secrets managers.

Cloud Monitoring

Google Cloud Monitoring can be used to monitor the different resources of the architecture.

GCP GKS

For more information on monitoring the Google GKE, see Observing your GKE clusters.

GCP Cloud SQL

For more information on monitoring Cloud SQL, see Monitor Cloud SQL instances.