4 Manage the AMC Deployment
The upgrade and maintenance of WKO and AMC can be achieved seamlessly using the Containerized AMC.
You can also migrate non-containerized AMC to Containerized AMC with minimal down time and continuity of services.
Migrate Non-containerized AMC to Containerized AMC
Migration of non-containerized AMC to Containerized AMC involves reusing of existing on-premise AMC database connection with Containerized AMC. In other words, the database connecting to on-premise (non-containerized) AMC is disconnected and connected to Containerized AMC. However, the WebLogic domain configuration of on-premise AMC is not migrated to Containerized AMC.
Note:
When upgrading the Advanced Management Console to version 2.17 or later, and if the Agent Auto Update option is enabled, you must manually replace the signing certificate in the agent machine. For detailed steps, see Automatic Update of Advanced Management Console Agent.-
Reuse On-premise AMC Server Address: The AMC server address is the host name and port number you set during AMC initialization. This address is used by all agents connected to the on-premise AMC. You can retain the same AMC server address for the migrated Containerized AMC. However, to reuse the AMC server address, the server address has to be front ended by an external load balancer.
OR
-
Change AMC Server Address: Plan the migration by changing the AMC server address.
Reuse On-premise AMC Server Address
Before you begin the migration, ensure that the on-premise AMC is front ended through an external load balancer application.
- Stop or un-deploy the running AMC application in your on-premise WebLogic cluster or server. You can also stop the WebLogic server or cluster if its used only for AMC deployment.
- Deploy Containerized AMC using the database connection properties that were used by the on-premise AMC.
- Identify the service end points (that is, server host name or IP address, and port number) of your Containerized AMC deployment. See Access the Containerized AMC.
- Replace the external load balancer backend with Containerized AMC service end points and restart the load balancer application.
- If you want to upgrade to higher version of AMC, see Upgrade Containerized AMC deployment.
-------------------------------------------------
HA Proxy front ending on-premise AMC
-------------------------------------------------
frontend AMCServer_001
bind *:8189 ssl crt /etc/haproxy/cert/server.pem
reqadd X-Forwarded-Proto:\ https
default_backend AMCServer_001_Back
backend AMCServer_001_Back
cookie JSESSIONID prefix nocache
server AMCServer_001_MS1 <onprem-managed-server1:port> cookie amc-cluster ssl verify none
server AMCServer_001_MS2 <onprem-managed-server2:port> cookie amc-cluster ssl verify none
-------------------------------------------------------
HA Proxy front ending Containerized AMC
-------------------------------------------------------
frontend AMCServer_001
bind *:8189 ssl crt /etc/haproxy/cert/server.pem
reqadd X-Forwarded-Proto:\ https
default_backend AMCServer_001_Back
backend AMCServer_001_Back
cookie JSESSIONID prefix nocache
server AMCServer_001_MS1 <cont-amc-server-host:port> cookie amc-cluster ssl verify none
Upgrade the Deployments
Run the upgrade
command to fetch the latest version of WKO,
AMC, and Helm chart values.
Upgrade WKO Deployment
helm upgrade <release-name> weblogic-operator/weblogic-operator \
--set "javaLoggingLevel=FINE" -n <operator-namespace> \
--reuse-values
$ helm upgrade wko weblogic-operator/weblogic-operator \
--set "javaLoggingLevel=FINE" -n wko-ns \
--reuse-values
For detailed steps to upgrade WKO deployment, see Upgrade the operator.
Upgrade Containerized AMC deployment
- A newer version of AMC container image is available
- If you need to increase or decrease the number of pods running (Scale-in or Scale-out)
- Changes in WebLogic domain configuration
- Switch to a different database, mail server, or LDAP server
custom-values.yaml
file.
helm upgrade <release_name> <path to amc helm package> –-values custom-values.yaml --wait \
-n <amc-namespace> --reuse-values
custom-values.yaml
are the custom values that overwrite the standard values in the local or remote repository.release_name
is the name of the Containerized AMC deployment.path to amc helm package
is the local helm package containing the standard AMC values.amc-namespace
is the AMC version that is being upgraded.wait
pauses the output until all pods and services are in the ready state.reuse-values
uses the last release values and merge overrides, if any, while upgrading.
$ helm upgrade amc ./java-amc-1.0.0.tgz --values custom-values.yaml --wait \
-n amc-ns --reuse-values
Uninstall Deployments
Uninstall will remove all resources that you have created during deployment. Ensure to uninstall the Containerized AMC before you uninstall WKO.
Use the following commands in the specified order to uninstall AMC and WKO deployments:
Uninstall Containerized AMC Deployment
kubectl delete configmap <configmap-name> -n <amc-namespace>
kubectl delete secret <secret-name> -n <amc-namespace>
kubectl delete namespace <amc-namespace>
helm uninstall <release_name> -n <amc-namespace>
Uninstall WKO Deployment
kubectl delete customresourcedefinition domains.weblogic.oracle -n <operator-namespace>
kubectl delete namespace <operator-namespace>
helm unistall <release-name> -n <operator-namespace>
#!/bin/bash
kubectl delete configmap amc-keystore -n amc-ns
kubectl delete secret amc-wls-credentials -n amc-ns
kubectl delete secret amc-ds-credentials -n amc-ns
kubectl delete secret amc-mail-credentials -n amc-ns
kubectl delete secret amc-ldap-credentials -n amc-ns
kubectl delete secret amc-jks-credentials -n amc-ns
helm uninstall amc -n amc-ns
helm uninstall wko -n wko-ns
kubectl delete customresourcedefinition domains.weblogic.oracle -n wko-ns
kubectl delete namespace amc-ns
kubectl delete namespace wko-ns