1. Create a working folder and download the OracleComms_OSM_O2A_CartridgesInstaller_2.1.2.1.0.xxx.zip Order-to-Activate installer into the working folder.
2. Unzip the Order-to-Activate installer ZIP file within the working folder.
3. From Design Studio, import the working_folder/OSM.PIP/OracleComms_OSM_O2A_Install.zip archive file as an existing project.
4. Import COM, SOM, or COM and SOM together with the solution cartridge into the workspace and upgrade the model. See "Performing an Interactive Installation of the Order-to-Activate Components" in Order and Service Management Cartridge Guide for Oracle Application Integration Architecture.
5. Add the SolutionConfig.xml file from the solution cartridge that you imported to Ant view and configure it to run as the same JRE as the Eclipse workspace.
6. Run the config_All_CloudNative Ant target.
7. When prompted, enter d for development or p for production.
8. Choose the topology and complex topology options as desired. The config_All_CloudNative target also runs the config_Metadata_And_ModelVariable target. Hence, there is no need to run it separately.

   After config_All_CloudNative is run successfully, the cloud native artifacts are generated. If you chose the CSO option, the artifacts are generated under OracleComms_OSM_O2A_XXX_CSO_Solution/cloud-native.

9. Save the generated artifacts.
10. Build your solution. If you chose the CSO option, build OracleComms_OSM_O2A_XXX_CSO_Solution.

• o2a_project.yaml: The yaml fragment containing all JMS resources and SAF queues. Copy this fragment into your project specification file.
• o2a_project-instance.yaml: The yaml fragment containing all SAF connection configuration. Copy this fragment into your instance specification file.
• o2a_users.yaml: The yaml fragment of all cartridge users defined for the solution. Copy this fragment into your project specification file.
• o2a_users_embedded_ldap.txt: User information text file to be used by the manage-cartridge-credentials.sh OSM cloud native toolkit script to create Kubernetes secrets for all cartridges. These secrets are added to WebLogic embedded LDAP when the instance is created.
• o2a-wdt-app-archive.zip: The application archive that contains the error handler for the solution. If the Order-to-Activate config option development or cso is selected, then emulators for AIA and the CSO solution are included as well.
• Dockerfile: The Docker build file to extend a base OSM image to include the o2a-wdt-app-archive.zip file.
• create-o2a-base-image.sh: The Linux shell script that uses the application archive and dockerfile to extend an OSM image for Order-to-Activate use.

1. Change the working directory to the directory where the cloud native artifacts are generated. If you chose CSO, change the working directory to OracleComms_OSM_O2A_XXX_CSO_Solution/cloud-native/application.

2. Build the new Docker image containing the archive by running the create-o2a-base-image.sh script.

   The following sample shows the usage:

   Usage:
   create-o2a-base-image.sh <parameters>
    -t o2a-image-tag-name : mandatory, the image tag name to be created. 
    -i osm-base-image-name : mandatory, the base osm image to be extended. 
    -a o2a-app-archive : mandatory, the application archive that contains O2A app artifacts. 
   
   For example.... 
   $ ./create-o2a-base-image.sh \
   -t o2a-domain:7.4.1 -i osm-base:7.4.1 -a o2a-wdt-app-archive.zip

• Secrets used by SAF connection to AIA, UIM, and OSM TOM
• Secrets used by automation in OSM and Order-to-Activate to communicate to OSM and other systems

kubectl create secret generic project_name-instance_name-saf-credentials-aia -n project_name --from-literal=username='aia_weblogic_user_name' --from-literal=password='aia_weblogic_user_password'

kubectl create secret generic project_name-instance_name-saf-credentials-uim -n project_name --from-literal=username='uim_weblogic_user_name' --from-literal=password='uim_weblogic_user_password'

kubectl create secret generic project_name-instance_name-saf-credentials-tom -n project_name --from-literal=username='tom_weblogic_user_name' --from-literal=password='tom_weblogic_user_password'

1. Populate your project.yaml file with the list of cartridgeUsers from the o2a_users.yaml file. If you chose CSO, the list of cartridge users is located in the OracleComms_OSM_O2A_XXX_CSO_Solution/cloud-native/project/o2a_users.yaml file.

       # cartridge users for o2a
       cartridgeUsers:
        - osm
        - osmoe
        - osmde
        - osmfallout
        - osmoelf
        - osmlfaop
        - osmlf

2. Copy the o2a_users_embedded_ldap.txt Order-to-Activate user file to $OSM_CNTK/samples/credentials. If you chose CSO, the user file is located in the OracleComms_OSM_O2A_XXX_CSO_Solution/cloud-native/project directory.
3. Run the $OSM_CNTK/samples/credentials/manage-cartridge-credentials.sh script to create the Kubernetes secret:

   $ chmod 777 $OSM_CNTK/samples/credentials/manage-cartridge-credentials.sh
   $ $OSM_CNTK/samples/credentials/manage-cartridge-credentials.sh -p project_name -i instance_name -c create -f $OSM_CNTK/samples/credentials/o2a_users_embedded_ldap.txt