Using System Manager to configure InterChange Server Express
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.
Viewing general properties using System Manager
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.
Configuring database properties using System Manager
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 Server or 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 maximum number of connections
you want InterChange Server Express to make with the database server
in the Maximum number of connections field,
or enable the Unlimited check box to allow
InterChange Server Express an unlimited number of connections.
-
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.
For more information on the behavior of the server in the case
of a database deadlock, see the WebSphere InterChange Server: System Administration Guide.
- Type in the number of times you would
like the InterChange Server Express to try to regain a connection to
the database should you lose your connection in the Max connect retries field.
- Type in the amount of time (in seconds)
you want InterChange Server Express to wait to reconnect to the database
in the Connect retry interval field.
- 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.
Changing database passwords
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, user
profile QWBISVR44 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 then have to also
change the authorities to all of the installed files on OS/400 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.
Configuring
security using System Manager
One of the key features of InterChange Server Express
is the ability to authorize permissions for users accessing the
system using roles, known as role-based access control (RBAC).
Roles can easily be defined by the administrator and assigned to
a group of users, restricting access to key components only to verified
users.
Use of RBAC functionality ensures that only an administrator,
or users with permission to administer roles, are allowed to create
users and assign roles. If RBAC is not active on the server, any
user can create users and roles with no verification. Therefore,
if you want to use the server with RBAC on, after the product is installed,
have the administrator turn RBAC on. This will prevent any users
from turning RBAC on or editing other fields.
For more information regarding security and role-based access
control, see the Administration Guide.
Note:
Security can also be configured using the new parameter
-xmsp with the repos_copy command. For more information on using
repos_copy, see
Using repos_copy.
In InterChange Server Express, RBAC is automatically turned on during installation. Therefore, use the steps that follow only if RBAC is explicitly turned off post-installation and needs to be turned on again.Do
the following to configure InterChange Server Express for role-based
access control:
- First create a user with the administrator role. If there is
no user with the administrator role, then even if RBAC is turned
on in the InterChange Server Express configuration, the server will
reboot with RBAC turned off.
- Click the Security - RBAC tab.
- Select the Enable RBAC check box.
- In the User registry pull-down menu choose Repository or LDAP.
If you chose Repository, you must enter the following information
in the Repository details area of the Security - RBAC tab:
- Database
- Maximum number of connections or select the Unlimited check
box
- Max connect retries
- Login
- Password
- Connect retry interval
If you chose LDAP, you must enter the following
information in the LDAP setting area of the Security - RBAC tab:
- LDAP URL
- User name DN
- Password
- Userbase DN, which is the base distinguished name
- User name attribute, which is the attribute in the LDAP schema
that InterChange Server Express uses as a user name
- Search criteria, to use when retrieving LDAP users
- Maximum number of search returns, which is the maximum number
of entries returned from a search
- SSL, which indicates whether you want a secure connection between InterChange
Server Express and LDAP
- In the Server start user field, enter
the user name that will start the server.
- In the Server start password field enter
the password associated with the user name.
- To turn on audit settings select the Enable audit check
box and fill in the following fields:
- Audit log directory, which is the path of the audit log file
- Audit log frequency, for example, Daily, Weekly or Monthly
- Audit file size (MB), which is the maximum size for the audit
file
For more in-depth information on configuring options for InterChange
Server, refer to the Administration Guide.
Configuring
privacy using System Manager
End-to-end privacy is a very important feature of InterChange
Server. It allows you to send messages securely from the moment
they leave a source adapter, through InterChange Server, to a destination
adapter.
Critical to any secure system is end point verification. IBM
WebSphere Business Integration Server Express provides security
at each end point of the information flow, ensuring that your information
is secure from end to end.
When business communications to InterChange Server Express are
transported asynchronously over JMS, messages are stored on disk
at the queue manager while they wait for processing. End-to-end
privacy ensures that these messages are secured at this level.
Note:
For in-depth information on end-to-end privacy,
refer to the System Administration Guide.
To configure InterChange Server Express for end-to-end privacy,
do the following:
- Click the Privacy tab.
- Enter the Keystore Path and Keystore Password. (For information
on keystores, refer to the Administration Guide.)
- Click on Import privacy setting and select
one of the available connectors. This loads the privacy configuration
for that specific connector.
You can also set a general privacy setting by doing the following:
- In the General privacy setting area, click
on All in the Message type column.
A drop-down list will appear. Select a message type.
- Click on None in the Security level column.
- Select a destination for the messages by double-clicking in
a cell in the Destination column, for example, System Test Connector
or Destination Connector.
To set a privacy setting for an individual business object, do
the following:
- Enter the name of the business object or select a business object
from the available list in the Name column
under Individual business object setting.
- Select a security level by double-clicking on a cell in the Security level column
and selecting an option from the drop-down list that appears.
- Select a destination for the messages by double-clicking in
a cell in the Destination column, for example,
System Test Connector or Destination Connector.
For more in-depth information on the options for configuring
InterChange Server Express for end-to-end privacy, refer to the Administration Guide.
Configuring tracing levels using System Manager
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 WebSphere InterChange Server: 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.
Configuring logging and tracing properties using System Manager
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:
- 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 WebSphere InterChange Server: System Administration Guide.
Configuring e-mail notification properties using System Manager
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 WebSphere InterChange Server: 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 WebSphere InterChange Server: 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.
Configuring miscellaneous properties using System Manager
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 WebSphere InterChange Server: System Administration Guide.
- For information on the interface elements in the "Flow
Monitoring" pane, see the WebSphere InterChange Server: 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 WebSphere InterChange Server: Collaboration Development Guide.
- For information on the "Server Memory" pane,
see Using the memory checker thread.
Configuring environment variables using System Manager
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.
Configuring WebSphere MQ properties using System Manager
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 QWBISVR44 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.
