Business activity support provides compensation for activities
such as sending an email, which can be difficult or impossible to
roll back atomically. With this compensation, applications on disparate
systems can coordinate activities that are more loosely coupled than
atomic transactions. To use the business activity support, you must
first enable it on each server that you plan to use.
About this task
If an application component uses business activity support,
you must enable the support on each server that runs the application.
Note: 這個主題參照一或多個應用程式伺服器日誌檔。
此外,在分散式和 IBM® i 系統上,另外也建議您可以配置伺服器來使用「高效能可延伸記載 (HPEL)」日誌和追蹤基礎架構,而不使用 SystemOut.log、SystemErr.log, trace.log 及 activity.log 檔案。HPEL 與原生 z/OS® 記載機能也可以一起使用。如果您使用 HPEL,則可以從伺服器設定檔 bin 目錄,利用 LogViewer 指令行工具來存取您所有的日誌和追蹤資訊。請參閱有關利用 HPEL 疑難排解應用程式的資訊,以取得更多使用 HPEL 的相關資訊。
Procedure
- In the administrative console, click .
- Select the Enable service at server startup check
box.
- To change the directory in which compensation
logs are written, type the full path name of the directory in the Recovery
log directory field. For a high availability
(HA) environment, you must change the compensation log directory so
that each server in the cluster has a unique compensation log directory.
When
you use WebSphere® Application Server without high
availability support, you do not need to set the recovery log configuration
for persistent services such as the compensation service. The application
server assumes a default location in the appropriate profile directory.
When high availability support is enabled, this default location might
not be visible from all servers in the cluster (for example, if the
servers are in different profiles or physical nodes.) Because of this
behavior, configure the recovery log directory for each server in
the cluster before enabling high availability. Each server in the
cluster must have a unique compensation and transaction log directory,
so that multiple servers do not attempt to access the same log file.
Also, each server in the cluster must be able to access the transaction
and compensation log directories of the other servers in the cluster.
- If required, modify the compensation handler retry interval
and limit. These values control the frequency with which
the compensation handler compensate and close methods are retried, when either throw
a RetryCompensationHandlerException exception,
and the number of times that these methods are retried.
- Save your changes to the master configuration.
- Repeat the previous steps for each server that you plan
to use.
- Restart all the servers for the changes to take effect.
Results
The business activity support is enabled for the application
server. Verify a successful enablement by checking for the message,
CWSCP0005I:
The Compensation service started successfully. in the
SystemOut.log file
for the relevant server.
Note: 這個主題參照一或多個應用程式伺服器日誌檔。
此外,在分散式和 IBM i 系統上,另外也建議您可以配置伺服器來使用「高效能可延伸記載 (HPEL)」日誌和追蹤基礎架構,而不使用 SystemOut.log、SystemErr.log, trace.log 及 activity.log 檔案。HPEL 與原生 z/OS 記載機能也可以一起使用。如果您使用 HPEL,則可以從伺服器設定檔 bin 目錄,利用 LogViewer 指令行工具來存取您所有的日誌和追蹤資訊。請參閱有關利用 HPEL 疑難排解應用程式的資訊,以取得更多使用 HPEL 的相關資訊。
What to do next
Deploy the business-activity-enabled application to the server.
Note: Applications can exploit the business activity support only if you
deploy them to a WebSphere Application Server at
Version 6.1 or later. Applications cannot use the business activity
support if you deploy them to a cluster that includes WebSphere Application ServerVersion 6.0.x servers.