To build the ASAP cloud native Docker image, the asap-img-builder.zip file is required. For more information about downloading the ASAP cloud native Image Builder, see "Downloading the ASAP Cloud Native Artifacts".

The prerequisites for building ASAP cloud native image are:

• The Docker client and daemon on the build machine.

• Approximately 2 GB of swap space on the machine where the Docker daemon is running. By running the free -m command, you can verify the swap space.

  Note:

  If the required swap space is not available, contact your administrator.
• ASAP 7.4.0.0 or later Linux Installer. Download the .tar file from Oracle Software Delivery Cloud:

  https://edelivery.oracle.com

• Create the disk1 directory and copy the contents of the .tar file to this directory.

• Installers for WebLogic Server and JDK. Download these from Oracle Software Delivery Cloud:

  https://edelivery.oracle.com

• Oracle Database Client. Download this from Oracle Software Downloads:

  https://www.oracle.com/downloads/

• Java, installed with JAVA_HOME set in the environment.

• ASAP is installed in a silent installation mode using the asap.properties file. You should update the properties file with the database, WebLogic Server, ORACLE_HOME, port numbers, and all required details.

• Keep the TRAEFIK Ingress service node port details ready where it is being deployed.

• Create ASAP database users. For more information, see "Creating Oracle Database Tablespaces, Tablespace User, and Granting Permissions" in ASAP Installation Guide.

For details about the required and supported versions of the prerequisite software, see ASAP Software Compatibility Matrix.

The ASAP cloud native image builder tool builds the ASAP cloud native Docker image, which is then pushed to the Docker repository and deployed in the Kubernetes cluster. If the Docker repository is not available, you copy the image to all the worker nodes of the cluster.

The ASAP installer is packaged with the ASAP cloud native image builder and the cloud native toolkit.

To create the ASAP cloud native Docker image:

1. Copy the asap-img-builder.zip file to the machine where the Docker daemon is running.

2. Extract the contents of the zip file by running the following command:

   unzip asap-img-builder.zip

3. Copy the following installers to the $asap-img-builder/installers directory.

   • Linux Installer for ASAP 7.4.0.1 or later
   • Installers for WebLogic Server and JDK
   • Oracle Database Client

4. Copy the required cartridges to the $asap-img-builder/cartridges directory.

5. Set the environment variable for ASAP_IMG_BUILDER to the $asap-img-builder directory.

6. Update the $asap-img-builder/scripts/tnsnames.ora file with the database details. For example,

   orcl19c =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = database host)(PORT = 1521))
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = service name)
        )
      )

7. Update the HTTPS_PROXY and HTTP_PROXY variables in the build_env.sh script.

   Note:

   The variables in the section Docker details, Installer filenames, and Installation locations are populated by default with the appropriate information.

   base_image=oraclelinux:8
   HTTPS_PROXY=
   HTTP_PROXY=
   
   # Docker details
   ASAP_IMAGE_TAG="7.4.0.0.0"
   ASAP_VOLUME=dockerhost_volume
   ASAP_CONTAINER="asap-c"
   DOCKER_HOSTNAME="asaphost"
   
   # Installer filenames
   JDK_FILE=jdk-8u321-linux-x64.tar.gz
   DB_CLIENT_FILE=LINUX_193000_client.zip
   FMW_FILE=fmw_14.1.1.0.0_wls_lite_Disk1_1of1.zip
   
   # Installation locations
   TNS_ADMIN=/scripts/ 
   JAVA_HOME=/usr/lib/jvm/java/jdk1.8.0_321
   ORACLE_HOME=/home/oracle/oracle/product/19.3.0/dbhome_1
   PATH=$ORACLE_HOME:$JAVA_HOME/bin:$PATH
   CV_ASSUME_DISTID=OEL8
   WLS_HOME=/home/oracle/weblogic14110/wlserver 
   

   Note:

   Ensure that the file names of JDK_FILE, DB_CLIENT_FILE, and FMW_FILE variables match with the file names in the /asap-img-builder/installers/ folder.

8. Update the following parameters in the $asap-img-builder/asap.properties file with the required details for ASAP and the WebLogic Server domain. You can update the configuration parameters that must be updated after ASAP installation using asap.properties file. All the configuration parameters should be prefixed with asap.properties. You can create multiple ASAP instances by entering multiple unique environment IDs in the asap.envid variable separated by a comma. For example, asap.envid=CNE1, CNE2, CNE3 where CNE1, CNE2, and CNE3 are unique environment IDs.

   asap.tar.file=ASAP.R7_4_0.B196.linux.tar
   asap.envid=CNE1
   asap.installLocation=/scratch/oracle/asap
   asap.db.alias=
   asap.db.username=
   asap.db.password=
   asap.db.tablespace=
   asap.db.temp.ts=
   weblogic.domainName=asapDomain
   weblogic.domainLocation=/u01/oracle/user_projects/domain/
   weblogic.username=
   weblogic.password=
   weblogic.port=7601
   weblogic.channel.listenport=7602
   weblogic.channel.publicport=30301
   asap.server.adm.password=
   asap.server.ctrl.password=
   asap.server.nep.password=
   asap.server.sarm.password=
   asap.server.srp.password=
   asap.weblogic.adminPassword=
   asap.weblogic.cmwsPassword=
   asap.weblogic.monitorPassword=
   asap.weblogic.operatorPassword=
   asap.weblogic.wsPassword=
   ## ASAP.cfg properties
   asap.properties.MSGSND_RETRIES=5

   Note:

   • If Traefik is configured, weblogic.channel.publicport parameter must have the traefik ingress controller nodeport value (for http 30305 and for https 30443).
   • If DNS is configured, weblogic.channel.publicport must have the value same as weblogic.channel.listenport.
   • asap.weblogic.adminPassword, asap.weblogic.cmwsPassword, asap.weblogic.monitorPassword, asap.weblogic.operatorPassword, and asap.weblogic.wsPassword parameters must have passwords at least 8 characters long, and must contain at least 1 number or special character.
   • The asap.properties file is available only in the host machine and not as part of the Docker image.
9. Run the build-asap-images.sh script using the following command:

   ./build-asap-images.sh -i asap

   The script creates the staging Docker image by installing WebLogic Server, Java, and the database client.

   The script also creates the staging ASAP Docker image for the environment IDs specified in the asap.properties file.

ASAP cartridges are discrete software components developed for ASAP. An ASAP cartridge provides specific domain behavior on top of the core ASAP software. This domain behavior includes a part of, or all services on a network element (NE), element management system (EMS), or network management system (NMS). For more information about cartridges, see ASAP Cartridge Development Guide and for installing cartridges, see ASAP Installation Guide.

To provision orders to network elements, you install cartridges in the ASAP container that are available in the $ASAP_VOLUME/cartridges/ directory. After installing the cartridges, you must exit the ASAP container by using the exit command.

To install cartridges:

ASAP security is designed to provide confidentiality, data integrity, and ensure on-demand access to services for authorized users. For information about ASAP security, see "Setting Up and Managing ASAP Security" in ASAP System Administrator's Guide.