To use System Manager for configuration of InterChange Server Express, an
instance of InterChange Server Express must be running and System Manager must
be connected to it.
Do the following to open the InterChange Server Express configuration
editor in System Manager:
- Start System Manager as described in Starting System Manager.
- Connect System Manager to the InterChange Server Express instance as
described in Connecting to InterChange Server Express.
- Right-click the InterChange Server Express instance and choose Edit
Configuration from the context menu.
- Make the desired changes in the configuration tabs as described in the
following sections:
- When you are done use the keyboard shortcut Ctrl+S to save the
file.
The "General" tab of the System Manager configuration file editor
has the following read-only fields:
- The Server name field, which identifies the name of the
InterChange Server Express instance.
- The Server version field, which identifies the version of IBM
WebSphere Integration Server Express software the server is running.
- The Total memory field, which identifies the amount of RAM on
the computer running InterChange Server Express.
- The Free memory field, which identifies the amount of RAM that
is available on the computer running InterChange Server Express.
- The Startup time field, which identifies the time at which the
server instance started.
- The Local Time Zone field, which identifies the time zone in
which the computer running System Manager resides.
- The Server Time Zone field, which identifies the time zone in
which the computer running InterChange Server Express resides.
- The Server locale field, which identifies the locale of the
computer on which InterChange Server Express is running.
The "Database" tab of the configuration file editor allows you to
change properties that specify the databases InterChange Server Express uses
to store repository, event management, and transaction management data.
Do the following to configure the database properties:
- Click the Database tab.
- Select the appropriate value in the Database Driver drop-down
menu--either IBM DB2 Serveror MQ SQL
Server--depending on the database vendor.
- Type the maximum number of connections you want InterChange Server Express
to make with the database server in the Max Connections field, or
enable the Unlimited checkbox to allow InterChange Server Express
an unlimited number of connections.
- Type the maximum number of pools InterChange Server Express should
establish to contain the database connections it caches in the Max
pools field.
- Type the number of minutes you want a connection object to remain idle
before being returned to the database connection pool for reuse in the
Idle Timeout field.
- Type the number of times that the server should
attempt to execute a deadlocked database transaction in the Max deadlock
retry field.
This field is related to the Deadlock retry interval field
documented in step 7.
For more information on the behavior of the server in the case of a
database deadlock, see the System Administration Guide.
- Type the number of seconds that the server should wait
in between attempts to execute a deadlocked database transaction in the
Deadlock retry interval field.
This field is related to the Max deadlock retry field documented
in step 6.
For more information on the behavior of the server in the case of a
database deadlock, see the System Administration Guide.
- Do the following in the "Event Management" pane to configure the
database connectivity for the event management service:
- If you chose MQ SQL Server(Type 4)in the Database
Driver drop-down menu, then type the name of the computer on which the
database server resides in the Host name field.
- Type the name of the database in the Database field.
- Type the maximum number of connections you want InterChange Server Express
to make with the specific database server in the Max Connections
field, or enable the Unlimited checkbox to allow InterChange Server
Express an unlimited number of connections.
- Type the user name that should be used by InterChange Server Express to
log in to the specified database in the Login field.
- Type the password for the user name in the password
field.
- If you chose MQ SQL Server(Type 4), or Oracle(Type
4) in the Database Driver drop-down menu, then you must type
the port number through which clients communicate with the database server in
the Port Number field.
- Repeat step 8 in the "Transactions" pane to configure the database
connectivity for the transaction management service.
- Repeat step 8 in the "Repository" pane to configure the database
connectivity for the repository service.
- Note:
- On OS/400 installations, it is recommended that you do
not change the Login or Password fields in the "Event Management",
"Transactions", or "Repository" panes of the Database tab. At
installation time, user profile QWBISVR43 is created with no
password on OS/400. This user profile owns all of the resources
necessary to run InterChange Server Express. If you change these Login
or Password fields, you will then have to also change the authorities to all
of the installed files on OS/400 in order for InterChange Server Express to
work correctly.
Do the following to change the password for the user name that InterChange
Server Express uses to access one of the databases:
- Click Change next to the Password field in the
"Event Management", "Transactions", or "Repository"
panes.
- Type the new password in the New Password field.
- Type the new password again in the Confirm Password
field.
- Click OK.
Do the following to set properties for flow tracing and subsystem tracing
at the "Tracing Levels" tab:
- Click the Tracing Levels tab.
- To set the flow trace level for a business object, select the desired
value in the Level column for the particular business object in the
"Flow Tracing Levels" pane.
For more information on flow tracing, see the System Administration Guide.
- To set the trace level for an InterChange Server Express subsystem, select
the desired trace level from the drop-down menu associated with the
subsystem.
Do the following to configure the locations to which InterChange Server
Express logs and traces runtime information:
- Click the Trace/Log Files tab.
- Do the following in the Logging pane to configure how
InterChange Server Express logs runtime information:
- Enable the To Console checkbox if you want InterChange Server
Express to output logging information to the console.
- Note:
- This option is not recommended for use if your InterChanger Server Express is
on OS/400. On OS/400 systems, this option will result in the
information being placed in a spool file and the information will be truncated
at 132 characters.
- Enable the To File checkbox if you want InterChange Server
Express to output logging information to a file. Do the following steps
as well if you enable this checkbox:
- Type the name and path of the file to which output
should be logged in the unlabeled text field, or click the browse button to
select a file.
- Do one of the following to specify how the log files should be
managed:
- Click the Unlimited checkbox to have InterChange Server Express
write information to the file specified in step a without a limit on the size of the file.
- Note:
- Be sure to manage the file well if you make this selection, because
InterChange Server Express could potentially fill up the disk and cause a
system failure.
- Do the following to configure a log file archiving approach:
- Select Byte, KB, MB, or GB
from the unlabeled drop-down menu to indicate whether you want to store the
log and archive files in increments of bytes, kilobytes, megabytes, or
gigabytes.
- Select a number from the Log file drop-down menu to indicate
the number of bytes, kilobytes, megabytes, or gigabytes you want the log file
to grow to before it is archived.
- Select the number of archive files that should be kept before they are
deleted in the Number of archives drop-down menu.
- Repeat step 2 for the "Tracing" pane.
- To enable tracing for WebSphere MQ, type the name and path of the file to
which output should be logged in the unlabeled text field in the
"WebSphere MQ Tracing" pane, or click the browse button to select a
file.
- To use stack tracing, select Enable Stack Tracing and then
select the desired severity level from the Tracing Severity Level
drop-down menu.
For more information about stack tracing, see System Administration Guide.
InterChange Server Express can send e-mail notifications when errors occur
in the business integration system. By default the server uses the Java
e-mail APIs, and can send e-mail notifications for a number of different
subsystems. To enable the server to send e-mail notifications for
errors experienced by individual collaborations, you must configure the system
to use the Adapter for e-Mail. For detailed information on configuring
the system for e-mail notification, see the System Administration Guide. To make the necessary
modifications to the configuration file (which is just one step in the total
number of tasks described in the System Administration Guide), do the following:
- Click the E-mail tab.
- Select Java mail or Connector
mail from the E-mail send type drop-down menu depending on
which e-mail notification mechanism you want to use.
- Note:
- Keep in mind that collaborations will only be able to send e-mail
notifications if you choose Connector mail.
- If you chose Java mail in step 2, type the name of the computer on which the SMTP server is
installed in the SMTP mail host field.
- Type a valid e-mail address or comma-separated series of e-mail addresses
in the text fields for each subsystem as desired.
The "Misc" tab in the System Manager configuration file editor has
panes for configuring features such as persistent monitoring, flow control,
and long-lived business processes. Do the following to configure
settings for these features:
- Click the Misc tab.
- Do the following in the "Persistent Monitoring" pane:
- Select Continue in the Action on error drop-down
menu if you want InterChange Server Express to continue running in the event
of errors experienced by the persistent monitoring subsystem.
Select Shutdown in the Action on error drop-down menu
if you want InterChange Server Express to shut down in response to errors with
the subsystem.
- Select the desired tracing level in the Persistent monitoring
service drop-down menu to specify the tracing level for the
subsystem.
- For information on the interface elements in the "Flow Control"
pane, see the System Administration Guide.
- For information on the interface elements in the "Flow Monitoring"
pane, see the System Administration Guide.
- In the "Workflow Management" pane, type a number in the
Business object consumer processor to indicate how many threads you
want spawned to manage business objects participating in a long-lived business
process.
These threads deliver business objects from the collaboration runtime to
the appropriate connector controllers when the business objects are retrieved
from persistent storage to resume processing in a long-lived business
process. For more information on long-lived business processes, see the
Collaboration Development Guide.
- For information on the "Server Memory" pane, see Using the memory checker thread.
At the "Environment Properties" tab, you can specify any Java user
environment properties that might be required in the business integration
system. Some environments may require such a variable to be
specified; instead of adding them to the script that starts InterChange
Server Express, you can add them to the configuration file by using the
"Environment Properties" tab. Do the following to add a new
environment property:
- Click the Environment Properties tab.
- Type the name for the property in the Property name
field.
- Type the value for the property in the Property value
field.
- Click Add Property.
To delete a property, select the property and click Delete
Property.
To edit a property's value, select the property and edit the text in
the Property value column for the property.
Do the following to configure the connectivity between InterChange Server
Express and the WebSphere MQ persistent messaging software:
- Click the WebSphere MQ tab.
- Type the name of the computer on which the WebSphere MQ server is
installed in the Host name field.
- Type in the Port number field the port over which WebSphere MQ
allows clients to communicate with the server.
The default port is 1414.
- Note:
- For OS/400, if you change the port number here, you also must change the port
number in the job description for the server instance. Use the CHGJOBD
CL command and change the value on the RQSDTA parameter. The job
description name is the name of the InterChange Server Express instance in the
QWBISVR43 library on OS/400.
- Type in the Queue manager name field the name of the queue
manager that has been created to contain the queues on which InterChange
Server Express will persistently store messages for the flows it
processes.
- Type in the Channel field the name of the channel over which
clients of WebSphere MQ communicate with the WebSphere MQ server. The
default value is CHANNEL1. Consult with the WebSphere MQ
administrator at the site to determine if CHANNEL1 can be used and
if not, which channel can be used.
