Open topic with navigation

TIBCO® BPM Enterprise 5.5.0

# Example - Phase 4 Extending the Organization Model

Finally, the project is rolled out to include other parts of the company.

The initial Finance division implementation defines a single application, FinanceProc1, which involves departments d, e and f.

## Design Time

The solution designer:

(1) Creates a FinanceOrg organization model with a version number of V2.1.0.ts.

(2) Adds participants from departments d, e and f to FinanceProc1. Each participant is defined as an external reference to the FinanceOrg organization model.

FinanceOrg’s major version number (2) is recorded (internally) in the FinanceProc1 process definition as part of the participant definitions.

Note: The FinanceOrg organization model does not need to include departments a and c - it simply provides a view of those parts of the organization that are relevant to the Finance department and the FinanceProj1 application.

Because this will be an extension to the existing runtime organization model (which does not impact departments a and c) the same major version number can be used with an update to the minor version number.

## Deployment

The solution designer:

(1) Deploys the FinanceOrg organization model as the easyAsOrg2 application, version 2.1.0.ts.

(2) Deploys the FinanceOrg project as the FinanceProc1 application, version 1.0.0.ts.

## Runtime

TIBCO BPM Enterprise merges the changes from the deployed FinanceOrg organization model - the addition of departments d, e and f - into the existing V2 runtime organization model.

(1) Directory Services adds the deployment artifact from the 2.1.0.ts version of the easyAsOrg2 application to the V2 organization model.

This establishes a dependency on the deployment artifact from the 2.0.0.ts version of the easyAsOrg1 application.

(2) The platform does not delete the 2.0.0.ts version of the easyAsOrg1 application (because it has a different name from the deployed application).

(3) The V2 organization model is the combination of both deployment artifacts.

## User Application Dependencies

Note: In the following diagram, application dependencies are shown using the convention [Min,Max):

- Min is the version referenced when the process application is initially deployed. The square bracket denotes that the value is inclusive.
- Max is the next major version. The round bracket denotes that the value is exclusive.

For example, [1.0.0.ts,2.0.0.ts) denotes any version from 1.0.0.ts (inclusive) to 2.0.0.ts (exclusive). (The ts is not used in the comparison.)

(1) FinanceProc1 has a dependency on the easyAsOrg2 application, version 2.1.0.ts (inclusive) to version 3.0.0.ts (exclusive).

(2) ClaimProc1 and ClaimProc2 have a dependency on the easyAsOrg1 application, version 2.0.0.ts (inclusive) to version 3.0.0.ts (exclusive).

(3) ClaimProc1, ClaimProc2 and FinanceProc1 all execute against V2 of the runtime organization model (which includes departments a, c, d, e and f).

Note: If the FinanceOrg organization model was instead deployed as version 3.0.0.ts of the easyAsOrg1 application:

- Version 2.0.0.ts of the easyAsOrg1 application would be deleted.
- This would undeploy the V2 runtime organization model. The ClaimProc1 and ClaimProc2 applications would then enter a "Waiting for Dependencies" state, as they would be unable to resolve their references to departments a and c.

## Alternative Scenario

Instead of using a new application name, the FinanceOrg project could have been deployed as version 2.1.0.ts of the easyAsOrg1 application. This would have resulted in the scenario shown here.

In this case:

(1) FinanceProc1 has a dependency on the easyAsOrg1 application, version 2.1.0.ts (inclusive) to version 3.0.0.ts (exclusive).

(2) ClaimProc1 and ClaimProc2 have a dependency on the easyAsOrg1 application, version 2.0.0.ts (inclusive) to version 3.0.0.ts (exclusive).

Note: Although version 2.0.0.ts of this application has been deleted, the dependency is still resolved by version 2.1.0.ts.

(3) ClaimProc1, ClaimProc2 and FinanceProc1 execute against V2 of the runtime organization model (which now includes only departments a, c, d, e and f).

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO® BPM Enterprise

Copyright © 2015-2024. Cloud Software Group, Inc. All Rights Reserved.