2 Setup the Environment
Before you start the deployment, install the prerequisite software and setup the environment.
You need to build the AMC container image using AMC ear file. See Create the AMC Container Image.
Prerequisites
The following are the prerequisites to deploy the Containerized AMC:
- Familiarity with Containers, Kubernetes, and Helm
- Ability to setup the Kubernetes cluster
- Availability of Oracle DB or MySQL database
- Access to Oracle Container Registry (OCR)
- Java SE Subscription license to download AMC ear from Oracle Technology Resources (OTN) or My Oracle Support (MOS)
- Privilege to perform common administrative tasks on Database
System Requirements
System requirements to deploy WebLogic Kubernetes Operator (WKO) and Containerized AMC.
- Prerequisites for WKO release: See WKO Prerequisites
- Setup either of the following database, which is ready to accept
external connections from AMC application:
- Oracle DB: 19c, 12c, or 11g
- MySQL: 8, 5.7, or 5.6
- WebLogic Cluster, as a publicly accessible Kubernetes Service, must be
accessible from all agent machines
Note:
Change in the host name provided at the time of AMC initialization might stop AMC Agent to communicate with the server and block agent bundle downloads. - WKO deployment in Kubernetes Cluster
- Kubernetes worker nodes must have internet access as AMC connects to external network to fetch Java release information
- All agents must be able to access the server
Environment Setup
You need to setup the environment for seamless deployment of Containerized AMC.
Ensure you have the following environment setup:
- Setup the Kubernetes environment. See:
- WKO is a prerequisite to manage the AMC domain resource. You can either make use of an already running WKO deployment in a cluster, or setup a new WKO and configure it for AMC deployment.
- Setup the database, either on-premise or DBaaS. Oracle database or MySQL is supported.
- Install and configure the database. See Database Installation and Configuration for Advanced Management Console. Also, see the Configurable Parameters, Table 3-1 to know more about the configuration parameters that are required to setup the database for Containerized AMC.
- Ensure that Oracle or MySQL database is ready to accept the connection.
Create the AMC Container Image
You can use WebLogic Image Tooling (WIT) to create the AMC Container Image.
Note:
- Ensure that the operating system user has adequate permissions
to perform install and deploy commands. Use
sudo
orsudo -E
commands as required. - The folder names mentioned in this topic are for illustrative purposes. You can name the folders as per your requirement.
[INFO ] Build successful. Build time=36s. Image tag=amc2u20:latest
Also, run the container (docker) image commands to verify if the image is created successfully.
Distribute the Image to all Kubernetes Nodes
The AMC container image is built on one machine. During deployment, the image must be available on all Kubernetes nodes.
To distribute the image to all Kubernetes nodes,
push
the image to a private container registry and
pull
the image from this registry during deployment. If the
registry is not available, then you can distribute the image using the Save and Load
method.