Managing Solutions

Solutions are the units of all business functionality created for concrete integration scenarios.

Solutions have Releases to represent their evolution over time.

Every release consists of a set of Software Assets such as

As every Release has different sets of Software Assets, these Assets themselves may represent new versions of Assets in previous Releases, but also may represent newly added logic.

The following sections describe how a Solution for IPP is configured in the Lifecycle Management Portal.

Create Solution

To create your Solution right-click on the Assets word and select the Create Solution item from the popup menu.

The Solution Dialog will open.

The General Tab

Select the General tab.

Infinity SasS Platform Solution GUID

This field is currently not used.

Name

Enter a meaningful asset solution name. An example, as shown above, Customer On Boarding Model

This name will appear under the asset tree.

There is no required naming convention - automatic validation will ensure only accepted content is entered.

Provider Name

From the Provider Name drop down menu list select the name of the team on behalf you are intending to create the Solution should you be member of multiple teams. Otherwise the only entry will be the name of your team.

An example, as shown above, SGS BPM Service Line - APAC

Description

Enter a meaningful description for your asset solution. The description defined here will appear in the dialog box when you mouse-over the solution from the Assets Tree.

Click the Create button.

Your new solution will now appear Under the Assets tree.

Releases

Releases allow you to define releases of software artifacts. A Release may include process models, business logic code, and UI screen definition. These artifacts define your Solution as at this release. The Create Release function can be likened with deploying a model locally using the Export, Deploy Model function within IPP.

For the business analyst whose intent to deploy only a process model, the Release will only incorporate the XPDL. However, if that process model relies on additional business logic code for example java files, the model will not deploy to the cloud successfully. If the solution one is deploying has a model and business logic both, his release will have and xpdl and a jar (set of java classes).

Creating a Release

Right-click on the Solution Name and select the Create Release menu item.

The Release Dialog opens.

General Tab

Select the General tab.

Synopsis

The name entered in the Synopsis field should be something to reflect the composition and version of the model being deployed e.g. Release 1.0 then Release 2.0. With these names one can easily identify that Release 2.0 is an upgrade to Release 1.0.

Deploy By Default

You can think of the Default Release as the "current release" of your solution. This indicates that you intend to deploy this Release and all the Releases this Release depends on whenever an instance of the Solution is created.

Note that the Deploy by Default option can only be assigned at the creation of a new Release. The setting is automatically reset for each subsequent deployment of that Release. There can be only one Release per solution, i.e. if one sets it for a release the earlier one that has this set gets unset.

An example of a scenario where you do NOT Deploy by Default, you have an interested customer who wants to consume your solution on IOD, but he/she has some questions from your solution. This means you need to upgrade you solution and then only deploy it. In those cases you can go ahead create a tenant for this customer, deploy any other release of your choice and keep him/her engaged until you are ready with specific solution for him/her. May be a common release called demo, that you want to use for keeping incoming customers engaged.

Target Platform Solution

Select the Platform Solution on which you want your Release depend on. The Target Platform Solution drop down lists all the available Platform Solutions.

Release

Select the Platform Release on which you want your Release depend on. The Target Platform Release drop down lists all the Releases of selected Target Platform Solution.

Description

Enter a meaningful description for your Release here. What you enter here will appear when you mouse over the Release from your Assets tree.

Software Assets Tab

Switch to the Software Assets tab in the Release dialog box.

For the business analyst who is only deploying a process model within this Release, there are two relevant choices available:

For a new Release, select Process Model (Version/Initial Deployment) .

If the process model to be deployed is overriding an existing process model select Process Model (Overwrite) .

Type

Process Model (Version/Initial Deployment)

Name

Enter a meaningful name for the Software Asset.

This information will appear under the Solution Instance in the Asset Tree.

Description

Enter a meaningful description for the Software Asset of your Release.

For example: Customer On Boarding Model

This description will appear under the solution instance in the Asset Tree.

Software Asset Retrieved From Registry

Leave un-ticked.

This function is only used by the IOD Technical Team when a Release needs to be grouped together.

Asset GUID Infinity Registry

Leave blank.

This function is only used by the IOD Technical Team when a Release needs to be grouped together.

File

Click on the Browse button

Locate the XPDL process model file that you want to deploy.

Select Upload

Upload means we are confirming that this artifact would become part of this release and that file will be added to the Software Assets table.

Please note that the order of the assets is important. The default deployment order is as below:

Dependencies Tab

Select the Dependencies Tab.

Where Software Assets compose a complete release, Dependencies allows the business analyst to identify anything that this release depends on but doesn't want to compose within itself.

As we are only having one Release for this solution, dependencies do not exist.

Overwrite

Select the Overwrite Tab

This tab is only referenced when a Release is being updated from a previous version. The Business Analyst will select this tab when an older Release is to be removed and a new one is to be deployed.

Note: Not to be used in case you are Overwriting a model, that means you only have an xpdl in a release and you are only interested in overwriting that release with a new release containing updates to the existing model, in that don't select both "Process Model (Overwrite)" and Overwrite tab.

Select Create.

Your new Release will appear under the Solution, within your Assets tree.


Updating Your Solution

When your process model is updated, and you want to overwrite the deployed process model with the updated version, you undertake the same steps as illustrated above. The only variance is:

From the Release dialog box:

Deleting Your Solution

When you want to delete your Solution from the Assets list: