Connect configuration parameters are those basic data that are defined in setting up connector readers, connector senders, etc. This page describe different types of those parameters, how those parameters can be set, how to export/import configuration data, etc.
Configuration data is structured into configuration areas, configuration groups, configuration instances and parameters of those instances. Setup IFS Connect will open up the feature that allow us to edit these connect configuration parameters.
Configuration group is a set of configuration instances. Each area will consist of a few such configuration groups. Integration has the following groups.
Note: Consider limitation for multiple instances of Connect Server here
Connect_J2EE Server Configuration:Configuration instances can be divided into two main types, Static Instances and Non Static Instances. Static instances cannot be duplicated,
deleted or renamed. They will be created by the initialize program. They will be indicate by
Gray color, e.g. DEFAULT queue, NOTIFICATIONS queue, ERROR queue,
J2EE_SERVER server etc.
All other non static instances can be duplicated and can have more than one instance of that type.
Configuration Instances can have two types of parameters. Editable and Write Protected.
Each Write Protected parameter will be shown in Gray.
e.g. JAR_FILE parameter for each connector reader.
Help text for each parameter is given in the tool tip of the parameter value field. You can keep you mouse pointer on the parameter value field to get the help text of a parameter.
As mentioned above you can't edit Write Protected parameters. To edit other parameters of an instance select the configuration instance. When editing a parameter the instance will be marked as edited.
Use the Save feature toolbar button and save changes.
For Envelopes and Transformers it is possible to import/export
the envelope or transformer file as binary data. You can import a new file as binary or export a saved binary file
to the disk.
To import:
Load link will open up a file dialogue allowing you to select the file to load as the
configuration parameters binary data.
To export:
Save link will open up a file dialogue which allows you to save the binary data in the parameter as a file.
New configuration instances are always created by duplicating existing ones. To duplicate an
instance select the instance first and use either RMB Duplicate
or Duplicate feature toolbar button.
Note:
You cannot duplicate static configurations like ERROR, NOTIFICATIONS, TRASHCAN in Message Queues.
Rename the duplicated instance, edit the parameters there and save by clicking the Save feature toolbar button to create the new instance.
To remove a configuration, select the instance and click 'Delete' feature tool bar
button. The item will be marked as removed. Use the Save feature toolbar button to commit
removal.
Note: Static configuration instances are not possible to remove.
Import Configuration at
configuration area level, e.g. Integration, of the
configuration tree. If
configuration area already exists, new details will be merged into the
existing record. Record will be saved if the import is successful.Export Configuration
from RMB menu on the area level. The result will be saved in xml format.
Import of configuration instances is little different from the above procedure.
Import Instance at
the configuration area level, e.g. Integration, of the configuration tree. The imported instance will be added to the configuration group
to which it belonged in the exported system. If this group was not present in the current area you should add that group to this configuration area first. Else the instance will not be imported.
If the import is successful, a new record will be added
to the client dataset which can be modified and save.Export Instance. The result will be saved in xml format.
