Noteworthy Points - Einsight

1.

The Java Composite Application Platform Suite (Java CAPS) allows companies to assemble large-scale applications built on existing systems and infrastructure. Java CAPS is an application-level network that unifies connectivity among people, application systems, and devices in different locations and across organizations. Business services facilitate the implementation of extended applications. Service oriented architectures (SOA) clarify design and enable reuse by sharing logic and data among different client systems and users.

2.

eInsight BPM is a component of Java CAPS that delivers Business Process management features and functions to the product suite. Business Process management is a strategic orchestration of the movement of information and the flow of complex processes between participants (systems, users, and organizations) to accomplish larger business objectives.

3.

The eInsight Engine runs within the Java CAPS Integration Server or a third-party application server.

4.

eInsight BPM provides you with a clear view into the internal and external processes of an organization. These processes can be executed by either computer systems or personnel. eInsight BPM speeds the design and deployment of Business Processes by providing an open process modeling environment using Business Process Modeling Notation (BPMN) for the graphical notation of a Business Process. eInsight BPM automatically generates the code needed to implement the Business Process across all participating web services such as applications and business partners. You drag and drop components into the process model and then specify the additional flow control and business rules that manage what services are called at what time. eInsight BPM supports importing and exporting Business Process Execution Language for Web Services (BPEL4WS) to share processes with third-party tools.

5.

The technologies that carry out eInsight BPM’s functions are entirely based on industry standards. eInsight BPM’s architecture uses the following standards.

a. b. c. d. e.

Business Process Modeling Notation (BPMN), from the Business Process Management Initiative (BPMI) standards body, provides a standard graphical view for Business Process Execution Language for Web Services (BPEL4WS). Business Process Execution Language for Web Services (BPEL4WS) is the underlying code generated when creating a Business Process. Web Services Description Language (WSDL) is an XML-based language used to define web services and describe how to access them. All eInsight Business Processes are automatically described using generated WSDL. J2EE™ Connector Architecture (JCA) provides a mechanism to access external applications and data. The JCA engine is implemented as a standard JCA 1.5 module that plugs into the Java CAPS Integration Server. The eInsight Engine uses Java Enterprise Edition 1.4.

6.

There are two phases of Business Process Management. The first phase, design, begins before you start using eInsight BPM and ends once the Business Process is deployed. The second phase is called runtime, refers to the tasks that you perform after the Business Process is deployed.

7.

eInsight BPM supports the following database platforms:

a. b. c. d.

Oracle 8i (8.1.7), 9i (9.0.1, and 9.2), and 10g Sybase 12.5 MS SQL Server 2000 IBM DB2 Universal Database 8.1

(When creating an Oracle 8.1.7 database, the required minimum db_block_size for eInsight BPM is 16KB.) 8.

The Enterprise Manager SVG plug-in is not required for viewing Connectivity Maps in Enterprise Manager. However, installing this component enhances the Connectivity Map’s capabilities.

9.

The JDK installation must be at version 1.5 or later in order for the eDMT to run.

10. A Business Process is a collection of actions that take place in your company, revolving

around a specific business practice. These processes can involve a variety of participants and might include internal and external computer systems or personnel. In eInsight BPM, you create a graphical representation of the Business Process called a Business Process model. The model defines each component in the process and the flow of data through those components.

11. The modeling elements you add from the Business Process Designer are standard BPEL elements.

12. Activities are elements in a Business Process model that specify the logical flow of information. The activity name must contain at least one character (A-Z, a-z, or 0-9), it must start with a letter or an underscore (_), and it may contain spaces. Activities are: a. Activity Elements

b. c. d. e.

Branching Activities Intermediate Events Scope Element While Element

13. The area where you map attributes in the Business Rule Designer is called the Mapper. 14. XPath predicates are only used with repeating nodes and allow you to isolate particular elements in repeating nodes at runtime. Predicates allow you to define conditional mappings in a business rule when using Business Process attributes that contain repeating values.

15. If the sub-process is to be invoked as a synchronous request/reply web service, the Receive and Reply must be associated with the same partner, port type, and operation. These properties can all be configured in the property sheet for the user activity.

16. From the Project Explorer, by right-click a Business Process and clicking Generate

Report, you can generate a custom HTML report of your Business Process model. This report displays information about the configuration of the Business Process, including activities, attributes, trading partners, correlation sets, and so on. The report can be as detailed or as high-level as you want it to be. You can specify the objects, details, and properties to include on the report. Use this report to evaluate the Business Process prior to finalizing the configuration.

17. Partners in eInsight identify external systems to which Project components are mapped in the Connectivity Map. If you are invoking multiple components such as web services, JMS messages, or connectors such as eWays, you must create unique partner names for those components. Then, when you create the Connectivity Map, there will be a unique partner for each component rather than just one partner for multiple components. This enables you to successfully associate those components in your Deployment Profile and deploy your Project.

18. clientSOAP cannot be completely configured until the server Project is deployed. Deploying the server Project gives you the servlet context for the client SOAP external system.

19. Correlation keys are individual data values contained within both the incoming

message and the eInsight BPM engine. When an arriving message contains a value that matches a configured correlation key, the unique Business Process instance associated with that value continues processing to the next step of the Business Process. These can be set using properties of the business process under “correlation” tab. Correlation sets are groups of properties (correlation keys) shared by all messages in the group. A correlation set matches messages and conversations with a Business Process instance.

20. Logic can be added to business process either by adding business rule or by invoking web service.

21. You can implement a WSD object that defines multiple operations under one port type and uses one URL for the operations. When you implement this type of WSD object, there is only one partner in the Connectivity Map to link to the Web Service External Application. Because there is only one partner for all operations, you need to use an event-based decision with each path of the decision implementing a different operation from the WSD object. The operation that is used during runtime is based on the type of request received.

22. User activities are unique Business Process activities in that they require human input

at specific points in the Business Process. They are the primary component for incorporating human workflows into Business Processes. Human workflows make it possible to deploy complex Business Processes that include human interaction with and management of distributed information systems. Task assignment allows you to set up and view tasks depending on your organizational role. With certain management level rights, you can assign a person to receive a task if an activity fails. User activities are used in conjunction with an eVision page flow and the Worklist Manager (WLM). The page flow provides a point of access to the Business Process through a web page where a user can enter the requested data. The Worklist Manager is used to assign and tasks and monitor task assignments and status.

23. When you create a sub-process, you must also create a partner to associate with the receive and reply activities. This partner appears in the Implemented Services panel for the sub-process, and is linked to the sub-process in the Invoked Services panel of the main Business Process.

24. The Worklist Manager is a web-based interface that allows you to view, assign, escalate, and execute the tasks generated from user activities. The functions that can be performed in the Worklist Manager are based on user hierarchy. eInsight BPM supports the definition of organization hierarchies and user roles for task assignment. Tasks can be escalated and delegated by users from custom worklists and activity processing windows. The Worklist Manager requires an LDAP directory to define users, their roles, and their hierarchy. 25. An LDAP-based application can be used to populate the Worklist Manager with members of your organization and their organizational roles. You assign rights based on organizational role assignments. 26. The Worklist Manager and task assignment window support the following LDAP servers: a. Sun Java™ System Directory Server, version 5.1 and 5.2

b.

Microsoft Active Directory (the version delivered with Windows 2003)

c.

OpenLDAP Directory Server 2.x or 3.x

27. By default, communications between the Repository and the LDAP server are

unencrypted. You can configure the LDAP server and Worklist Manager to use Secure Sockets Layer (SSL).

28. Flex attributes are customizable attributes that aid in task assignment.

29. In eInsight BPM, exception handling allows one or more components to throw an exception that is caught by eInsight BPM within a scope or at the process-level. A scope allows you to define a range for handling exceptions, which can span one or more activities in the Business Process. When the exception handler is not attached to a scope, exception handling is at the process level.

30. The Scope element allows you to apply exception handling to a set of sequential or

simultaneous steps in a Business Process. Using a Scope element, you can assign a compensation handler, event handlers, and fault handlers to a portion of a Business Process.

31. Exception handlers for parent scopes invoke the correct compensation handlers in the

appropriate order. The entire Business Process exists as a scope. This allows a user to create a single scope within a Business Process and design a compensation handler for that scope. In this case, you drop the exception handler at the Business Process level.

32. You can import code based on BPEL4WS version 1.0 or 1.1, but eInsight BPM only supports BPEL4WS 1.0. When you import from version 1.1, some code might be retrograded to version 1.0, which might require some extra steps.

33. In the Business Process properties, set the Persistence for Reporting property to yes, if you want to monitor business process through enterprise manager. You must also run the DB scripts. 34. If you have modified your business process and you want to monitor it correctly further also then do the following steps: a. Save all changes. b. Check in the Business Process. c. Check out the Business Process. d. Run the database script again for the Business Process. e. Open the Deployment Profile, and rebuild and redeploy the Project. 35. Basically for monitoring business processes we need to register each component of business process with business process monitor so we do check in, check out, rerunning of DB script, rebuild & redeploy (If you import a project then do the above step for all components).

36. When we say we are monitoring BP we mean to say we are monitoring BPI. We can filter the list of Business Process instances in order to see only Business Process instances that meet a specific set of criteria.

37. Before you can invoke the eInsight Business Process Debugger, i.e. in the Enterprise

Explorer, right-click the application or integration server & click Business Process Debugge, you must enable the debug property in the eInsight Engine Configuration properties.

38. The Business Process Instance Manager (BPIM) API provides methods for interacting

with deployed Business Processes using a custom application, similar to monitoring the Business Processes in Enterprise Manager. The BPIM API contains one class,

BPInstanceManager that encapsulates all the required methods to access and manage Business Process instances. BPInstanceManager is instantiated with the hostname, administrative port, username, password, and the name of the deployed .ear file containing the Business Processes to monitor. 39. If you do not want to use the default Worklist Manager interface provided with eInsight BPM, you can use the Workflow Service (WFS) API to create a custom interface with your own look and feel.