BEA WebLogic Server, Руководство пользователя

Страница: 182 / 294

Usage Considerations
8-18 BEA Systems, Inc.
In this scenario, because you are using the same SAP program ID, SAP sends event data to
all events configured with that program ID. BEA WebLogic creates separate schema for each
event (because configuration parameter(s) differ) and then binds a specific event channel
to that event schema. The result is that only events that match that schema are sent over a
specific channel. While SAP is sending event data to every event configured with the same
program ID, BEA WebLogic, as it validates schemas, rejects any event data that does not
match the schema for that channel.
For example, only Doc. A events that appear on the first channel are received, and Doc. B
events that appear on the second channel are received. Doc. B events that appear on the
first channel are rejected, because they do not pass schema type validation. The same result
occurs for Doc. A events that appear on the second channel.
This usage consideration applies to all supported platforms.
Workaround
If you wish to load balance SAP event data over multiple events in BEA WebLogic, ensure
you configure each event in precisely the same way.
If you do not wish to use load balancing, configure a separate event for each SAP program
ID. Also, ensure that no other event configured in an Application View or in another BEA
application uses the same program ID.