Cloud Native Deployment Guide for Oracle Application Integration Architecture Cartridges
Release 2.1.2
F43826-01
June 2021
Order-to-Activate 2.1.2.1.0 cartridges support deploying OSM instances in a cloud native environment. The integration pack generates all the required artifacts to be used by the OSM cloud native toolkit.
You perform the following tasks to use the Order-to-Activate cartridges for OSM cloud native deployments:
The Order-to-Activate integration pack generates all the required artifacts to be used by the OSM cloud native toolkit. You use the config_ALL_CloudNative configuration option in the SolutionConfig.xml Order-to-Activate configuration script to generate the artifacts.
Before generating the OSM cloud native artifacts, ensure that you have installed Design Studio and OSM plugins and that a workspace has already been created. For details about installing the Order-to-Activate components, see "Performing an Interactive Installation of the Order-to-Activate Components" in Order and Service Management Cartridge Guide for Oracle Application Integration Architecture.
d for development or p for production.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.
If you chose the CSO option, the par file is generated at: OracleComms_OSM_O2A_XXX_CSO_Solution/cartridgeBin/OracleComms_OSM_O2A_XXX_CSO_Solution.par.
You use the OSM cloud native toolkit to deploy the par file to the OSM database directly.
development or cso is selected, then emulators for AIA and the CSO solution are included as well.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.
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
In addition to the regular setup required for an instance defined by the OSM cloud native toolkit, you must perform the following additional steps:
$ vi spec_path/project_name.yaml # update image and add credential store as shown. image: O2A_image_name_and_tag #External Credentials Store, O2A cartridge user secret externalCredStore: # Uncomment and specify Kubernetes secret suffix for external/peer applications. The prefix project_name-instance_name will be derived # The suffix must be in the "osmcn-cred-mapName" format secrets: mapNames: - osm - uim
If you chose product mode when running config_ALL_CloudNative, modify your project_name-instance_name.yaml to add customSecrets and safConnectionConfig sections to set up the secrets and SAF end point URL for the SAF connection.
$ vi spec_path/project_name-instance_name.yaml # add the Order-to-Activate credentials store as shown #Customer Credentials Store, a secret used in SAF remote connect to AIA, UIM and TOM # Replace all ${DOMAIN_UID} with project_name-instance_name instance: customSecrets: secretNames: - "${DOMAIN_UID}-saf-credentials-aia" - "${DOMAIN_UID}-saf-credentials-uim" - "${DOMAIN_UID}-saf-credentials-tom"
$ vi spec_path/project_name-instance_name.yaml # provide the AIA t3Url under O2A_SAFImportedDestinations, # UIM t3Url under O2A_UIM_SAFImportedDestinations and # TOM t3Url under O2A_TOM_SAFImportedDestinations. # Replace all ${DOMAIN_UID} with project_name-instance_name # SAF connection configuration for O2A safConnectionConfig: - name: O2A_SAFImportedDestinations t3Url: t3://t3_host:t3_port secretName: ${DOMAIN_UID}-saf-credentials-aia - name: O2A_UIM_SAFImportedDestinations t3Url: t3://t3_host:t3_port secretName: ${DOMAIN_UID}-saf-credentials-uim - name: O2A_TOM_SAFImportedDestinations t3Url: t3://t3_host:t3_port secretName: ${DOMAIN_UID}-saf-credentials-tom
Note:
Perform this task for production environments only. When configuring theconfig_ALL_CloudNative option, if you chose development, the solution uses emulators and you do not need to create secrets for SAF connection.The credentials used to obtain connection to other systems via SAF are stored as Kubernetes secrets.
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'
The Order-to-Activate user credentials are persisted to a cartridge credential secret in Kubernetes. This uses the osm map name and is available via the OSM automation framework in the cartridge automation plugin code. In addition, the automation users must have accounts in embedded LDAP.
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$ 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
Oracle Communications Order and Service Management Cloud Native Deployment Guide for Oracle Application Integration Architecture Cartridges, Release 2.1.2
F43826-01
Copyright © 2021, Oracle and/or its affiliates.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. The terms governing the U.S. Government’s use of Oracle cloud services are defined by the applicable contract for such services. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.