Browse Prior Art Database

Mechanism to isolate business process execution session in a shared deployment environment

IP.com Disclosure Number: IPCOM000196147D
Publication Date: 2010-May-27
Document File: 2 page(s) / 29K

Publishing Venue

The IP.com Prior Art Database

Abstract

Generating runtime artifacts for an application and deploying them to a runtime environment allows users with the appropriate authorization privileges to be able to execute the application. In a managed deployment environment (see publication CA8-2009-0042), where users desires to test the execution logic of their business process in a test session would encounter isolation issues since their test session would contain other artifacts which is not part of their test session and furthermore have their test session be visible to other users with the appropriate authorization privileges. A mechanism to isolate business process execution sessions in a shared deployment environment is needed. The solution is to isolate the business process execution sesssion from one another by introducing a concept of a test session ID which is unique for each deployed process and that is specified in both the business environment and the runtime environment.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 56% of the total text.

Page 1 of 2

Mechanism to isolate business process execution session in a shared deployment environment

Disclosed is a process to isolate business process execution sessions in a shared deployment environment. Generating runtime artifacts for an application and deploying the artifacts to a runtime environment allows users, with appropriate authorization privileges, to execute the application. When a user test the execution logic of business processes in a test session of a managed deployment environment isolation issues are typically encountered because the test session contains artifacts that are not part of the user test session. In addition the user test session is visible to other users with appropriate authorization privileges. A mechanism to isolate business process execution sessions in a shared deployment environment is needed. The disclosed technique separates the business process execution sessions from each other by introducing a concept of a test session identifier which is unique for each deployed process and that is specified in both the business environment and the runtime environment.

The disclosed technique provides a capability in each deployment session for artifacts defining the business logic to have a session ID specified. The artifacts are also deployed to the runtime environment. Similarly, configuration of the business environment for the same deployment session is configured with the same test session ID. The resulting business environment and associated widgets interact with the runtime environment and use the test session ID to query for deployed artifacts of the deployment session. The following figure illustrates a flow of interaction.

 Business Environment Configuration

Widget A Filter = ID

Widget B Filter = ID

4. Generate
Configuration 5. Deploy

Business Environment

Widget A

Widget B

Development

Environment

6. Query 7. Results returned for display

1. Get unique ID

2. Generate Runtime Artifacts

Runtime Environment

Component A

Component B

Provider

Provider

Component A Artifact Property = ID

Component B Artifact Property = ID

3. Deploy artifacts

Property = ID is optional - Would work if ID not present

1

Page 2 of 2

1. Get a unique ID from the runtime en...