Supported Artifacts

• Property Exclusions
• Integration Cloud Archive
• Process Cloud Archive
• SCA
• OSB
• MDS
• ADF
• Java EAR
• Java WAR
• SQL
• B2B
• BAM
• MFT
• Application Configuration (Properties/XML)
• OSB Custom XPath
• OWSM Policy
• ODI Application (XML)
• JAR Library
• Java Shared Library

Property Exclusions

A list of artifact properties excluded from being published to Myst Studio. Avoid using the following properties:

• core.*
• internal*

Integration Cloud Archive

Oracle Integration Cloud Archives can be deployed using Myst. These artifact types can be deployed to either Oracle Integration Cloud or the Legacy Integration Cloud Service. For each version of an Oracle Integration Cloud Archive which you wish to deploy, you must first register it with Myst. These steps can be performed manually, however, it is recommended to include these steps in a CI server job, so that they can be triggered automatically as required.

Step 1: Export your Integration Cloud Archive

We can export either from the Oracle Integration Cloud console, Integration Cloud Service console or via the REST API for either service.

To export via the Oracle Integration Cloud console:

1. Navigate to Integrations within the Oracle Integration Cloud console
2. Download the Integration. This will download a file with the .iar file extension.

To export via the Oracle Integration Cloud REST API:

1. Ensure you have curl installed and are running on a Linux based machine
2. Set the following environmental variables to match your environment:

   OIC_USERNAME="your-email@your-company.com"
   OIC_PASSWORD="your-password"
   OIC_HOST="your-instance.uscom-central-1.oraclecloud.com"
   OIC_ICS_PROJECT_ID="ECHO|01.00.0000"
   OIC_ICS_EXPORT_FILE_NAME="ECHO_01.00.0000.iar"
   

3. The OIC_ICS_PROJECT_ID can be obtained by combining the integration identifier with the version. These details can be found under the Primary Info menu item for the integration.
4. Execute the following to export your project.

   curl -u ${OIC_USERNAME}:${OIC_PASSWORD} \
   https://${OIC_HOST}/ic/api/integration/v1/integrations/${OIC_ICS_PROJECT_ID}/archive > ${OIC_ICS_EXPORT_FILE_NAME}
   

   If using the Legacy Integration Cloud Service, then use the following instead

   curl -u ${OIC_USERNAME}:${OIC_PASSWORD} \
   https://${OIC_HOST}/icsapi/v2/integrations/${OIC_ICS_PROJECT_ID}/archive > ${OIC_ICS_EXPORT_FILE_NAME}
   

Step 2: Create the Maven pom.xml

1. Create a pom.xml. Be sure to set the Maven details to match your environment. An example pom.xml is shown below.

   <?xml version="1.0" encoding="UTF-8"?>
   <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
   <modelVersion>4.0.0</modelVersion>
   <groupId>com.rubiconred</groupId>
   <artifactId>RetrieveAllAirlines</artifactId>
   <packaging>jar</packaging>
   <version>1.0-SNAPSHOT</version>
   <name>Retrieve All Airlines</name>
   <properties>
    <myst.component.type>opaas-ics</myst.component.type>
    <ics.deployment-name>RetrieveAllAirlines</ics.deployment-name>
    <ics.configuration-plan>(EMBEDDED)/ics.json</ics.configuration-plan>
   </properties>
   <build>
    <resources>
      <resource>
        <directory>${project.basedir}</directory>
        <excludes>
          <exclude>pom.xml</exclude>
        </excludes>
      </resource>
    </resources>
   </build>
   </project>
   

Myst supports the following PCS-specific deploy-time properties being defined with the Maven pom.xml.

Step 3: Create a configuration plan (Optional)

If the integration has connections, then these will need to be defined in a JSON file that is packaged with the artifact itself. Below is an example configuration containing two REST API connections.

{
    "connections": {
        "FLIGHTAIRLINESREST": {
            "connectionProperties": [
                {
                    "propertyValue": "https://${flights.api.host}",
                    "propertyName": "connectionUrl"
                }
            ]
        },
        "LOGGERREST": {
           "connectionProperties": [
                {
                    "propertyValue": "https://${logger.api.host}",
                    "propertyName": "connectionUrl"
                }
           ]
        }
    }
}

Property references (e.g. flights.api.host and logger.api.host in the example above) will be automatically made available as artifact properties in Myst. These properties can be defined with different values per environment.

The connection identifiers (e.g. FLIGHTAIRLINESREST and LOGGERREST in the example above) must match the identifiers of the connections shown in the console. These identifier for a given connection can be found by clicking on Primary Info when viewing the connection.

Each connection type may have different available properties. The available properties for a given connection can be obtained by calling the connection through a GET API call on https://${OIC_HOST}/ic/api/integration/v1/connections/${OIC_CONNECTION_ID}.

Make sure the location of the JSON file is indicated against the ics.configuration-plan property in the pom.xml.

Step 4: Unpack the archive to the version control system (Optional)

Whilst it is possible to publish the artifact directly to Maven. It is recommended to rebuild the artifact from source. This will ensure that individual files changes are version controlled. This approach also allows for the configuration plan to be easily packaged alongside the artifact. An unpacked Integration Cloud Archive has a structure similar to the following

├── ics.json
├── icspackage
│   ├── appinstances
│   │   ├── FLIGHTAIRLINESREST.xml
│   │   └── LOGGERREST.xml
│   └── project
│       └── RETRIEVEALLAIRLINES_01.00.0000
│           ├── PROJECT-INF
│           │   └── project.xml
│           ├── ics_project_attributes.properties
│           └── resources
└── pom.xml

Step 5: Set a unique version number for our artifact

When publish an artifact to Maven and later registering it with Myst, it is important to ensure that the version number of the artifact is unique. This can be done via Maven prior to building the artifact. An example of this is described here.

Step 6: Build and publish your application to a Maven Repository

We can achieve the build and publish using Maven. For example:

mvn clean deploy

Alternatively, if we skipped step 3 and 4 and would rather publish our artifact directly to Maven, we may wish to do this directly using the deploy:deploy-file goal. For example:

mvn deploy:deploy-file -Durl=http://admin:password@your-myst-instance.com/artifactory/libs-release-local \
-Dfile=RetrieveAllAirlines.iar \
-DgroupId=com.rubiconred \
-DartifactId=RetrieveAllAirlines \
-Dversion=1.0-${BUILD_NUMBER} \
-Dpackaging=jar

Be sure to publish to the same Artifact Repository that is defined within the Myst Continuous Delivery Profile. This ensures that Myst will be able to retrieve the artifact at deploy-time.

Step 7: Register the artifact with Myst

This can be achieved through the Myst Java SDK or via the REST API. Alternatively, if you are using Jenkins, you can use the Myst Jenkins Plugin.

Once the Artifact is registered with Myst it can be added to a new or existing Application Blueprint and promoted across Oracle Integration Cloud or Integration Cloud Service instances using a Release Pipeline.

Process Cloud Archive

Oracle Process Cloud Archives can be deployed using Myst. These artifact types can be deployed to either Oracle Integration Cloud or the Legacy Process Cloud Service. For each version of an Oracle Process Cloud Archive which you wish to deploy, you must first register it with Myst. These steps can be performed manually, however, it is recommended to include these steps in a CI server job, so that they can be triggered automatically as required.

Step 1: Export your Process Cloud Archive

We can export either from the Oracle Integration Cloud console, Process Cloud Service console or via the REST API for either service.

To export via the Oracle Integration Cloud console:

1. Navigate to Process Builder then Applications within the Oracle Integration Cloud console
2. Download the Application. This will download a file with the .exp file extension.

To export via the Oracle Integration Cloud REST API:

1. Ensure you have curl and jq installed and are running on a Linux based machine
2. Set the following environmental variables to match your environment:

   OIC_USERNAME="your-email@your-company.com"
   OIC_PASSWORD="your-password"
   OIC_HOST="your-instance.uscom-central-1.oraclecloud.com"
   OIC_PCS_PROJECT_ID="Administer%20Patient%20Well%20Being"
   OIC_PCS_SPACE_NAME="RxR"
   OIC_PCS_EXPORT_FILE_NAME="AdministerPatientWellBeing.exp"
   

3. Ensure OIC_PCS_SPACE_NAME matches the design-time space where your Process Application is located. In the example above, it is in the RxR space.
4. Also, ensure that any space character in your project name is replaced with the %20 character.
5. Execute the following to export your project.

   export OIC_PCS_SPACE_ID=$(curl -u ${OIC_USERNAME}:${OIC_PASSWORD} https://${OIC_HOST}/bpm/api/4.0/spaces/ | jq -r ".items[] | select( .name == \"${OIC_PCS_SPACE_NAME}\") | .id")
   curl -u ${OIC_USERNAME}:${OIC_PASSWORD} https://${OIC_HOST}/ic/api/process/v1/spaces/${OIC_PCS_SPACE_ID}/projects/${OIC_PCS_PROJECT_ID}/exp > ${OIC_PCS_EXPORT_FILE_NAME}
   

To export via the Process Cloud Service console:

1. Navigate to Develop Processes within the Process Cloud console
2. Download the Application. This will download a file with the .exp file extension.

To export via the Process Cloud Service REST API:

1. Ensure you have curl and jq installed and are running on a Linux based machine
2. Set the following environmental variables to match your environment:

   PCS_USERNAME="your-email@your-company.com"
   PCS_PASSWORD="your-password"
   PCS_HOST="your-instance.process.us2.oraclecloud.com"
   PCS_PROJECT_ID="Administer%20Patient%20Well%20Being"
   PCS_SPACE_NAME="RxR"
   PCS_EXPORT_FILE_NAME="AdministerPatientWellBeing.exp"
   

   • Ensure PCS_SPACE_NAME matches the design-time space where your Process Application is located. In the example above, it is in the RxR space.
   • Also, ensure that any space character in your project name is replaced with the %20 character.
3. Execute the following to export your project.

   export PCS_SPACE_ID=$(curl -u ${PCS_USERNAME}:${PCS_PASSWORD} https://${PCS_HOST}/bpm/api/4.0/spaces/ | jq -r ".items[] | select( .name == \"${PCS_SPACE_NAME}\") | .id")
   curl -u ${PCS_USERNAME}:${PCS_PASSWORD} https://${PCS_HOST}/bpm/api/4.0/spaces/${PCS_SPACE_ID}/projects/${PCS_PROJECT_ID}/exp > ${PCS_EXPORT_FILE_NAME}
   

At the time of writing, Oracle do not support automated deployment of Decision Model Applications. Therefore, Myst is only able to support deployment of Process Applications at this time.

Step 2: Create the Maven pom.xml

1. Create a pom.xml. Be sure to set the Maven details to match your environment. An example pom.xml is shown below.

   <?xml version="1.0" encoding="UTF-8"?>
   <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
   <modelVersion>4.0.0</modelVersion>
   <groupId>com.rubiconred</groupId>
   <artifactId>AdministerPatientWellBeing</artifactId>
   <packaging>jar</packaging>
   <version>1.0-SNAPSHOT</version>
   <name>Administer Patient Well Being</name>
   <properties>
    <myst.component.type>opaas-pcs</myst.component.type>
    <pcs.deployment-name>Administer Patient Well Being</pcs.deployment-name>
    <pcs.space-name>RxR</pcs.space-name>
   </properties>
   <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-shade-plugin</artifactId>
        <executions>
          <execution>
            <phase>package</phase>
            <goals>
              <goal>shade</goal>
            </goals>
            <configuration>
              <filters>
                <filter>
                  <artifact>*:*</artifact>
                  <excludes>
                    <exclude>META-INF/</exclude>
                  </excludes>
                </filter>
              </filters>
            </configuration>
          </execution>
        </executions>
      </plugin>
    </plugins>
    <resources>
      <resource>
        <directory>${project.basedir}</directory>
        <excludes>
          <exclude>pom.xml*</exclude>
        </excludes>
      </resource>
    </resources>
   </build>
   </project>
   

Myst supports the following PCS-specific deploy-time properties being defined with the Maven pom.xml.

Step 3: Create a configuration plan (Optional)

By default, Process Applications are deployed with the following configuration plan

{
  "revisionId": "1.0",
  "overwrite": true,
  "forceDefault": true
}

To use an alternative configuration plan, create a file at the same directory as the pom.xml so that it will be included in the artifact when it is built. Make sure the location of this file is indicated against the pcs.configuration-plan property in the pom.xml.

Step 4: Unpack the archive to the version control system (Optional)

Whilst it is possible to publish the artifact directly to Maven. It is recommended to rebuild the artifact from source. This will ensure that individual files changes are version controlled. This approach also allows for the configuration plan to be easily packaged alongside the artifact. An unpacked archive has a structure similar to the following

├── Administer\ Patient\ Well\ Being
│   └── SOA
│       ├── HumanTasks
│       ├── Schemas
│       ├── WADLs
│       ├── WSDLs
│       ├── businessCatalog
│       ├── businessIndicators.bi
│       ├── composite.xml
│       ├── connectors
│       ├── contentMetadata.xml
│       ├── forms
│       ├── kpis.kpi
│       ├── measurementActions.xml
│       ├── measurements.xml
│       ├── organization.xml
│       ├── processes
│       ├── projectInfo.xml
│       ├── resources
│       ├── simulations
│       ├── socialMetadata.xml
│       ├── wsm-assembly.xml
│       └── xsl
├── pcs.json
└── pom.xml

Step 5: Set a unique version number for our artifact

When publish an artifact to Maven and later registering it with Myst, it is important to ensure that the version number of the artifact is unique. This can be done via Maven prior to building the artifact. An example of this is described here.

Step 6: Build and publish your application to a Maven Repository

We can achieve the build and publish using Maven. For example:

mvn clean deploy

Alternatively, if we skipped step 3 and 4 and would rather publish our artifact directly to Maven, we may wish to do this directly using the deploy:deploy-file goal. For example:

mvn deploy:deploy-file -Durl=http://admin:password@your-myst-instance.com/artifactory/libs-release-local \
  -Dfile=AdministerPatientWellBeing.exp \
  -DgroupId=com.rubiconred \
  -DartifactId=AdministerPatientWellBeing \
  -Dversion=1.0-${BUILD_NUMBER} \
  -Dpackaging=jar

Be sure to publish to the same Artifact Repository that is defined within the Myst Continuous Delivery Profile. This ensures that Myst will be able to retrieve the artifact at deploy-time.

Step 7: Register the artifact with Myst

This can be achieved through the Myst Java SDK or via the REST API. Alternatively, if you are using Jenkins, you can use the Myst Jenkins Plugin.

Once the Artifact is registered with Myst it can be added to a new or existing Application Blueprint and promoted across Oracle Integration Cloud or Process Cloud Service instances using a Release Pipeline.

SCA

OSB

MDS

ADF

Java EAR

Java WAR

SQL

B2B

BAM

MFT

Application Configuration (Properties/XML)

OSB Custom XPath

OWSM Policy

ODI Application (XML)

JAR Library

Java Shared Library