Chapter 2 Getting Started

Transcription

1 Chapter 2 Getting Started Process Commander is a business process management solution that combines a patented enterprise rules engine with tools for developing, deploying, and evolving enterprise-wide business applications. Process Commander automates both the business decisions and the processes that drive work to completion. Your developers use Process Commander both to build standalone applications and to integrate Process Commander applications with your existing legacy systems. As an administrator, you maintain all the components of your Process Commander system the development system and the production system, both of which may be configured as multinode (clustered) systems. This chapter describes the first steps to take with your Process Commander system and describes the system s initial state. It contains the following sections: First Steps Default State of Process Commander After Installation

2 2-2 Administration and Security Getting Started First Steps Before you begin working with Process Commander, it is a good idea to familiarize yourself with Process Commander terms and concepts. If you have not yet attended training, read the Quick Start Tutorial and skim the overview sections of Designing Your Applications with SmartBuild. Additionally, Appendix A of this document provides a glossary of terms. During the installation, the installers used a setup tool that created the subset of organizational components necessary for you to begin working with the system immediately. Before you begin, ask the installers what name they specified as the name of your organization during the installation. That name was used as the basis for all the generated components Starting and Stopping the System As with any Web or enterprise application deployed in an application server, you start and stop Process Commander using the procedure determined by the application server software. If Process Commander is running in WebSphere or WebLogic, use the application server s administrator console to start and stop Process Commander. If Process Commander is running in Tomcat, use the startup and shutdown.sh or.bat files located in the bin directory of the Tomcat installation directory to start and stop Process Commander. Logging In and Logging Off You access the Process Commander user interface through a browser. The main Process Commander servlet that provides the interface is called PRServlet. To log in, navigate to the following URL:

3 Getting Started First Steps 2-3 Where: context_root is the name of the deployed Process Commander Web application, typically prweb servername is the name of the server it is running on portnumber is the port number the application server uses for the Process Commander application; typically 9080 for WebSphere, 7001 for WebLogic, and 8080 for Tomcat For example: For access to the administrator features, you need administrator access rights: you need the SysAdmin access role and the Developer portal assigned to your access group. These terms are defined in the Access Rights chapter of this document. For now, log in as one of the default administrator users created during the installation process (Figure 2-1). Administrator User Name where MyOrg is the name the installers specified as the name of your organization Password rules Install Figure 2-1. Default Administrator Users When you log in for the first time, the Welcome window appears (Figure 2-2).

4 2-4 Administration and Security Getting Started Figure 2-2. Process Commander Welcome Window Click the Close button and the Process Commander developer home page appears (Figure 2-3). Figure 2-3. Process Commander Developer Portal

5 Getting Started First Steps 2-5 When you log in or use certain system features for the first time, your system downloads ActiveX components, and you may see a Security Warning window. Click Yes to download the Pegasystems components. To log off, click the Log off link in the upper right of the main workspace. Change the Passwords Several default users (operator ID records) were created for your Process Commander system during installation. The best practice is to change their passwords immediately. Figure 2-4 lists all the users (Data-Admin-Operator-ID) created during the installation, where MyOrg is the name specified for your organization. User Name Administrator@pega.com Administrator@MyOrg.com ProcessArchitect@MyOrg.com SystemArchitect@MyOrg.com WorkManager@MyOrg.com WorkUser@MyOrg.com Password install rules rules rules rules rules Figure 2-4. Default Users To change the passwords for these six users, complete the following steps: 1. Choose View > Organization > Operators from the menu. The Operators list appears. 2. Click the name of the Administrator@MyOrg.com operator. The Operator ID form for that user appears. 3. Select the Security tab (Figure 2-5).

6 2-6 Administration and Security Getting Started Figure 2-5. Security Tab on Operator ID Form 4. Click in the Password field and enter the new password. 5. Click Save (in the toolbar), and then click Close. 6. Back in the Operators list, complete steps 2 through 5 for the other five users, including the Administrator@pega.com user. Verify That the Help System Is Installed The Application Developer Help system is packaged as a separate Web application that should have been deployed during the installation of your Process Commander system. To verify that the Help application is installed and Process Commander is configured to locate it, choose Help > Process Commander Help from the menu. If the Help system does not appear in a second browser window, ask the installers whether they installed it and verify that the URL for it is correct.

7 Getting Started First Steps 2-7 The URL of the Help system is contained in a system setting called ProComHelpURI. From the Rules by Type explorer tab in the navigation panel, choose System > Dynamic System Settings. Then select ProComHelpURI from the list of settings to examine the URL (Figure 2-6). Figure 2-6. ProComHelpURI Setting If the Help system was not installed, locate the installation media and the Installation Guide and install it now. Verify That the System Management Application Is Installed Process Commander is instrumented with JMX mbeans that provide information about the way the system is running. The System Management application is a separate Web application that provides an interface to the Process Commander mbeans. The System Management application should have been deployed during the installation of your Process Commander system; just one System Management application is necessary no matter how many Process Commander nodes are running in your system. To verify that the System Management application is installed and Process Commander is configured to locate it, choose Tools > System Management Application from the menu. If the System Management application does not appear in a second browser window, ask the installers whether they installed it and verify that the URL for it is correct.

8 2-8 Administration and Security Getting Started The URL of the System Management application is contained in a system setting called SystemManagementURI. From the Rules by Type explorer tree in the navigation panel, choose System > Dynamic System Settings. Then select SystemManagementURI from the list of settings to examine the URL. Figure 2-7. SystemManagementURI Setting If the System Management application was not installed, locate the installation media and the Installation Guide and install it now.

9 Getting Started Default State of Process Commander After Installation 2-9 Default State of Process Commander After Installation Process Commander uses constructs called rules and classes to support various features, functions, and processes. Instances of classes are stored as objects (records) in the PegaRULES database. Data objects and rules are the instances that store the configuration information and the processing logic for the applications you design. Work objects are the instances that store work. When you first log in to Process Commander, two organizational structures with users and access groups assigned to those users exist: your organization and the pega organization. These structures give you and the developers a place to start. You create additional items to supplement the starting structure of your organization. Generated Components for Your Organization Structure The following components were created during the installation. Their names are based on the name specified for your organization: One organization (Data-Admin-Organization), with the name specified as the name for your organization during the installation with the suffix.com appended; for example, MyOrg.com One division (Data-Admin-OrgDivision), named with the word Div appended to the name specified for your organization; for example MyOrgDiv. One unit (Data-Admin-OrgUnit), named with the word Unit appended to the name of your organization; for example, MyOrgUnit. One abstract class rule (Rule-Obj-Class) that has the same name as the organization, for example, MyOrg- One workgroup (Data-Admin-WorkGroup) named default; for example, default@myorg.com. One workbasket (Data-Admin-WorkBasket) named default; for example, default@myorg.com One RuleSet (Rule-RuleSet-Name) that has the same name as the organization, for example, MyOrg

10 2-10 Administration and Security Getting Started One RuleSet version (Rule-RuleSet-Version), set to One application rule (Rule-Application), with the same name as the organization and with its version number set to Five access groups (Data-Admin-Operator-AccessGroup) named as follows: MyOrg:Administrators MyOrg:ProcessArchitects MyOrg:SystemArchitects MyOrg:WorkManagers MyOrg:WorkUsers where MyOrg is the name specified for your organization during the installation. Five users (Data-Admin-Operator-ID) with passwords set to rules and named as follows: where MyOrg is the name specified as your organization during the installation. With these pieces in place, you and your developers can run the Application Accelerator. The Application Accelerator creates the basic structure of an application, for example, RuleSets, class rules, class groups, properties, flows, flow actions, and work parties. Then the developers fine-tune the generated rules and build the rest of the application.

11 Getting Started Default State of Process Commander After Installation 2-11 The Pega Organizational Structure There are also several Pega organizational elements present on every Process Commander system. Important: Certain background processes and agents rely on these items. Do not delete any of components in the following list. One organization (Data-Admin-Organization) named pega.com One division (Data-Admin-OrgDivision) named Administration One unit (Data-Admin-OrgUnit) named Installation One workgroup (Data-Admin-WorkGroup) named Default Several workbaskets (Data-Admin-WorkBasket) that support the standard flows One application rule (Rule-Application) named PegaRULES Eight access groups (Data-Admin-Operator-AccessGroup) named as follows: PegaRULES:Administrators PegaRULES:Agents PegaRULES:PortalUsers PegaRULES:ProcessArchitects PegaRULES:SystemArchitects PegaRULES:Unauthenticated PegaRULES:WorkManagers PegaRULES:WorkUsers Four users (Data-Admin-Operator-ID) named as follows: External

12 2-12 Administration and Security Getting Started Process Commander Explorers The Process Commander user interface has two main sections: a navigation panel on the left and a workspace on the right (see Figure 2-3). You use the explorers, located in the navigation panel, to find the rules and data objects that you must create and modify as the system administrator. Four explorers are available, each under its own tab: The Application Explorer provides access to the rules that belong to a single, selected application s RuleSets. The Used by Application Explorer provides access to the rules in the current application plus any rules from other RuleSets that are referenced in the application. The Class Explorer provides access to all the base, rule, data, and work classes present in the PegaRULES database. The Rules by Type Explorer provides access to most of the rules and data instances by their categories. The procedures in this book assume you are using the Rules by Type Explorer (Figure 2-8). Figure 2-8. Rules by Type Explorer Tip: You can configure which of the explorers appears in the navigation panel. From the menu, select Edit > Preferences. In the Preferences window, select View and then specify which tabs you want to see in the navigation panel.

13 Getting Started Default State of Process Commander After Installation 2-13 Base Classes Rules and classes support various features, functions, and processes. All rule, data, and work objects are instances of classes, and all classes inherit either directly or through pattern inheritance from one of the base classes. When an object is created, it is stored as a page and the values for its properties are stored as property-name value pairs in server memory. Pages and their values are displayed on the Process Commander clipboard (Tools > Clipboard), which is separate from the operating system clipboard. Figure 2-9 lists the standard base classes with brief descriptions of their main purpose. Base Class Assign- Code- Data- Embed- History- Index- Description The top class in the hierarchy. All other classes inherit from it. Implements the concept of assignments, each identifying a step in a workflow that requires human input or work by an outside organization, person, or system. Classes that directly reference server program code. Pages belonging to classes derived from the Code- base class exist only temporarily, in memory, and are not saved in the PegaRULES database. Reference data for application processing, including data for system and user administration. Pages embedded within other pages. Pages belonging to the classes derived from the Embed- base class can be saved only as part of other pages. A class whose instances record the change history of the objects in your application, including rules, work, and data. Implements the declarative indexing feature.

14 2-14 Administration and Security Getting Started Base Class Name Link- Log- PegaAccel PegaSample Rule- System- Work- Description Instances that record associations between linked or attached objects. Records of system events. Supports the Application Accelerator. Supports the PegaSample sample application. Business rules defining applications built with Process Commander. Operational status information Work-related data structures, including work objects, covers, and folders Figure 2-9. Base Class Names and Descriptions