PeopleTools 8.51 PeopleBook: PeopleSoft Integration Broker Administration

Configuring PeopleSoft Integration Broker for Handling Services

This section discusses how to configure PeopleSoft Integration Broker for handling services.

Understanding Configuring PeopleSoft Integration Broker for Handling Services

This section provides an overview of several of the service configuration properties that you must set to use services with PeopleSoft Integration Broker.

Namespaces

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.

Target Locations

Target locations are URLs that PeopleSoft Integration Broker uses to build and validate XML message schemas, export WSDL documents, and as the SOAP endpoint.

PeopleSoft Integration Broker enables you to define two target location URLs, and provides a Target Location field and Secure Target Location field on the Service Configuration page.

The URL you enter in the Target Location field should be an unsecured URL. By default, the system uses this URL to build and validate XML message schemas, export WSDL documents, and as the SOAP endpoint.

Note. XML schema validation will fail if you enter a secured URL in the Target Location field.

If you need to use a secure URL for the SOAP endpoint, enter a secure URL in the Secure Target Location field. Any URL you enter in the Secure Target Location field overrides the URL entered in the Target Location field for the SOAP endpoint.

In addition, you can override the (unsecured) target location URL for exporting WSDL documents on a case–by–case basis. The Provide Web Service wizard features a Use Secure Target Location box in Step 2 – Select Service Operations of the Wizard. If you select the box, the system exports the WSDL document to the URL specified in the Secure Target Location field on the Service Configuration page. The override is in effect only for that particular export of WSDL. If you need to generate WSDL again for the service, the system defaults back to using the (unsecured) target location URL, unless you again check the Use Secure Target Location box in the wizard to override the URL to use the secure target location.

To use services with PeopleSoft Integration Broker, you must specify a target location. Specifying a secure target location is optional.

Service System Status

The Services Configuration page contains a Service System Status drop-down 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 drop-down 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 service operations that are associated to services that have WSDL provided. You must delete the WSDL before you can delete the service operation. If you delete the default service operation version, all versions of the service operation are deleted. 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.

Setting Service Configuration Properties

This section discusses how to set service configuration properties.

You set service configuration properties on the Service Configuration page (IB_SVCSETUP) 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 (PeopleTools, Integration Broker, Services Configuration).
In the Service Namespace field, declare a service namespace.
In the Schema Namespace field, declare a schema namespace.
In the Target Location field, enter an unsecured URL to be used for XML message schema, WSDL, and as the SOAP endpoint.

If you enter a secure URL in the Target Location field, XML message schema validation will fail.

If you require a secure target location for the SOAP endpoint, see Step 5.

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 location URL format: .
```
http://<machine>:<port>/PSIGW/PeopleSoftServiceListeningConnector/<defaultlocalnode>
```
(Optional) In the Secure Target Location field, enter a secure URL to be used as the SOAP endpoint.

The URL entered here overrides the target location defined in Step 4 for the target location for the SOAP endpoint.

The URL you enter here is also used as a secure target location for exporting WSDL, if you choose the Use Secure Target Location box in the Provide Web Service wizard.

If you do not enter a value in this field, the system uses the unsecured URL that you specify in the Target Location field for both the SOAP endpoint and for exporting WSDL.

See Step 2: Select Service Operations.

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, use the alternate location URL format:
```
http://<machine>:<port>/PSIGW/PeopleSoftServiceListeningConnector/<defaultlocalnode>
```
From the Service System Status drop-down list box, select one of the following options:
- Development. (Default.)
- Production.
These statuses are discussed elsewhere in this chapter

See Understanding Configuring PeopleSoft Integration Broker for Handling Services.
(Optional) Check the Enable Multi-queue box to use multiple queues to process inbound and outbound asynchronous requests.

This feature is discussed elsewhere in PeopleBooks.

See Assigning Multiple Queues to Process Service Operations.
From the WSDL Generation Alias Check drop-down list, select an option for enforcing field and record alias names in generated WSDL.

This feature is discussed elsewhere in PeopleBooks.

See Enforcing Message Record and Field Aliases in Generated WSDL.
Click the Save button.