Select a Service Type value: Requestor ABCS, Provider ABCS, Enterprise

2-20 Developers Guide for Oracle Application Integration Architecture Foundation Pack ■ Access the AIA Home page. Click Go in the Project Lifecycle Workbench area. Select the Project tab. Click the project link for the project for which you want to define service solution components. Business tasks assigned to the selected project display on the Business Tasks tab. Locate the business task for which you want to define service solution components. Click the Add Service Solution Component button, as shown in Figure 2–21 . Figure 2–21 Add Service Solution Component Button on the Business Tasks Tab on the Project Tab The Add Service Solution Component page displays as shown in Figure 2–22 . Figure 2–22 Add Service Solution Component Page

2. Select a Service Type value: Requestor ABCS, Provider ABCS, Enterprise

Business Flow , Enterprise Business Service, Composite Business Process, or Others . The actual composite or service that is built from this service solution component definition will inherit the service type value. Developers can override this inherited attribute when working in Service Constructor. For more information, see Chapter 19, Working with Service Constructor. Working with Project Lifecycle Workbench 2-21 For example, selecting a Requestor ABCS service type will result in a requester Application Business Connector Service being queued for construction later in the AIA lifecycle flow. If you select Requestor ABCS or Provider ABCS, an autogenerated globally unique identifier GUID is assigned to the service solution component. The composite built for this service solution component is tagged with the GUID when it is created by the Service Constructor. When the implemented composite is harvested for display in the Oracle Enterprise Repository, the GUID on the composite is used to associate the composite back with its originating service solution component in the Project Lifecycle Workbench. The Product Code field displays. Select the product code that corresponds to the participating application for which the service solution composite is being defined. For example, if you are defining a requester service solution component, the product code that you select should correspond to the requesting participating application. The Deployment Plan Generator uses the product code value in carrying out its logic. For more information about the Deployment Plan Generator, see Chapter 6, Generating Deployment Plans and Deploying Artifacts. Available product code values are derived from the Application Object Library directory names in your source control system. If the required product code is not available, users should be able to contact their system administrator to have a product code added. For more information about making product code values available to the Project Lifecycle Workbench, see Section 2.2.1, How to Add Lookup Values. For more information, see Chapter 19, Working with Service Constructor.

3. In the Name field, enter a descriptive name for the service solution component.