Skip to content

Applying the Delivery to the Use Place

Once the delivery is created, tested, and approved, you can now deploy it to the relevant use place environment. Before you deploy, make sure that the delivery you are about to deploy is created based on the latest delivery deployed in the relevant use place environment, as deliveries can only be deployed in an incremental order.

Deploying a Normal Delivery to Use Place

The process is explained using an example.

The delivery version which is deployed in the CFG environment (1.10.0) should be taken as the baseline when creating a new normal delivery. The new normal delivery version will be 1.11.0 which was created by taking 1.10.0 as the baseline delivery. The 1.11.0 can now be deployed on top of the 1.10.0 in the CFG.

Deploying a Corrective Delivery to Use Place

The process is explained using an example.

The delivery version which is deployed in the CFG environment (1.11.0) should be taken as the baseline when creating a new corrective delivery. This is on the assumption that the identified defect exists in the 1.11.0 delivery. The new corrective delivery version will be 1.11.1 which was created by taking 1.11.0 as the baseline delivery. The 1.11.1 which contains the fix for the defect, can now be deployed on top of the 1.11.0 in the CFG.

Residency Options

Depending on the Residency option a customer has selected for their Use Place, the deliveries are applied in two ways.

Residency Option 1 - IFS Cloud:

In this case, the approved delivery can be applied to the use place by using a scheduled job via SNOW. The process below explains the delivery deployment of IFS Cloud.

Use Place Management Form in SNOW

CSM Portal - https://support.ifs.com/csm

The IFS Lifecycle Experience Use Place Management Form can be found in the Catalogs menu as shown below.

In the form, enter customer details, use place detail,s and scheduling information.

Residency Option 2 - Remote:

In this scenario, the user has to download the delivery via the Deliveries section in the Build Place and apply it themselves, but beforehand the user must first have a properly configured remote Use Place to apply a delivery.

Artifact Download Functionality

In the event where the requirement arises to deploy the deliveries to the Use Place in a remote location, the scripts, other artifacts, and runtime repository information needed to set up the remote Use Place can be found in the Manage Deployments section in the Build Place.

1. General Artifacts

Both customers with residency options 'Cloud' and 'Remote' will have the option of downloading some general artifacts from the Manage Deployments section. These include Remote Virtual Appliance, Remote Bootstrap Zip, and Remote Aviation Maintenance Deployment.

Note

Please note that the Remote Virtual Appliance Artifacts are de-supported from 23R2 GA onwards and hence not shown for users in 23R2 or later.

2. A&D Artifacts

Customers with residency option 'Cloud' and the industry is A&D, will have a separate set of artifacts called Remote Aviation Maintenance Deployment in addition to the general artifacts.

The artifacts are available for all the Service Update versions related to the release version the customer is in. The relevant version can be selected and downloaded to be deployed in the Use Place.

Please note that this feature is available only for A&D customers in 22R2 and beyond.

The deployment instructions for A&D customers can be found in the "Maintenix" section of the Remote Deployment Guide in the Technical Documentation.

3. PSO Artifacts

Customers with the residency option 'Remote' who have purchased PSO as an add-on to IFS components are able to download the latest PSO artifacts from the LE portal.

4. Oracle Database Software Artifacts

The Oracle Database software, base version, and Release Updates will be available for all customers to be deployed for remote instances of IFS Cloud.

The artifacts include the following:

  • All available Oracle Release Versions supported and verified by IFS.

  • The 4 most latest Oracle patch versions for each Release Version.

  • The Oracle base versions for each Release Version.

  • One patch version would include the Oracle patch, OPatch tool, and other dependent required patches (often OJVM) compressed into one zip file.

  • All the artifacts will be available for both Windows and Linux operating systems.

It is recommended to apply the latest Release Update. The Release Updates are cumulative, so earlier updates are always included in the latest one.

Note

Each file size of an artifact would be approximately 2GB.

Password Generation for Customers with Cloud Residency Option

A password must be generated in order to view the runtime repository information. If the credentials are not visible, click on the Generate Password button to generate this information.

This task needs to be performed just once. Once completed, you can access the runtime repository information, as depicted in the screenshot provided.