You are on page 1of 3

AT&T Prism End-to-End Demonstration

Requirements by Role Process Server SME Develop a business process that: - includes at least 2 human tasks, in addition to the initialization task - is exposed via web services (SOAP/HTTP) - defines separate roles for the 2 human tasks Using WebSphere Portlet Factory Archive Generator Plug-in, export the human task meta-data and provide to Portal SME. Deploy business process to a WebSphere Process Server instance which is in a separate cell from the Portal server instance. Work with WebSphere Security SME on Process Server items listed in security section. Be able to show that the correct business process is invoked throughout the lifecycle of the business process (i.e. that the correlation mechanism works) Provide example standalone client which can do the same web services calls as demonstrated from the Portal. At a minimum: - instantiate a business process - fulfill a human task - 1-2 HTM tasks (claim tasks, re-assign, etc.) Provide documentation on work done for the demonstration, including best practices for construction of processes using top/bottom, middle, bottom up. Package all collateral into a VMWare image based on a Linux OS with no licensing restrictions. Be prepared to demonstrate not only final working code but also development process used to create code. Portal SME Using the Business Process Integration Extension to Portlet Factory, develop a portlet that, using SOAP/HTTP to Process Server:

instantiates the business process created by the Process Server SME provides UIs for the other 2 human tasks in the business process UIs should use at least 2 different data input types (text box, choice, etc.) UIs will be invoked by different users

Using the Human Task List Application feature set to Portlet Factory, develop a task list management portlet that uses the Process Server HTM web services APIs to: - show the list of tasks assigned to the user - allow a user to claim a task

allow a user to reassign a task allow a user to designate a delegate user for their tasks highlight overdue tasks

Deploy portlets to a WebSphere Portal instance which is in a separate cell from the Process Server instance. Work with WebSphere Security SME on Portal Server items listed in security section. Provide documentation on work done for the demonstration, including best practices for construction of processes using top/bottom, middle, bottom up. Package all collateral into a VMWare image based on a Linux OS with no licensing restrictions. Be prepared to demonstrate not only final working code but also development process used to create code. WebSphere Security SME Provide overall security guidance on demo Confirm/deny need for custom JAAS module in Process Server to accept propagated identity via WS-I Security (identity passed in SOAP header) Assist the Process Server SME in: - configuring process server to use the file-based registry - configuring process server users/roles and assignment to the proper human task items - configuring process server to accept propagated identity via WS-I security for all in-bound web services calls Assist the Portal SME in: - configuring portal server to use the file-based registry - configuring portal server users/roles and assignment to the proper UI elements - configuring portal server to send propagated identity via WS-I security on outbound calls

AT&T Original Requirements 1. Portal -> WPS A. Portal calls to WPS via soap/HTTP
B. Documentation on best practices for construction of the demonstration top/bottom, middle, bottom up. C. Building the web service calls to do the following: 2. A web svcs call to initiate or instantiate the Business Process 3. Make several WS calls to various workflow tasks within the BP.

4. At least two simultaneous users are involved in the workflow 5. Proof that the correct instantiated BP is used throughout the life cycle of the BP by whatever correlation mechanism is in place. 6. An example standalone client which can do the same WS calls as what is demonstrated from Portal. Include work list display

Include ability to work 2+ human tasks with multiple fields (choice, text, etc). This would be in addition to the initialization task. Ability to reassign task Include role level security Application must have 2+ roles Human task are worked/owned by separate and distinct roles Highlight tasks overdue ability to for delegate to work task instance
Use the file based registry Portal Server and Process Sever in seperate jvm's, each in its own cell Portal using its own local authentication tooling Calls from Portal to Process Server via SOAP only (HTTP is fine) Process Server with tasks and workflow that uses roles defined in the user registry Portal Server passing identity to Process Server using WS-I Security (identity in the SOAP Header) Portlets created with Portlet Factory for Web Services Package PRISM ETED (End To End Demo) in a working copy of RSA/WID/PortletFactory in a VM (Fedora is fine) and deliver to AT&T electronically so we have a working copy of the PRISM ETED with source.

You might also like