This chapter provides an overview of managing services and discusses how to:
Configure PeopleSoft Integration Broker for handling services.
Specify UDDI repositories in the PeopleSoft system.
Access and view service definitions.
Add service definitions.
Configure service definitions.
Restrict write access to services.
Rename and delete services.
Services are used to logically group a set of service operations.
For example, if you have a number of service operations that are related to customers, such as those pertaining to customer information, adding customers, updating customers, deleting customers, and so on, you can create a customer web service and then associate the related service operations with that service.
Warning! PeopleSoft delivers two services with PeopleSoft Integration Broker: IB_GENERIC and IB_UTILITY. These services are used internally by the system. Do not delete or modify these services.
Comments |
(Optional.) Enter comments about the service or service definition. |
Description |
Description of the service. |
Generate SOAP Template |
Click to open the Generate SOAP Template utility. The utility enables you to generate SOAP documents for each service operation in a service for testing purposes. |
Object Owner ID |
(Optional.) Indicates the owner of the service. The owner ID helps to determine the application team that last made a change to a service definition. The values in the dropdown list box are translate table values that you can define in the OBJECTOWNERID field record. |
Operation Type |
Specifies how the service is transmitted. On the Service page this field defines the operation type of the service operation added. |
Provide Web Service |
Click to launch the Provide Web Services component and export PeopleSoft services as WSDL documents. |
Schema Namespace |
Provides qualification for attributes and elements within an XML schema document (XSD). The default is http://xmlns.oracle.com/Enterprise/Tools/schemas. The namespace on the message definition defaults to the schema namespace you set as the default on the Service Configuration page. Note. If you change the namespace, all future messages will have the new namespace. |
Service |
The name of the service. |
Service Alias |
(Optional.) Overrides the service name and will be the name of the service when the WSDL is provided or exported. The alias enables you to use mixed case in the name. |
Service Operation |
The name of the service operation that is associated with the service. On the Services page, use this field to add new service operations for the current service. |
Service NamespaceandNamespace |
The service namespace field in the Service Configuration page used to default the service namespace field when defining PeopleSoft services. The default value is http://xmln.oracle.com/enterprise/tools/service. The namespace field on the Service pages provides qualification for attributes and elements within a WSDL document. |
Service System Status |
The status that is selected restricts rename, delete, and other administrative actions that users can perform on integration metadata in the Services Administration component. Values are:
See Understanding Configuring PeopleSoft Integration Broker for Handling Services. |
Target Location |
Specifies the URL to be used for service requests. You must define this location before creating services and service schemas. |
View WSDL |
Click to view WSDL documents that were generated for the service in the WSDL repository. |
Before you can work with services in PeopleSoft Integration Broker, you must set several configuration properties.
This section provides an overview of configuring PeopleSoft Integration Broker for handling services and discusses how to set service configuration properties.
This section provides an overview of several of the service configuration properties that you must set to use services with PeopleSoft Integration Broker.
Namespaces provide a method for qualifying element and attribute names that are used in XML documents and are identified by Uniform Resource Identifier (URI) references.
To use services with PeopleSoft Integration Broker, you must specify a service namespace and a schema namespace.
The Services Configuration page contains a Service System Status dropdown list box that enables you to restrict rename, delete, and other administrative actions that users can perform on services, service operations, messages, and other integration metadata.
You can select one of two values from the dropdown list box: Production or Development.
The following table describes the impact of the setting on managing integration metadata:
Object |
Action |
Production Mode |
Development Mode |
Messages |
Rename |
You cannot rename a message that is associated to a service that has WSDL provided. You must first delete the WSDL documents before you can rename the message. |
An alert message displays indicating that WSDL documents have been provided for the service to which the message is associated, but you may continue with the action and rename the message. |
Messages |
Delete |
You cannot delete a message that is associated to a service that has WSDL provided. You must first delete the WSDL documents before you can delete the message. |
An alert message displays indicating that WSDL documents have been provided for the service to which the message is associated, but you may continue with the action and delete the message. |
Message Schemas |
Delete |
You cannot delete a message schemas that is associated to a service that has WSDL provided. You must first delete any WSDL documents before you can rename the schema. |
An alert message displays indicating that WSDL documents have been provided for the service to which the message schema is associated, but you may continue with the action and rename the schema |
Queues |
Rename |
The Service System Status has no impact on renaming queue definitions. However, you cannot rename a queue if it is referenced in a service operation or if it is referenced in the runtime tables. |
The information that applies to renaming queues in production mode also applies to renaming queues in development mode. |
Queues |
Delete |
The Service System Status has no impact on deleting queue definitions. However, you cannot delete a queue if it is referenced in a service operations or if it is referenced in a runtime table. |
The information that applies to deleting queues in production mode also applies to deleting queues in development mode. |
Routings |
Rename |
The Service System Status has no impact on renaming routing definitions. |
The information that applies to renaming routing definitions in production mode also applies to renaming routings in development mode. |
Routings |
Delete |
You cannot delete an any-to-local routing definition that is tied to a service that has WSDL provided. You must first delete the WSDL from the service before deleting the routing definition. |
An alert message displays indicating that WSDL documents have been provided for the service to which the routing is associated, but you may continue with the action and delete the routing definition. |
Service |
Rename |
You cannot rename services that have had WSDL documents provided. The WSDL documents must be deleted before you can rename a service. |
An alert message displays indicating that WSDL documents have been provided for the service, but you can continue with the action and rename the service. |
Service |
Delete |
The Service System Status has no impact on deleting services. However, you cannot delete any service that is referenced by a service operation. |
The information that applies to deleting services in production mode also applies to deleting services in development mode. |
Service Operation |
Rename |
You cannot rename service operations that are associated to services that have WSDL provided. You must delete the WSDL before you can rename the service operation. |
An alert message displays indicating that WSDL documents have been provided for the associated service, but you may continue with the action and rename the service operation. |
Service Operation |
Delete |
You cannot delete a service operation that is referenced in the runtime tables. |
An alert message displays indicating that WSDL documents have been provided for the associated service, but you may continue with the action and delete the service operation. You cannot delete a service operation that is referenced in the runtime tables. |
Service Operation |
Change Service |
You cannot change a service operation that is associated to a service that has WSDL provided. You must first delete the WSDL documents before you can modify the setting. The new service to which you associate an operation may have had WSDL generated. However, if you want the WSDL from the newly associated service operation to be included in the WSDL document, you must export the service again. |
An alert message displays indicating that WSDL documents have been provided for the associated service, but you may continue with the action and change the service associated with the service operation. The new service to which you associate an operation may have had WSDL generated. However, if you want the WSDL from the newly associated service operation to be included in the WSDL document, you must export the service again. |
Page Name |
Object Name |
Navigation |
Usage |
Service Configuration page |
IB_SVCSETUP |
Select PeopleTools, Integration Broker, Integration Setup, Service Configuration. |
Use this page to configure PeopleSoft Integration Broker for handling services. |
You set service configuration properties on the Service Configuration page in the Services Configuration component (IB_SVCSETUP). To access this page, select PeopleTools, Integration Broker, Services Configuration. The following example shows the Service Configuration page:
To set service configuration properties:
Access the Service Configuration Properties page.
In the Service Namespace field, declare a service namespace.
In the Schema Namespace field, declare a schema namespace.
In the Target Location field, enter a URL to be used for service requests.
If you have a dedicated integration gateway, the format of the value that you enter is http://<machine>:<port>/PSIGW/PeopleSoftServiceListeningConnector.
If the default local node points to a different gateway server where WSDL documents and XSD schemas are available, use the alternate target location URL format of http://<machine>/PSIGW/PeopleSoftServiceListeningConnector/<defaultnode>.
From the Service System Status dropdown list box, select one of the following options:
Development. (Default.)
Production.
See Understanding Configuring PeopleSoft Integration Broker for Handling Services.
Click the Save button.
This section discusses how to specifying UDDI repositories in the PeopleSoft system for providing and consuming services.
You can provide services to and consume services from one or more UDDI repositories. Before doing so, you must configure each repository in the PeopleSoft system.
Page Name |
Object Name |
Navigation |
Usage |
UDDI Configuration page |
IB_SVCSETUP2 |
Select PeopleTools, Integration Broker, Configuration, Service Configuration. Click the UDDI Configuration tab. |
Configure PeopleSoft Integration Broker to provide services to and consume services from UDDI repositories. |
Use the Service Configuration-UDDI Configuration page to specify UDDI repositories in the PeopleSoft system for providing services to and consuming services from UDDI repositories.
To access this page, select PeopleTools, Integration Broker, Integration Setup, Service Configuration and click the UDDI Configuration tab. The following graphic shows the UDDI Configuration page:
To specify a UDDI repository in the PeopleSoft system:
Access the UDDI Configuration page.
In the UDDI Name field, enter the name of the UDDI server.
In the Description field, enter a descriptive information for the UDDI server.
Specify the URL used when consuming services from UDDI repositories.
In the Inquiry URL field, enter the URL to use to inquire for services available on the UDDI server. This is the URL used when consuming services from UDDI repositories. It is also used when publishing to UDDI repositories to inquire the server for possible existing WSDL document versions.
Click the Ping button next to the Inquiry URL field to verify that you entered the correct URL.
Specify the Publish URL.
In the Publish URL field, enter the URL for publishing WSDL documents to the UDDI server. This URL is used when providing services to UDDI repositories.
Click the Ping button next to the Publish URL field to verify that you entered the correct URL.
To specify additional UDDI repositories to use for providing or consuming services, click the plus (+) button at the top right corner of the UDDI Server section to add a row.
See Also
This section discusses how to.
Access service definitions.
View WSDL documents generated for services.
View service operation information services.
View messages defined for services.
Page Name |
Object Name |
Navigation |
Usage |
Services |
IB_SERVICEDEFN |
Select PeopleTools, Integration Broker, Integration Setup, Services. |
Use this page to:
|
WSDL Repository page |
IB_SERVICEDEFN_SEC |
From the Services page, click the View WSDL link. |
Use this page to view WSDL generated for a service. |
Services-General page |
IB_SERVICE |
From the Service page, click a hyperlinked service operations name. |
View details about the default service operation version defined for a service. |
The following example shows the Services page:
The top of the Service page displays general information about the service, including the name of the service, its description, its alias name, and so on.
Click the View WSDL link to display a page that provides a summary of all the WSDL documents that are generated for the service, as well as the service operations, request messages, response messages, and fault messages that are contained in each.
Note. Service operations must exist for a service to view WSDL documents for the service.
Click the View WSDL link to view the contents of the document.
Click the Return button to return to the Services page.
The Existing Service Operations section of the Services page contains an Operation tab that displays service operations and service operation versions that are associated with the service. It also displays descriptions of the service operations, the type of operation, and whether the service operation is active.
When you click the name of a service operation, the operation opens on the Service Operations page, where you can view and modify service operations information, work with the service operation handlers, routing definitions, and do much more.
See Also
The Existing Service Operations section of the Services page contains a Messages Links tab that displays the request and response messages defined for each service operation.
The following example shows the Message Links tab displaying request and response messages for the service operation that is associated with the QE_FLIGHTPLAN_SYNC service:
Click the request or response message name to open the message in the Message Definitions page, where you can view and modify message definition information, message schema information, and more.
See Also
This section discuses how to add a service definition to the system
Page Name |
Object Name |
Navigation |
Usage |
Services |
IB_SERVICEDEFN |
Select PeopleTools, Integration Broker, Integration Setup, Services. |
Add a service definition to the system. |
To add a service definition to the system, use the Add a New Value tab on the Services search page. To access this page, select PeopleTools, Integration Broker, Integration Setup, Services. Then select the Add a New Value tab.
Note. Before you can add a service, you must configure PeopleSoft Integration Broker to handle services using the Service Configuration page.
To add a service definition:
Access the Services page and select the Add a New Value tab.
In the Service field, enter a name for the service.
Click the Add button.
The Services page appears, and you can now define the service.
See Also
Configuring Service Definitions
Setting Service Configuration Properties
This section discusses how to configure service definitions.
Page Name |
Object Name |
Navigation |
Usage |
Services |
IB_SERVICEDEFN |
Select PeopleTools, Integration Broker, Integration Setup, Services. |
Add a service definition to the system. |
After you add a service definition to the system, the Services page appears and you can configure the service definition.
To configure a service, use the Services page in the Services component (IB_SERVICEDEFN) in the PeopleSoft Pure Internet Architecture. The following example shows the Services page:
To configure a service definition:
If it is not already open, access the Services page.
In the Description field, enter a description for the service.
(Optional.) In the Comments field, enter comments about the service or the service.
(Optional.) In the Service Alias field, enter an alias name for the service.
(Optional.) From the Object Owner ID dropdown list box, select the owner of the service.
Enter a namespace URI for the service.
The default value is the namespace that is declared in the Service Namespace field on the Service Configuration page.
Click the Save button.
You can add service operations to the service definition now or at a later time.
See Also
Setting Service Configuration Properties
This section provides an overview of restricting access to services and discusses how to:
Restrict write access to services.
Enable write access to services.
When you restrict write access to a service, sensitive fields of the service definition and of associated service operations appear in read-only mode. The following table lists the components and pages that contain fields and data that are related to services and describes the impact that restricting access to services has to each of them.
Restricted Component or Page |
Restriction |
Comments |
Service |
All fields are read-only. |
NA |
Service Operation |
All fields are read-only, with the following exceptions:
|
When a service is restricted, you cannot regenerate routings. |
Handlers |
All fields are read-only except.
|
When a service is restricted, you can still activate or inactivate handlers. |
Routings |
All fields are read-only except:
|
When a service is restricted, you can:
|
You cannot delete or rename a restricted service. In addition, you cannot change, rename or delete any service operation that is defined as part of a restricted service.
Page Name |
Object Name |
Navigation |
Usage |
Service Configuration-Restricted Services |
IB_SVCSETUP3 |
Select PeopleTools, Integration Broker, Service Configuration and click the Restrict Services tab. |
Use the page to:
|
The following example shows the Restricted Services page.
To restrict write access to services:
Select PeopleTools, Integration Broker, Service Configuration. Click the Restricted Services tab. The Restricted Services page appears.
In the Service field, enter a service name and click the Search button, or click the Lookup button to search for a service.
The service name or search results display in the Services list.
Check the Restricted Service check box next to the service name to which you want to restrict access.
Click the Save button.
To enable write access to services that you previously restricted:
Select PeopleTools, Integration Broker, Service Configuration. Click the Restricted Services tab.
The Restricted Services page appears.
Select the service to write-enable using one of the following methods:
In the Service field, enter a service name and click the Search button.
Click the Lookup button to search for a service.
Check the Restricted Services check box, and click the Search button to display and select from all currently restricted services in the system.
The service name or search results appear in the Services list.
Clear the check box next to the service name to write access enable.
Click the Save button.
You can rename and delete services using the Services tab in the Service Administration component (IB_HOME_PAGE). The Services tab contains two sections: a Delete section that enables you to delete services and a Rename section that enables you to rename services.
When you first access the Services tab, both sections are collapsed. Click the section header arrow buttons to expand and collapse each section.
The following example shows the Services tab with both Delete and Rename sections expanded.
Page Name |
Object Name |
Navigation |
Usage |
Service Administration-Services page |
IB_HOME_PAGE |
Select PeopleTools, Integration Broker, Service Utilities. Select the Service tab. |
Rename or delete services. |
The service system status that you set on the Services Configuration page affects the ability to rename services.
See Understanding Configuring PeopleSoft Integration Broker for Handling Services, Setting Service Configuration Properties.
To rename a service:
Select PeopleTools, Integration Broker, Service Utilities. Click the Service tab.
The Service page displays.
Click the arrow next to the Rename section header to expand the section.
In the Service field, enter the service to rename, or click the Lookup button to search for and select the service to rename.
In the New Name field, enter the new name for the service.
Click the Rename button.
After you click the Rename button, the Results field displays a message that the action was successful or displays a warning or error message with a description of the problem.
You can delete services only when the service has no service operations associated with it. When you search for a service to delete, only such services that have no service operations associated with them are retrieved from the system.
To delete a service:
Select PeopleTools, Integration Broker, Service Utilities. Click the Service tab.
The Service tab displays.
Click the arrow next to the Delete section header to expand the section.
In the Service field, enter the service name to delete, and click the Search button.
Search results display in the results grid.
In the results grid, check the check box next to the service or services to delete.
Click the Delete button.