As400 Connection    ODBC Connection     Oracle Connection    
LotusNotes Connection    XML Connection    Mainframe Connection

Multi-Platform Connectivity
This is OV2Word's most powerful feature in data-merge document technology.

Take your business's document system to the next level by migrating from OfficeVision to a truly cross-platform architecture. Now you can tie together your DB2 reservoirs to ODBC, LotusNotes, Mainframe, and Oracle databases. Create a multi-platform, web-enabled document portals for your satellite offices to work from using our XML connection. 

Supplement your investment and develop real-time, on-demand reports from heterogeneous, WAN-enterprise systems with your existing application. Layout the report in MS Word, add the logic to identify the data, generate an interface pointing to the various data sources using our SDK Connection tool. 

Local Connection
Settings for the connection types are stored in the connection manager ini file. Changes in this connection file can be made through the an easy to use GUI. The Local Connection can both be configured with global settings as well as with DID specific settings. 

AS400 Connection
Settings for the connection types are stored in the connection manager ini file. Changes in this connection file can be made through the an easy to use GUI.

This connection can use the TCP/IP or APPC protocol to connect to an AS/400 database. 

· To use the TCP/IP connection a Winsock 1.1 (or higher) compliant TCP/IP implementation (protocol stack) must be installed and configured on the PC.

· To enable ITP to communicate with the AS/400 through APPC, your PC must be running a correctly configured PC Support or Client Access/400 compatible APPC router. PC Support’s own router complies with this as well as for example NetSoft’s router. For Windows 95 and NT the router must support the E32APPC.DLL API.

The AS/400 Connection can both be configured with global settings as well as with DID specific settings in the dm.ini file. The following listing describes the available settings.

AS/400 Connection Settings

AS/400 System (Address) 
The name or address of the AS/400 host to connect to. The value that you have to enter here depends on the protocol:

TCP/IP Connection
The format used for the name of AS/400 system to connect to is:
host[:port]

Where host is the name or the dotted decimal TCP/IP address of the AS/400 and port is the optional port number or service name for a port number that the to which the AS/400 daemon is listening. The default port is 10042. You need not specify a port, unless you start the daemon on the AS/400 with another port than the default.

When you specify a host name, you must make sure that the TCP/IP name resolution process can resolve this name. TCP/IP must find the associated dotted decimal address, either by using a DNS or by using a local hosts file. 
When you specify a port name you must make sure that TCP/IP will be able to resolve the service name (i.e. find the associated port number). It usually does so by looking it up in the local services file (in the windows directory).

APPC Connection

In the router configuration, you have to define links to one or more AS/400’s in your network. Such a link is often called a Partner Logical Unit. This connection uses this Partner Logical Unit definition as the basis for communication.

ODBC Connection
Settings for the connection types are stored in the connection manager ini file. Changes in this connection file can be made through the an easy to use GUI.             
           
The ODBC Connection can be configured with global settings as well as with DID as with DID Module specific settings in the connection file. The ResetConnectionsAfterModel setting can only be used on DID level. The following listing describes the available settings.

ODBC Connection Settings

The values specified in Connstr, UserID, Password and DSN will be combined into one connection string.

Oracle Connection
Settings for the connection types are stored in the connection manager ini file. Changes in this connection file can be made through the an easy to use GUI.

The Oracle Connection can be configured with global settings as well as with DID as with DID Module specific settings in the dm.ini file. The following listing describes the available settings.

Oracle Connection Settings

We advise to use the UserId, Password and Server setting to specify a userid, password and server and not the Connstr setting. If a Connstr setting has been specified, it will be split into userid, password and server (if provided). Any available values specified at UserId, Password or Server will overwrite these values.

Lotus Notes Connection
Settings for the connection types are stored in the connection manager ini file. Changes in this connection file can be made through the an easy to use GUI.

The Notes Connection can be configured with global settings as well as with DID as with DID Module specific settings in the connection file. 

Lotus Notes Connection Settings

Batch Application Environment
When you connect to a Notes/Domino database a password may be required. The dialog box that pops up for this password is not under the control of the connection, but solely under the control of Notes. This causes problem in a batch environment where one does not want any interaction to take place. In a batch environment the password should be provided to Notes automatically. 
There are two solutions in Lotus Notes/Domino as described by Lotus Corporation:

1. Circumvent the problem by using a userid that does not have a password (actually has a blank password). In this case the password is of course not needed and asked at all. Allthough this may seem a bad solution it is actually not so bad when used in a controlled batch environment with no external access. One could furthermore restrict the userid to read-only access on the databases.

2. Use the Notes Extension Manager dll, ITPNotesExtPwd.dll that is provided by ITP. This dll provides the password to Notes when it is needed. However this dll is used for all-or-nothing, i.e. when this dll is installed and registered is operated for all Notes applications on the particular machine including ITP, but also the Notes Client.

Using ITPNotesExtPwd.dll

Please follow the following steps to use the extension manager dll

1. Copy the dll from the ITP Bs directory to your notes program directory (often c:\lotus\notes).

2. Register the dll by adding the following line to notes.ini:EXTMGR_ADDINS=ITPNotesExtPwd.dll

3. Configure the password in the Connection Configuration on the global level, using the ITP Administration Program. It can both be stored encrypted or as plain text. We advise to store it encrypted.

ITPNotesExtPwd.ini

Instead of storing the password in ITP’s connection configuration file (dm.ini), it can also be stored in a file with the name ITPNotesExtPwd.ini in the notes program directory, in the following format:
[Global]Notes.Password=xxx

The password can also be encrypted (format Encrypted:xxx), in which case the value should be copied from the regular connection configuration file.

The dll will first check for the availability of this file and if this file is not available it will look for the connection configuration file.

Remarks

· The EXTMGR_ADDINS line should not be the last line of notes.ini.

· If EXTMGR_ADDINS is already present in notes.ini, the name of the dll should be added to this line, using a comma as the separator.

· If the password cannot be found, none of the ini files can be found and/or the setting is blank, Notes will interactively prompt for the password anyway.

· The only way to make sure that the password is not used for other applications than ITP, is to use a separate notes.ini file for ITP. 

· It is not possible to use separate passwords for separate environment, DIDs or DID modules. Therefore it should only be configured on the global level. Configuration on other levels will be ignored.

XML Connection
Settings for the connection types are stored in the connection manager ini file. Changes in this connection file can be made through the an easy to use GUI.

The XML File Connection can be configured with global settings as well as with DID as with DID Module specific settings in the connection file. 

XML Connection Settings

Mainframe Connection
Settings for the connection types are stored in the connection manager ini file. Changes in this connection file can be made through the an easy to use GUI.

The Mainframe Connection can both be configured with global settings as with DID specific settings in the connection file. Some settings are meaningful for all types of mainframe connections. Some settings are only meaningful when using CPIC while other settings are only meaningful when using MQSeries. Using the CPI-C API for the Mainframe Connection is depreciated and will not be supported in future versions of the software.

Mainframe Connection Settings

©2003 ITSG Inc. All rights reserved.    Terms of Use    |    Privacy