Skip to main content

Deploying integrations

This page describes how to deploy a change from your development environment to your RegTest and production environments in iCore Cloud Services.

note

Do you want to deploy your integrations yourself? See Deploying integrations - self service.

Having a process for deploying changes is important for several reasons:

  • It provides users with a consistent, uniform method to make changes in their integrations.
  • It prevents users from making uncontrolled changes in the RegTest and Production environments.
  • It enables smooth handling of changes to the RegTest and Prod environment without access to iCore tools.
  • It creates a history/log of the changes that have been made.

A change will always be deployed to the RegTest environment first. Once the change has passed available regression tests, it can be deployed to your production environment. Details for deploying a change can include both the RegTest and the production environment in the same deployment ticket.

To deploy changes in your Dev environment to your RegTest and production environment, do either of the following:

To deploy a package the following three resources are required.

note

To learn how to upload a dependency file such as public-private key-pairs, see using system storage.

Deployment form​

The Deployment form is the web-based form that opens when you go to the Self Service Portal and create a new deployment request.
The Deployment form keeps the deployment together. It contains references to the other required files, as well as specific instructions on how the deployment should be performed.

  • An IEO file is required. Attach the IEO when submitting the form.
  • A Response file is required. Attach this file when submitting the form.
  • Deployment start is optional. Here you can enter a time/date when you want the deployment to start.
  • Additional Information is optional – here you can make any custom requests related to the deployment. For example: starting/stopping iCore Timers, making changes to endpoint settings for the RegTest/Production environment, etc.
note

Once the ticket has been submitted you can follow the current status as well as any feedback along with your other iCore support tickets in the iCore Self Service Portal (SSP).

IEO-file​

The IEO-file contains exported data from your iCore system. In most cases it is an export of your complete iCore system. However, a partial export can also be used if you for example have a specific category that you want to export.

When you export your data to an IEO-file from your Development system, the recommended target location is your common storage. For more information, see using common storage.

caution

Batch Import Response File​

Before deploying, you must create the batch import response file. You can either create a new file or edit one of the provided examples.

The response file contains rules and conditions for the import. Each item in the export file is matched against a set of conditions of each rule, in document order.

  • A rule will only be run if all associated conditions are fulfilled – otherwise the next rule in the document is evaluated until a match is found.
  • If no rule matches an item, an error is reported and the operation is aborted. Each rule specifies an action, and optionally a set of responses, which describes what happens when the rule is run.

Some iCore entities have several import options, which are specified in the batch import response file. If you do not specify an option, the default value will be applied automatically.

note

For more information about batch import, see Batch import.

Detailed description of rules and conditions​

note

For a detailed description of rules and conditions, see Batch import rules

Response file examples​

This section contains examples of batch import response files.

note

Examples for the response files can be found in Response file examples