IBM E02HRLL-G - WebSphere Partner Gateway Express, Руководство администратора

Страница: 40 / 268

Managing event delivery
About this task
With WebSphere Partner Gateway, you can choose to publish system-generated
events to an application (for example, a monitoring application). You publish these
events to a JMS queue. From the Event Publishing Properties page, you can view
the status of event publishing and the associated JMS configuration (if one exists),
or you can change the status.
Note: On some Windows versions (prior to XP), you might have to change the
default values of the JMS Queue Factory Name and the JMS Queue Name if you
want to use the default Event Delivery feature. You must change the value for JMS
Queue Factory Name from
WBIC/QCF
to
WBIC\\QCF
and the value for JMS Queue
Name from
jms/bcg/queue/deliveryQ
to
jms\\bcg\\queue\\deliveryQ
.
To activate event publishing, follow these steps:
1. Click System Administration > Event Processing > Event Delivery
Information .
2. In the Event Publishing Properties window, click the Edit icon next to Enable
Event Publication . Then enter or change the values for the JMS properties.
See the WebSphere Partner Gateway Hub Configuration Guide for the property
descriptions.
3.
Click
Save
.
Managing API calls
About this task
Partners can make application programming interface (API) calls (instead of using
the Community Console) to perform certain tasks.
To change the setting of the administration API, follow these steps:
1. Click System Administration > Feature Administration > Administration API .
2.
On the Administration API Properties window, click the
Edit
icon next to
Enable the XML Based API
.
3. Select the check box to enable the use of the API, or clear the check box to
disable the use of the API.
4.
Click Save .
Note: The XML-based administrative API is deprecated.
The migration utility that is introduced by WebSphere Partner Gateway can be
used instead of the administrative API to perform the creation and update tasks.
Creation and update tasks formerly only performed using the administrative API
can now be performed by using a migration import file that has the new or
updated information.
The import file is described by the XML schema that is provided with the
migration utility. You can use a development tool such as Rational Application
Developer to produce an import XML file that conforms to the schema. By
importing this file with the migration utility, you can load new partner definitions
including contacts and business IDs for the partners. You can also update existing
partner definitions by importing them with the migration utility. With the
34
IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide