Imports the application resources from the artifacts repository and deploys the application to one or more selected cloud instances. Performs environment-specific property replacement for one or more service endpoint configuration plans ( if exists ) before deployment. 

It is required to have exported the application resources using exportApplication operation prior to running the import. This operation uses the application artifact zip file (ApplicationId-ApplicationVersion.zip) from the artifacts repository and derives the ApplicationVersion to be used for the application imported to the target cloud instances. It will result in failure when there is no exported application artifact in the repo, 

Configuration plans can be used for this operation, see below for more details. It also performs application 'Stage' or 'Publish' based on the operation type plugin input after successfully importing all the resources. 

Environment/Instance Properties

Project Properties

Cloud Account Properties

Inputs

Outputs

Artifacts

This operation consumes the artifacts stored in the artifacts repository.

Endpoint Selection

This operation will select all available endpoints associated to the environment/instance.

Endpoint Execution

This operation will execute on any one of the selected endpoints and will be random in the determination of which one.

Configuration Plans

Configuration plans are used to dynamically update the environment specific information for service endpoints used across the applications. VBCS application stores the server endpoint configuration for all the service connections in the json format under '/services/' directory. This operation utilizes one or more config plans ( explained below ) to update the appropriate server definition prior importing the resources to the target cloud instance. 

Service Connection or Backend Connection specific ( global )

Lets say you have a 'getAPI' service connection in your application. Create a configuration plan with the getAPI-ovbconfigplan.json file name. The contents of the file is copied from the original service definition in the application resources and then overridden based on what you need it to be for this import operation. 

Steps to copy from the application service connection definition file

• Download the application artifact zip file created using exportApplication operation
• Unzip the application artifact zip file
• Go to 'services' directory 
• Go to appropriate service name directory. In this case, it is 'getAPI'
• Look for a *.json file have all the service definitions. It is expected to have only one *.json file in this directory
• Copy all the contents from /services/getAPI/someName.json to your configuration plan file
• Repeat the above steps for all the service definitions you want to override. 
  
  

{
    "openapi": "3.0.0",
    "info": {
        "title": "Get API Details",
        "version": "1.0.0"
    },
    "servers": [
        {
            "url": "https://instancename.servicename.ocp.oraclecloud.com:443/ic/builder",
            "description": "Ic",
            "x-vb": {
                "authentication": {
                    "authenticated": {
                        "type": "basic",
                        "credentials": "vb_018f0546-3ec5-4de3-8a20-2989bab79b31"
                    }
                }
            }
        }
    ],
    "paths": {
        "/api/": {
            "get": {
                "operationId": "getApi",
                "responses": {},
                "x-vb": {
                    "actionHint": "getMany"
                }
            }
        }
    }
}

Steps to copy from the application service backend definition file-

• Download the application artifact zip file created using exportApplication operation
• Unzip the application artifact zip file
• Go to 'services' directory 
• Open the /services/catalog.json file which stores all the backend service definitions
• Look for the backend name that you are looking for and copy the contents to your configuration plan file
• Repeat the above steps for all the service backend definitions you want to override. 
  
  

{
	"backends": {
		"backendService1": {
			"serviceType": "adf-describe",
			"servers": [
				{
					"x-vb": {
						"authentication": {
							"authenticated": {
								"type": "cloud"
							}
						}
					},
					"description": "Default Server",
					"url": "https://devserver.com"
				}
			],
			"transforms": {
				"path": "vb/BusinessObjectsTransforms"
			},
			"description": "Backend sample service 1"
		},
		"backendService2": {
			"serviceType": "ics",
			"servers": [
				{
					"x-vb": {
						"authentication": {
							"authenticated": {
								"type": "cloud"
							}
						}
					},
					"description": "Default Server",
					"url": "https://dev.integrations.com"
				}
			],
			"description": "Backend sample service 2"
		}
	}
}

{
	"backendService1": {
		"serviceType": "adf-describe",
		"servers": [
			{
				"x-vb": {
					"authentication": {
						"authenticated": {
							"type": "cloud"
						}
					}
				},
				"description": "Default Server",
				"url": "https://devserver.com"
			}
		],
		"transforms": {
			"path": "vb/BusinessObjectsTransforms"
		},
		"description": "Backend sample service 1"
	}
}

Service Connection or Backend Connection specific ( environment specific )

All the steps to create the configuration plan file will be the same as explained in (global) section above. The only difference will be the configuration file name which should be environment specific. 

For the examples shown above, the (development) environment specific configuration plan file names will be 

• FD_ARTIFACTS_DIR/configplans/getAPI-ovbconfigplan-development.json
• FD_ARTIFACTS_DIR/configplans/backendService1-ovbconfigplan-development.json

No Configuration plans 

You may choose not to utilize the dynamic reusable configuration plans. You will just not copy any configuration plan files in the artifacts repository and the operation will just do the import without any modifications. In this case, you will need to setup multiple deployment profiles in your application which will be duplicated across multiple instances.