x

To add a JDBC connection:

1. In the left console pane of the Server menu, select Data Provider.
2. Beneath the JDBC section, click Add.

   The JDBC Data Provider Definition pane displays.

3. Provide the appropriate values for your JDBC connection as listed and defined in the following table.

   Parameter	Description
   JDBC Connection Pool Properties
   Name *	Enter the name of the JDBC data provider to add.
   Driver Class	The JDBC driver class is the name of the class that contains the code for this JDBC Driver. You can select a predefined database from the drop-down list or enter your own. The following are sample values for the driver: com.microsoft.jdbc.sqlserver.SQLServerDriver COM.ibm.db2.jdbc.app.DB2Driver com.informix.jdbc.IfxDriver sun.jdbc.odbc.JdbcOdbcDriver oracle.jdbc.driver.OracleDriver com.sybase.jdbc2.jdbc.SybDriver The required .jar files for the JDBC driver must be installed and registered in the Service Manager classpath. You can use the Path Settings option on the console to add Java classes and libraries.
   Connection URL	The JDBC connection URL to use when creating a connection to the target database. The URL generally includes the server name or IP address, the port or service, the data source name, and a driver specific prefix. You can select a predefined database from the drop-down list or enter your own. The following are sample values for the URL: jdbc:microsoft:sqlserver://server:1433;DatabaseName=DB jdbc:db2:database jdbc:informix-sqli://HOST:PORT/DB:INFORMIXSERVER=SERVER_NAME jdbc:odbc:DBjdbc:oracle:thin:@HOST:PORT:SIDjdbc:sybase:Tds:HOST:PORT For more information, see the JDBC documentation for the specific data source.
   User	User name with respect to the JDBC URL and driver. SREG names can be used.
   Password	Password with respect to the JDBC URL and driver. SREG names can be used.
   Connection Pool Properties
   Initial Pool Size *	Number of connections to place in the pool at startup.
   Maximum Number of Idle Connections *	Maximum number of idle connections to retain in the pool. A value of zero (0) means no limit except what is enforced by the maximum number of connections in the pool. This value can be reset using the jdbc command, allowing this to be changed, often on a schedule, to respond to changing database conditions.
   Maximum Number of Connections *	Maximum number of connections in the pool. A value of zero (0) means no limit. This value can be reset using the jdbc command, allowing this to be changed, often on a schedule, to respond to changing database conditions.
   Login Timeout	Time in seconds to wait for a pooled connection before throwing an exception. A value of zero (0) means to wait forever.
   Behavior When Exhausted	What to do when the pool reaches the maximum number of connections. Block means wait for a connection to become available for the period defined by the login timeout parameter. Fail means throw an exception immediately.
   Validation SQL	SQL statement that can be executed to validate the health of a pooled connection. The statement should return a result set of at least one row.
   Validate on Borrow	If set to true, the validation SQL statement will be executed on a pooled connection before returning the connection to the caller.
   Validate on Return	If set to true, the validation SQL statement will be executed on a pooled connection before replacing the connection in the pool.

4. Click Test to check for proper connections.

   If a connection cannot be made, an error message displays describing the problem. Typically, the driver has not been installed or the classpath has not been set.

5. Click Add to return to the Data Provider pane.

x

Since drivers are stopped, they do not need to be added. However, if you need to add a JLINK data source:

1. In the left console pane of the Server menu, select Data Provider.
2. Beneath the JLINK section, click Add.

   The Data Provider - JLINK pane displays, as shown in the following image.

   

3. In the Name field, type the name of a new server. In this example, type NEWSERV.
4. In the Description field, type a brief description for the new server. The default is JLINK Data Provider.
5. From the Type drop-down list, select a JLINK server type.

   The default is WebFOCUS Pro Server.

6. Type the required values for Host and Port.
7. Type the required values for User and Password.
8. From the Engine drop-down list, select a database engine.

   The default is 0 (EDA).

9. From the Encoding drop-down list, select a codepage.

   The default value is 137 (U.S. English).

10. To encrypt data that is transported over the wire (optional), select the Encryption check box.
11. In the Trace File field, type the path and name of the file for the trace output.
12. To set trace levels, select any number of the check boxes listed (optional).
13. Click Add.

x

This feature allows you to specify the amount of time a connection can remain idle in the connection pool. Similar to a feature of Apache DBCP, the idle connection eviction thread runs at regular intervals, with the following options:

• Eviction Interval. Time between runs of the idle connection eviction thread, in seconds. A negative value means the eviction thread will never run.
• Idle Connection Timeout. The minimum amount of time a connection can remain idle in the pool before the eviction thread disposes of it. When the eviction thread runs and finds that a connection has been idle for at least this interval, the connection will be removed from the pool and closed. Note that a connection can remain in the pool longer than the timeout, depending on the scheduling of the eviction interval.
• Maximum Number of Tests Per Run. This is a performance tuning option. Since the eviction thread must lock the pool when it runs, this option allows you to specify how many connections can be tested in each run, thus limiting the duration of the lock. If the eviction interval is short, or the number of connections in the pool is large, performance may improve with fewer connections tested per run. Enter 0 to test all connections.
• Validate Idle Connections. If true, the eviction thread executes the validation SQL statement on connections that have not reached the idle connection timeout. If the statement does not execute successfully, the connection will be dropped from the pool.

x

The Services Provider pane enables you to define properties required to support iWay business services as web services.

To configure for a web service:

1. In the left console pane of the Server menu, select Services Provider.

   The Services Provider pane opens, as shown in the following image.

   

2. From the Data Store Type drop-down list, select a repository you want to configure.

   The following are available:

   • Embedded Database (no data provider required)
   • File System (no data provider required)
   • IBM DB2
   • MaxDB
   • Microsoft SQL Server
   • Oracle
   • Sybase

   You must configure the tables before using the repository. For more information on configuring repository tables, see the iWay Installation and Configuration Guide.

   Note: iWay Service Manager is installed with an embedded HSQL repository, which is the default data store for information that is generated during design time and then published into a deployed runtime environment.

   For more information on the properties on this window, see the table in Services Provider Settings.

3. From the Data Provider Name drop-down list, select an available data provider.

   For more information on how to add a data provider, see How to Add a Data Provider.

4. Type new values or modify existing values.
5. Click Update.

x

The following table lists and describes the Services Provider settings.

Property	Type/Value	Description
Repository
Data Store Type	Choice	Acts as a metadata repository. The default value is Embedded Database. Select a database from the drop-down list: File System (not supported for production use), IBM DB2, MaxDB, Microsoft SQL Server, Oracle, and Sybase.
Data Provider Name	String	JDBC driver defined in the Data Provider pane. Select from the drop-down list, or click Add to define a new JDBC connection.
Connection Pooling	Boolean	When selected, turns on connection pooling for the JDBC driver.
iWay Business Services
Publishing Location	Directory	Directory where the WSDL files produced by the iWay Business Services Provider (iBSP) are stored. If the directory does not exist, select the check box to create the named directory.
Adapter Library	Directory	Directory where the iWay adapter JAR files are located. If the directory does not exist, select the check box to create the named directory.
Policy Based Security	Boolean	When selected, enforces iBSP security policy. For more information, see the iWay Business Services Provider User's Guide.
Namespace Awareness	Boolean	If set, iWay Business Services preserve XML namespaces from the adapter's response message in the SOAP response message. Note: When the Java system property ibsp.wsdl.nsaware is set to true, namespaces are preserved without regard for the Namespace Awareness property.
Operation Namespace URI	String	If set, iWay Business Services use this specified URI for the operation node in the SOAP response message. Note: When the Java system property ibsp.operation.ns is set, the value of this Java system property is used and the Operation Namespace URI property is ignored.

Additional Notes on the Operation Namespace URI Property

In this example, an iWSE SOAP response from a web service method named PFIVP_1 would have the following format:

<SOAP-ENV:Envelope xmlns:SOAP-
ENV="http://schemas.xmlsoap.org/soap/envelope/">
     <SOAP-ENV:Body>
        <PFIVP_1Response cid="9952CD68D2AFAC3FCD1ED00A645237D4"
         xmlns="urn:iwaysoftware:ibse:jul2003:PFIVP_1:response">
              <d>
                  <d1/>
                  <d2/>
              </d>
        </PFIVP_1Response>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Note that the child of the SOAP Body element is named PFIVP_1Response and it declares a default namespace of urn:iwaysoftware:ibse:jul2003:PFIVP_1:response. This element is the parent of the actual output from the adapter. The element name and the namespace URI are constructed using the name of the service method. In a use case scenario, you may not want the response from an iWSE service to reference iWay Software, as the default namespace URI does. You can use the Operation Namespace URI parameter to override the default behavior by supplying your own namespace URI.

x

To add a data provider:

1. Click Add in the Data Provider Name section.

   The Data Provider - JDBC pane opens.

   

2. Enter a name for the JDBC data provider.
3. From the Driver Class drop-down list, select the JDBC class for the data provider.

   You can also manually enter the name.

4. From the Connection URL drop-down list, select the connection URL to use when creating a connection to the target database.

   You can also manually enter the URL.

5. Enter the user ID to access the repository database.
6. Enter the password to access the repository database.
7. Click Test.

   You should receive a response that says:

   The JDBC data provider test completed successfully.

   If you receive an error, troubleshoot accordingly. Ensure the driver is in the iWay7\lib directory. For more information, see the iWay Installation and Configuration Guide.

8. Click Update if the test is successful.

   You connection appears on the Data Provider pane. If you need to change its parameters, you can click the name of the connection.

   

   If you need to define both the target and source repositories, repeat this procedure to define another repository.

x

You can migrate repositories using the iWay Service Manager Administration Console. These repositories can be for iWay Service Manager, the older iWay Adapter Manager, Servlet iBSP, or iWay Connector for JCA. The structure of the repository has not changed.

Some of the things you can migrate include:

• Migrate the data in the default iWay SM HSQL database to another database repository.
• Migrate an older iWay Adapter Manager repository into the default iWay SM HSQL database.
• Migrate a Servlet iBSP or iWay Connector for JCA database repository.

Note: Monitoring tables are not migrated.

In this section:

• Source repository refers to the older existing repository you wish to migrate.
• Target repository refers to the new repository you wish to use.

Top of page

x

A directory is a set of information with similar attributes organized in a logical and hierarchical manner. The protocol accesses LDAP directories, regardless of the form of the directory itself. LDAP sees the directory in a standard manner.

• A directory is a tree of directory entries.
• An entry consists of a set of attributes.
• An attribute has a name (an attribute type or attribute description) and one or more values. The attributes are defined in a schema.
• Each entry has a unique identifier, its Distinguished Name (DN). This consists of its Relative Distinguished Name (RDN) constructed from some attribute(s) in the entry, followed by the DN of the parent entry. Think of the DN as a full filename and the RDN as a relative filename in a folder.

A DN may change over the lifetime of the entry, for instance, when entries are moved within a tree. To reliably and unambiguously identify entries, a unique key (called a UUID) may be provided in the set of the entry's operational attributes.

iWay provides a simple access function to supply the value of a single LDAP attribute for use as a configuration parameter. The following function accesses the information in the directory:

_LDAP( filter, attribute, context [,providername])

For example: _LDAP("cn=John Doe",mail,'dc=example') might return the mailing address for John.

LDAP providers may also be used to hold certificates for security operations.

Top of page

x

A keystore is a database of key material. Key material is used for a variety of purposes, including authentication and data integrity. There are various types of keystores available, including "PKCS12" and Sun's "JKS." Some keystores can contain both encryption keys and security certificates. Formally, however, a keystore holds the private key for one or more PKI key pairs.

A truststore is a database of key material. It holds the public certificates of trusted partners for message exchange. Although it is possible to share a single file with the keystore, more formally a truststore and a keystore are separate entities.

A certificate store, also called a certstore, is a database of public key certificates and Certificate Revocation Lists. The CRL is required to stop the use of a certificate when it would otherwise be considered valid. A CRL is not needed to tell you a certificate is bad once its expiration date is reached. In fact, CRLs are usually cleaned of expired CRLs after one complete CRL revision period has elapsed. This means the expired CRL will continue to appear in at most one CRL after it expired.

If certificate revocation is turned on, you will need one CRL for each CA in the certificate chain you want to verify. If a CRL is missing, there is no way to know whether certificates issued by that Certificate Authority are still valid. Therefore, all certificates issued by this CA will be considered revoked. A CRL that contains no certificates is acceptable. It belongs to a Certificate Authority that did not revoke any certificates.

x

CertStore providers define the directories from which certificates and CRLs can be loaded. A configured Directory Certstore provider can be used as a named provider in the components that support CRL checking for messages.

x

The following section describes LDAP certstore providers.

Top of page

Top of page

x

To define a keystore provider using the iWay Service Manager Administration Console:

1. In the left console pane of the Server menu, select Security Provider.

   The Security Provider pane opens.

   

2. Click New in the Keystores section.

   

   The Keystore Definition pane opens.

   

3. Enter the parameters for the keystore and make sure to select the appropriate values from the Keystore Type and the Keystore Provider drop-down lists that will correspond to your keystore configuration.
4. In the Callback Handler field, optionally enter the fully qualified name of a callback handler that will satisfy authentication callbacks for the keystore.

   The callback handler must satisfy the javax.security.auth.callback.CallbackHandler interface and be available in the classpath for iWay Service Manager.

   It is recommended that developers make use of the Test button to verify that the property values are tested against the Keystore before completing the definition. When there are no failures encountered during testing, then continue from this point.

5. Click Add.

   You are returned to the main Security Provider pane and the new keystore that was defined is added to the list.

   

   Note: The keystore provider is set as the default SSL provider and default S/MIME provider if it is the first one that is created. When an SSL or S/MIME default provider is removed, the first remaining keystore provider is automatically set as the default.

6. To define multiple keystore providers, repeat this procedure.

   A defined keystore provider can be used as a named provider when configuring other iWay components (for example, listeners, services, emitters, and so on).

x

To define an SSL context provider using the iWay Service Manager Administration Console:

1. In the left console pane of the Server menu, select Security Provider.

   The Security Provider pane opens.

   

2. Click New in the SSL Contexts section.

   The SSL Context Provider pane opens.

3. Enter the appropriate values for the SSL context provider parameters.

   For more information, see Parameters for SSL Context Providers.

4. Click Add when you are finished.

   You are returned to the main Security Provider pane and the new SSL context provider that was defined is added to the list.

   

   Note: The SSL context provider is set as the default provider, if it is the first one that is created. When the default provider is removed, the first remaining provider is automatically set as the default.

5. To define multiple SSL context providers, repeat this procedure.

   A defined SSL context provider can be used as a named provider when configuring IP-based components, such as AS2 and HTTP.

   Note: To activate any new security providers that have been configured, you must restart iWay Service Manager.

x

The following table lists and describes all of the available parameters for SSL context providers.

Property	Description
Name	The name of the SSL Context definition to add.
Description	A brief description of the use of this SSL Context.
Keystore Provider	Configured Security Provider for the keystore you wish to use for this SSL context. Choose default to use the default SSL Keystore Provider. Keystores hold private keys.
Truststore Provider	Configured Security Provider for the truststore you wish to use for this SSL context. Choose default to use the default SSL Keystore Provider. Truststores hold the certificate of Trusted CAs used to verify peer certificates.
Security Protocol	Specify the version of security protocol that should be used. During SSL handshake, a negotiation selects the protocol to be used from the best mutually supported. This field sets the minimum acceptable security protocol. If the handshake cannot select a mutually supported protocol, the connection fails. The options are: SSL, SSLv2, SSLv3, TLS, TLSv1, and TLSv2. Note: You must have Java version 1.7 configured on your system to use TLS protocol version 2.
JCE SSL Context Provider	JCE Provider for the SSL Context.
Server Key Alias	Alias for the key to be used to identify secure servers using this SSL context. If not supplied, the key will be selected using JSSE default behavior.
Client Key Alias	Alias for the key to be used to identify secure clients using this SSL context. If not supplied, the key will be selected using JSSE default behavior.
Session Cache Size	The maximum number of SSL sessions that will be retained in the session cache. Sessions in the cache can be reconnected with less overhead than those not cached.
Session Timeout	Maximum length of time (in seconds) that an SSL session can remain in the cache.
Enable Certificate Revocation	Enable CRL checking of certificates during handshake.
OCSP Responder	Name of the OCSP Responder provider. This verifies the status of certificates online instead of relying on Certificate Revocation Lists (CRLs).
JCE PKIX Trust Manager Provider	JCE provider to construct PKIX Trust Manager. Choose 'Not Specified' for default.
JCE Signature Provider	JCE provider used to verify digital certificate signatures during handshake.
PKIX Certificate Store	Certificate store from which certificate revocation lists are loaded.
Enabled Cipher Suites	If supplied, only cipher suites on this list will be enabled for SSL sockets or SSL engines created using this provider. The user must take care that enabled cipher suites are supported by other components specified. Enter as comma-delimited list or use FILE() function. If left blank, all available cipher suites will be enabled and be available during SSL negotiation.
Hostname Verification	If true, client SSL connections using this provider will attempt to verify that the server certificate matches its host name.
Client Authentication	If true, servers using this provider will use SSL client authentication, that is, the server must receive and authenticate a certificate from the client as part of the SSL handshake.

x

To define a Pooling provider:

1. In the left console pane of the Server menu, select Pooling Providers.

   The Pooling Providers pane opens, as shown in the following image.

   

2. Click New in the Defined HttpClient Providers section.

   The HttpClient Provider pane opens, which contains settings for the Pooling provider, as shown in the following image.

   

3. Enter the appropriate values for the Pooling provider parameters.
4. Click Add when you are finished.

   You are returned to the main Pooling Providers pane and the new provider that was defined is added to the list.

5. To define multiple Pooling providers, repeat this procedure.

x

The following table lists and describes all of the available parameters for the Pooling provider.

Parameter	Description
Name	Name for the Pooling provider.
Description	Brief description of the use of this Pooling provider.
Maximum Connections Per Host	Defines the maximum number of simultaneous connections allowed per host. When this threshold is reached, new connections will not be accepted until current connections are closed and the total number of connections is below the limit. Leave this field blank (default) or set a value of zero to have no maximum limit of connections.
Maximum Total Number of Connections	Defines the maximum number of simultaneous connections that are allowed overall. When this threshold is reached, new connections will not be accepted until current connections are closed and the total number of connections is below the limit. Leave this field blank (default) or set a value of zero to have no maximum limit of connections.
Connection Timeout	Maximum length of time (in milliseconds) that a request will block while waiting for a connection to become available from the pool. A value of zero (0) means there is no timeout.
Set TCP No Delay	If set to true, Nagle's Algorithm on the client socket is disabled. This will result in faster line turnaround at the expense of an increased number of packets.
Reuse Socket Address	Allow sockets to be bound to the local addresses of sockets that already closed, but are still in a TIME_WAIT state. In applications that make large numbers of short-lived connections, this can reduce or eliminate address in use and related errors when no more ephemeral ports are available to be bound. When using this option, you should specify the any local address wildcard (0.0.0.0 in case of IPv4 or :: for IPv6) as the value of the IP Interface Host parameter below. For more detailed information and a discussion on the interactions between the Reuse Socket Address and IP Interface Host parameters, see the following website http://stackoverflow.com/questions/14388706/socket-options-so-reuseaddr-and-so-reuseport-how-do-they-differ-do-they-mean-t Note: The effects of setting this option can be complex and should be handled with care.
Linger-On-Close Timeout	This option disables or enables immediate return from a close() function of a TCP Socket. Enabling this option with a non-zero integer timeout means that a close() function will block pending the transmission and acknowledgment of all data written to the peer, at which point the socket is closed gracefully. Upon reaching the linger timeout, the socket is closed forcefully, with a TCP RST. Enabling the option with a timeout of zero does a forceful close immediately. Note that this may have the effect of leaving sockets on the server side in a wait state. Enter -1 or leave blank for the proper default. Note: The effects of setting this option can be complex and should be handled with care.
Redirect Strategy	Determines how an HTTP redirect response is handled. The default is to follow redirects according to the RFC. The off strategy does not redirect any request.
Proxy	If set to true, emit through a proxy server.
Proxy User ID	User ID for the proxy challenges.
Proxy Password	Password to access the proxy server.
Proxy Domain	Domain for NTLM proxy authentication.
Proxy Host	Host where the proxy can be accessed.
Proxy Port	Port where the proxy can be accessed.
Authentication Preference	If several schemes are returned in the WWW-Authenticate header, this parameter defines which schemes take precedence over others. The value is a comma-separated list of authentication scheme names with the most preferred scheme listed first. The default is negotiate,NTLM,Digest,Basic where negotiate means SPNEGO. Kerberos requires the negotiate scheme and HttpClient version 4.1 or higher.
Kerberos Login Entry	The Application Login Entry in the JAAS login configuration file that will be used to login to Kerberos. This login entry should configure a Kerberos login module (Krb5LoginModule).
SSL Context Provider	Named iWay Security provider for SSL Context. Defaults to the value assigned to the SSL Context Provider.
IP Interface Host	Local IP Interface from which the outgoing IP socket originates.
Idle Timeout	Time in seconds that an unused connection can remain in the pool. If set to 0, connections will remain in the pool indefinitely.
Cookie Specification	The cookie management specification determines the rules for parsing, validating, and formatting cookies. By default, best-match is selected from the drop-down list, which is the recommended policy. HttpClient version 4.1 or higher is required.
Persistent Cookie Store	If set to true, cookies are preserved between server reboots. By default, false is selected.

x

By default, the Pooling provider handles cookies automatically. The provider looks for cookies in the responses it receives and then stores them in a cookie store. When a new request is made, the provider looks in the cookie store and the cookies that match are resubmitted to the originating server. Each Pooling provider manages its own independent cookie stores.

Cookie management is configured with parameters on the Pooling provider. The Cookie Specification parameter determines the rules for parsing, validating, and formatting cookies. The specifications that are available for this parameter are listed and described in the following table.

Cookie Specification	Description
best-match	Selects a cookie policy based on the format of cookies sent with the HTTP response.
rfc2109	Cookie Version 0.
rfc2965	Cookie Version 0 and Cookie2 Version 1.
compatibility	Closely mimics (mis)behavior of common web browsers.
netscape	Conforms to the original draft specification published by Netscape Communications. Should be avoided unless strictly necessary for legacy code.
ignoreCookies	Cookie management is disabled.

The recommended Cookie Specification is best-match because it can handle cookie versions 0, 1, and 2.

To disable automatic cookie management, select ignoreCookies. Cookies will continue to appear in the request header namespace, but they will not be automatically resent to the originating host. This option might be necessary for legacy iWay applications that handled cookies manually.

The cookie store is managed in memory. By default, the cookies are lost when the server halts. To preserve the contents of the cookie store, set the Persistent Cookie Store parameter to true. When persistence is enabled, the cookie store is saved to disk every time it changes. The next time the server reboots, it will reload the cookies from the file. The persistent cookie store files are specific to a server configuration and do not interfere with other configurations.

The provider periodically discards cookies that have expired. This avoids a memory leak and limits the growth of the file on disk. Expired cookies are also discarded when reloading a cookie store after a restart.

The HTTP Nonblocking Emit Service (com.ibi.agents.XDNHttpEmitAgent) is used to send HTTP requests. The HTTP Client Provider parameter for this agent determines which provider will send the request. This indirectly selects the cookie store and therefore the cookies that will be resubmitted to the destination server.

When two HTTP Nonblocking Emit Services must keep their cookies independent, they can use two different Pooling providers. To avoid the proliferation of Pooling providers, it is also possible to name a specific cookie store using the Cookie Store Name parameter for the service. The name could be any identifier chosen by the application. The Pooling provider keeps each named cookie store independent. Just like the default cookie store, a named cookie store is created and managed automatically. If the Pooling provider has the Persistent Cookie Store parameter to true, then all named cookie stores are also persistent.

The application might need to create many named cookie stores where each one is needed only for a very short time. This can cause an apparent memory leak, especially if the cookie expiration times are far in the future. The application can control the lifetime of a cookie store by explicitly deleting it with the help of the XDCookieStoreAgent. Set the Action parameter to Delete Cookie Store and specify values for the HTTP Client Provider and Cookie Store Name parameters. This will destroy the cookie store and delete the persistent file if applicable. Leave the Cookie Store Name parameter empty to delete the default cookie store. Unlike named cookie stores, the default cookie store is emptied but never destroyed.

x

To define a Data Quality Runtime providers:

1. In the left console pane of the Server menu, select Data Quality Providers.

   The Data Quality Providers pane opens, as shown in the following image.

   

2. In the Data Quality Runtime Providers area, click New.

   The Configuration pane opens, which contains parameters and settings for the Data Quality Runtime provider, as shown in the following image.

   

3. Enter the appropriate values for the Data Quality Runtime provider parameters.
4. Click Add when you are finished.

   You are returned to the Data Quality Providers pane, where the new Data Quality Runtime provider that was defined is added to the list.

5. To define multiple Data Quality Runtime provider, repeat this procedure.

x

The following table lists and describes all of the available parameters and settings for the Data Quality Runtime provider.

Parameter	Description
Name *	Enter a name for the Data Quality Runtime provider.
Description	Enter a brief description for this Data Quality Runtime provider.
Minimum Pool Size (per plan) *	Number of pre-started DQS execution threads for each plan managed by this provider. This setting is useful for iSM multithreading processing.
Maximum Pool Size (per plan) *	Maximum DQS execution threads allowed in parallel for each plan managed by this provider. Requests in excess of this size will be queued for execution.
Pool Inactivity Period *	Time in minutes that an unused data quality execution thread will remain in the pool.

x

To define a Data Quality provider (deprecated):

1. In the left console pane of the Server menu, select Data Quality Providers.

   The Data Quality Providers pane opens, as shown in the following image.

   

2. In the Data Quality Providers (deprecated) area, click New.

   The Configuration pane opens, which contains parameters and settings for the Data Quality provider (deprecated), as shown in the following image.

   

3. Enter the appropriate values for the Data Quality provider (deprecated) parameters.
4. Click Add when you are finished.

   You are returned to the Data Quality Providers pane, where the new Data Quality provider (deprecated) that was defined is added to the list.

5. To define multiple Data Quality providers (deprecated), repeat this procedure.

x

The following table lists and describes all of the available parameters and settings for the Data Quality provider (deprecated).

Parameter	Description
Data Quality Provider Settings
Name *	Enter a name for the Data Quality provider (deprecated).
Description	Enter a brief description for this Data Quality provider (deprecated).
DQS Plan File *	Location of the DQS plan file containing the logic of the data quality operation.
Runtime Config File	Location of iWay DQS runtime configuration file (optional). This file is used to define DQS runtime variables, such as JDBC data sources or folder shortcuts used in the plan.
Pooling Configuration
Minimum Pool Size *	Number of pre-started DQS execution threads for this plan. This setting is useful for iSM multithreading processing.
Maximum Pool Size *	Maximum DQS execution threads allowed in parallel for this plan. Requests in excess of this size will be queued for execution.
Pool Inactivity Period *	Time in minutes that an unused data quality execution thread will remain in the pool.

x

To define a Secure Shell (SSH) provider:

1. In the left console pane of the Server menu, select Secure Shell Provider.

   The Defined SSH Providers pane opens, as shown in the following image.

   

2. Click New.

   The Configuration pane opens, which contains parameters and settings for the Secure Shell provider, as shown in the following image.

   

3. Enter the appropriate values for the Secure Shell provider parameters.
4. Click Add when you are finished.

   You are returned to the Defined SSH Providers pane, where the new Secure Shell provider that was defined is added to the list.

5. To define multiple Secure Shell providers, repeat this procedure.

x

The following table lists and describes all of the available parameters and settings for the Secure Shell (SSH) provider.

Parameter	Description
SSH Providers
Name	Name used to reference the Secure Shell (SSH) provider.
Description	Brief description of the Secure Shell (SSH) provider.
Key Exchange Factories	Select one of the following classes that will be used to exchange keys between the SSH client and the SSH server: diffie-hellman-group14-sha1 diffie-hellman-group1-sha1
Random Factory	Pseudo random number generator (bouncycastle).
Cipher Factories	Select one of the following classes for a cryptographic cipher, used either for encryption or decryption: aes128-cbc 3des-cbc blowfish-cbc none
Compression Factories	Select one of the following classes that will be used to compress the stream of data between the server and SSH clients: none zlib zlib@openssh.com
MAC Factories	Select one of the following classes that will be used for Message Authentication Code (MAC) for use in SSH: hmac-md5 hmac-sha1 hmac-md5-96 hmac-sha1-96
Signature Factory	Select one of the following classes that will be used by the server to sign and verify packets sent between the server and client. ssh-dss ssh-rsa
Key Pair File
Provider	Provider for key pairs. The provider is used to create the SSH Key Pair repository when it doesn't exist. When the repository exists the Provider returns the Key Pair generated by the Signature Factory that was used to create the repository. com.ibi.sftp.common.keyprovider.XDSecureHostKeyProvider org.apache.sshd.server.keyprovider.PEMGeneratorHostKeyProvider org.apache.sshd.server.keyprovider.SimpleGeneratorHostKeyProvider
Key Pair File Signature	Select one of the following options that will be used by the SFTP Server to sign the Key Pair File that is generated if the Key Pair File does not exist: RSA DSA
Key Pair File Path	Fully qualified path to the Key Pair File. If the path points to a file that does not exist, then the provider will create a Key Pair file at this location using the Key Pair File Signature that was selected.
Key Pair File Password	Password for the SSH Key Pair file.
Authentication
Password Authenticator	Select one of the following classes that will be used by the server to authenticate the password of the SSH client: Test Password Authenticator File Based Password Authenticator JDBC Based Password Authenticator No Password Authentication
Public Key Authenticator	Select one of the following classes that will be used to authenticate the public keys of the SSH client. Test Authenticator Publickey Authenticator No Public Key Authentication
User Repository
Repository Type	Determines how the user repository is stored. The repository can be stored either as an XML file or as a JDBC database. This repository defines the users permitted to exchange messages with this server along with their mailbox and security characteristics. XML JDBC TPM
Security File	The location of the security file. This field is required either when the Repository Type parameter is set to XML.
JDBC Provider Name	The name of the JDBC Data Provider.
Basic
Reuse Address	If set to true, when the connection is closed, immediately make the address available, bypassing defaults of TCP.
Connections Backlog	Number of connections allowed to queue before a failure. The default is 50 connections.
SSH Property Label
SSH property description	Specify a property/value pair.

x

To configure a Schedule provider:

1. In the left console pane of the Server menu, select Schedule Provider.

   The Schedule pane opens, as shown in the following image.

   

2. Click New.

   The Schedule Configuration pane opens, which contains parameters and settings for the Schedule provider, as shown in the following image.

   

3. Enter the appropriate values for the Schedule provider parameters.
4. Click Add when you are finished.

   You are returned to the main Schedule pane, where the new Schedule provider that was defined is added to the list.

5. To define multiple Schedule providers, repeat this procedure.

x

The following table lists and describes all of the available parameters for the Schedule provider.

Parameter	Description
Name	Enter a name to identify this Schedule provider. The name will display in the logs when the scheduler starts the process.
Description	Enter a brief description for the use of this Schedule provider.
Alternate User	If the task requires a different user authentication, then enter the user with the correct authentication.
Password	Enter the password for the alternate user.
Active	If set, this scheduled item is active.
Skip Holidays	If checked, iSM will use either the Calendar provider specified for the Calendar Provider parameter or the Calendar provider that is marked as the default provider.
Calendar Provider	Select the defined Calendar provider from the drop-down list that contains the holiday definitions to apply to this schedule. The Calendar provider can be selected from a list of providers configured on this iSM configuration or a Calendar provider from a different configuration can be manually entered. If left blank and the Skip Holidays check box is selected, then the Calendar provider that was selected as the default will be used.
Minutes	Select minutes within the hour to run the task (minutes not checked will be skipped). For example, to schedule a task to run every minute of the hour, check all of the minutes; to schedule a task to run every 15 minutes click 0, 15, 30 and 45 minute check boxes.
Hours	Select hours within the day to run the task (hours not checked will be skipped). For example, to schedule a task to run every hour of the day, check all of the hours in both the AM and PM row.
Month	Select the month within the year to run the task (months not checked will be skipped). For example, to schedule a task to run every month check all the months. To schedule a task to only run in January, check the Jan check box.
Weekday	Select day of week to run (days not checked and not implied by Day of Month will be skipped). Weekday and Day of Month are cumulative. For example, every Wednesday AND the 15th of the month.
Day of Month	Select day within the month to run the task (days not checked and not implied by Weekday will be skipped). Day of Week and Day of Month are cumulative. For example, every Wednesday AND the 15th of the month.
Command	iSM command to be scheduled for execution. For more information on a specific command, see the iWay Service Manager Command Reference Guide.
Duration Timer	The length of time that the task will run prior to the Dependent Command. The format of duration [in seconds] is in the following format: [xxh][xxm]xx[s] For example, 04h30m45, which creates a duration of 4 hours, 30 minutes, and 45 seconds.
Dependent Command	Command to be executed after the Duration Timer of the task has expired. The command can be directed to any configuration / iWay Integration Application (iIA) by including it in a remote command.

x

This section describes all of the steps (including reference information) that are required to configure the Calendar provider.

Top of page

Top of page

x

In addition the being able to select specific dates, there are three convenience buttons that will either check specific dates, or uncheck (clear) the dates in the calendar:

• Skip US Holidays
• Skip Weekends
• Clear calendar

The convenience buttons allow you to quickly configure the schedule for the next 18 months.

Top of page

Top of page

Top of page

x

The function buttons interface with the current configuration of iSM.

Function Button	Description
Add	Displayed only when adding new Calendar providers. When you are satisfied with the calendar settings clicking Add commits the calendar settings and writes the calendar data to the iSM configuration.
Update	The Update button is displayed in conjunction with the Reload button when the Calendar provider already exists within the iSM configuration. Like the Add button, when you are satisfied with the calendar settings, clicking Update commits the calendar settings and writes the calendar data to the iSM configuration.
Reload	At any time during an update of the Calendar provider, if you want to discard your changes the current Calendar provider may be reloaded from iSM by clicking Reload. All changes to the Calendar provider are discarded and a fresh copy (as of the last Add or Update action) is reloaded from the iSM configuration.

<iwayhome>/etc/mibs

x

The iSM SNMP agent is exposed as a provider. There can be one or more providers defined in a configuration, although more than one is only required if there are independent managers controlling different aspects of the server.

To complete the configuration, you will need to know the configuration of the manager. For example, the manager will be configured to interact with the agent on a specific port (usually 161). If you have multiple configurations on the same installation host, you will need to separate these by having different addresses. For performance reasons, iSM uses separate providers on each configuration rather than having a single provider poll other configurations.

You will also be requested to specify which protocol(s) are used by your manager. Select the set that is supported by the manager.

The provider can accept simultaneous requests from multiple managers, and some managers are capable of sending multiple requests to their agents in parallel. If this is the case, you can specify the number of expected parallel requests by setting the number of execution threads.

Top of page