For information about process-specific messages, tracing, and audit
trails, see Troubleshooting Business Process
Choreographer. Here are some things to check if you have problems getting
the business process container to work:
If tables or views cannot be found in the database. When
configuring the authentication alias for the data source, you must specify
the same user ID that was used to create the database (or to run the scripts
to create it).
If you get a database error when installing an enterprise application
that contains a process. When an enterprise application is installed,
any process templates are written into the Business Process Choreographer
database. Make sure that the database system used by the business process
container is running and accessible.
If you cannot invoke Cloudscape™ tools. Make
sure that you have set up the Java™ environment, and have included the
necessary JAR files in the classpath environment variable.
If you have problems using national characters. Make
sure that your database was created with support for Unicode character sets.
If you have problems creating the queues using WebSphere® MQ: WebSphere MQ dll not found. Add the WebSphere MQ Java lib
directory to your path environment variable. For example, on Windows®,
enter the command:
set path=MQInstallationDirectory\java\lib;%path%
where MQInstallationDirectory is
the installation directory for WebSphere MQ.
If you do not want to have to stop the whole application server just
to be able to stop a local WebSphere MQ queue manager on Windows, UNIX®,
and Linux® platforms: Change the Transport Type from 'bindings' to 'client'. Compared to using
local bindings, the extra overheads associated with using the client transport
type will reduce the maximum workload throughput by approximately 5%.
Problem on AIX® connecting
to the queue manager. Edit the file /var/mqm/mqs.ini,
and add one of the following properties to the definition for your queue manager:
IPCCBaseAddress=12
IPCCBaseAddress=4
If restarting the business process container causes a Web client to throw
an exception. The Web client is using local bindings, and must
also be restarted.
To avoid deadlocks, make sure your DB2® system is configured to use sufficient
memory, especially for the bufferpool. Use the DB2 Configuration Advisor to determine reasonable
values for your configuration.
If Sybase reports the exception: The 'ALTER TABLE' command is not
allowed within a multi-statement transaction in the 'databaseName'
database. This can happen after you have installed a new PTF
level that requires the database to be migrated. Start the Sybase isql command
program, enter the following commands:
use master
go
sp_dboption databaseName, "ddl in tran", true
go
where databaseName is the name of your database.
If you installed a process application on a cluster, but get errors relating
to the data source. This can happen if the application was generated
to run on a single server, which makes it expect the default data source BPEDB.
In this case, change the data source for the application to BPEDB_cluster_name,
where cluster_name is the name of the cluster where the application
is installed.