Under the copyright laws, neither the documentation nor the software may be copied, photocopied, reproduced, translated, or reduced to any electronic medium or machine-readable form, in whole or part, without the prior written consent of Lotus Development Corporation.
Copyright 1998 Lotus Development Corporation
55 Cambridge Parkway
Cambridge, MA 02142
All rights reserved. Printed in the United States.
Trademarks
Lotus and Lotus Notes are registered trademarks, and LotusScript and Lotus NotesView are trademarks of Lotus Development Corporation.
AIX, AS/400, DB2, DPROPR, OS/400, IBM, MVS, and OS/2 are registered trademarks, and DB2/2 and RS/6000 are trademarks of International Business Machines Corporation.
Oracle and SQL*Net are registered trademarks, and Oracle7 and PL/SQL are trademarks of Oracle Corporation.
SYBASE and Transact-SQL are registered trademarks and SQL Server and Open Client are trademarks of Sybase, Inc.
ZMerge is a trademark of Granite Software, Inc.
EDA/SQL and FOCUS are registered trademarks of Information Builders, Inc.
Informix is a registered trademark of Informix Software, Inc.
Novell and NetWare are registered trademarks of Novell, Inc.
INTERSOLV is a registered trademark, and DataDirect is a trademark of INTERSOLV, Inc.
Visigenic is a trademark of Visigenic Software, Inc.
Microsoft and Windows are registered trademarks, and Microsoft Windows NT and ODBC are trademarks of Microsoft Corporation.
Intel is a registered trademark of Intel Corporation.
UNIX is a registered trademark of UNIX Systems Laboratories, Inc.
Hewlett-Packard and HP are registered trademarks, and HP-UX is a trademark of Hewlett-Packard Company.
Sun, Solaris, and SunOS are registered trademarks or trademarks of Sun Microsystems.
All SPARC trademarks are trademarks or registered trademarks of SPARC International, Inc.
Alpha, DEC, and Digital are registered trademarks of Digital Equipment Corporation.
Apple and Macintosh are registered trademarks and System 7 is a trademark of Apple Computer Inc.
All other trademarks are property of their respective owners.
Disclaimer
The information in this database is subject to change and does not represent a commitment on the part of Lotus Development Corporation.
O=Lotus Notes
O=Lotus Notes
PURSAFO
|.:#U
O=Lotus Notes
CN=Lotus Notes Template Development/O=Lotus Notes
PURSAFO
$Info
$Body
PURSAFO
Using Lotus Connectivity Guide
@ @@ @` @
@@ @@@@@`@@
`@ `@@`@``@
yeesEdgies
copyright
Lotus Connectivity Guide
This database is the online documentation for Lotus Connectors.
Full-Text Index
In addition to using the views built into this database, we strongly encourage you also to create and use a full-text index for the database. Doing so will require extra disk space, but will allow you to very quickly find the information you need.
Changing the Information in the Database
To add a comment to the database...
1) In a view, highlight the item you want to add a comment to.
2) Pull down the Compose menu.
3) Choose the "Comment" form.
O=Lotus Notes
O=Lotus Notes
PURSAFO
|.:#U
O=Lotus Notes
CN=Lotus Notes Template Development/O=Lotus Notes
PURSAFO
$Info
$Body
PURSAFO
O=Lotus Notes
O=Lotus Notes
PURSAFO
|.:#U
O=Lotus Notes
CN=Lotus Notes Template Development/O=Lotus Notes
PURSAFO
$TITLE
$Index
$Formula
$FormulaClass
$ViewFormat
$Comment
==?v3BMC
Section
Chapter
Section
1S3S4S6S8S
&Arial
Times New Roman
LCConSection
Chapter
Section
1S2S
Section:
Section
Chapter
Section
1S3S4S6S8S
Section
Contents
ChapterNumber
DocumentNumber
O=Lotus Notes
O=Lotus Notes
PURSAFO
|.:#U
O=Lotus Notes
CN=Lotus Notes Template Development/O=Lotus Notes
PURSAFO
6]zA,f
$TITLE
$Info
$WindowTitle
$$Script_O
$$ScriptName
ChapterNumber
DocumentNumber
$Body
Helvetica
Times
LotusFrute
Symbol
Times New Roman
5Courier New
This manual provides information related to enterprise connectivity for Domino Enterprise Connection Services, LotusScript Extension for Lotus Connectors, and Lotus Enterprise Integrator.
Included in this manual is information about the software required to connect to external data sources in order to access the data in those external sources.
Also included in this manual is information about the Lotus Domino Connector connectivity test program, LCTEST. This program runs a connectivity test that establishes that the client data source access libraries are available and functional on the Domino Server. The test program does not test any specific functionality of the products, but ensures that the communications and client software required to access a specific data source is available and properly configured.
&Arial
This manual includes the following sections.
Section
Description
Chapter 1
Introduction
This chapter provides information about the organization of this manual and includes information about related documentation.
Chapter 2
LCTEST
This chapter provides information and instructions for running the connectivity test program, LCTEST.
Chapter 3
DB2 Connectivity
This chapter provides information and instructions for testing your system connectivity to DB2.
Chapter 4
EDA/SQL Connectivity
This chapter provides information and instructions for testing your system connectivity to EDA/SQL.
Chapter 5
ODBC Connectivity
This chapter provides information and instructions for testing your system connectivity to ODBC.
Chapter 6
Oracle Connectivity
This chapter provides information and instructions for testing your system connectivity to Oracle.
Chapter 7
Sybase Connectivity
This chapter provides information and instructions for testing your system connectivity to Sybase.
&Arial
Symbol
Refer to the documents below for more information.
Domino Enterprise Connection Services
For information about Domino Enterprise Connection Services, refer to the
Domino Enterprise Connection Services User
,s Guide
, provided as an online NSF file (DECSDOC.NSF). You can also refer to the online field and popup help in the Connection Server documents.
LotusScript Extension for Lotus Connectors
LotusScript Extension for Lotus Connectors Reference Guide
- This manual, provided as an NSF file (LSXLCDOC.NSF), describes the LotusScript Extension for Lotus Connectors included with Domino 4.63 and above.
Enterprise Integrator Documentation
For more information about Enterprise Integrator and related products, refer to the following documents:
Enterprise Integrator 3.0 Release Notes
- The release notes contain information about the current release of Enterprise Integrator that may not be included in the printed documentation. We recommend that you read the release notes to review the information they contain.
Enterprise Integrator C API Reference Guide
- This is an online document delivered with the Enterprise Integrator software developer's kit (available on the Lotus Toolkit Collection CD) ) and on the Lotus Enterprise Integration web location at www.eicentral.lotus.com. This may be used by developers wishing to create new Connectors for external data sources, which can then be operated via DECS, the Lotus Connector LSX and Lotus Enterprise Integrator.
- This online, HTML document describes the Java classes that can be used to write Java Activities.
Other Documentation
For more information that you may find helpful, refer to the following documents:
Notes Administrator
,s Guide
- Provides information for configuring and administering a Notes installation.
LotusScript 3.1 Language Reference
- Provides information about writing LotusScript programs. This could be useful if you want to use the Lotus Connector LotusScript Extensions.
&Arial
Symbol
LCTEST is a connectivity test program provided with Domino Enterprise Connection Services (DECS). It is installed in the Domino program directory if you choose to install DECS.
Supported Data Sources
LCTEST tests system connectivity to the following supported data sources:
DB2 (not supported on Windows NT/Alpha or Solaris Intel Edition)
EDA/SQL (not supported on Windows NT/Alpha or Solaris Intel Edition)
ODBC (Open Database Connectivity)
Oracle
Sybase
Requirements
Before running LCTEST, you must have the appropriate software installed on the Domino host for each data source you want to test. The remaining chapters of this manual provide information about the software required for each of the supported data sources.
Symbol
Follow the steps below to run LCTEST.
Locate the LCTEST.EXE program specific to your operating system platform in the Domino program directory. The LCTEST program has the following names for each of the associated operating system platforms:
nlctest for Windows NT/95
lctest for AIX
ilctest for OS/2
alctest for Windows Alpha NT
lctest for UNIX
Double-click on the program name to launch it, or type the program name at the system prompt.
3. Enter the number of the test you want to run and press Enter. Depending on the type of data source you are testing, you are prompted to enter additional information as required to log in to the specified data source. For more information, refer to the chapter in this manual that discusses the specific data source for which you want to test connectivity.
RSymbol
Connectivity software requirements depend on the operating system platform and the specific version of DB2 that you are using.
IBM eNetwork Communications Server for your operating system platform
(see
www.software.ibm.com/enetwork/commserver
for more information)
DB2 Connect Personal Edition
DB2 Enterprise Edition
DB2 CAE (Client Application Enabler) version 2.1.2 or later.
In addition, to connect to DB2 on an AS/400 or mainframe, a DDCS gateway must be installed.
Helvetica
Times
LotusFrute
Symbol
Times New Roman
5Courier New
You should test for connectivity to the DB2 servers. To test for connectivity:
Run the version of the test program LCTEST, located in the Domino program directory, appropriate to your operating system. See Chapter 2 for more information.
Select DB2 from the program menu.
When the program prompts for a DB2 Database, User Name, and Password, enter valid connection information. The database must be cataloged in the DB2 database directory. (Refer to your DB2 Client documentation for further information on configuring a connection to a database.)
After entering the DB2 database, user name and password, the program attempts to connect to the DB2 Server. A message appears, telling if the test was successful or not.
You can retry a connection by entering Y at Try Again? [N]. This provides the opportunity to re-enter all of the required information, in case a mistake was made in spelling or you entered the wrong database, user name, or password.
Symbol
&Arial
This section provides information about software required to connect to DB2. This information is provided to help you get started. You should refer to the documentation for the specific software you are using for complete instructions.
IBM is currently shipping DB2 UDB Version 5. The specific product to use will depend on your environment.
Here is a brief listing of connectivity software available with DB2 Version 5:
DB2 Workgroup Edition: Includes Client Pack CD for client connectivity, but does not include support for MVS/ESA, OS/390, OS/400, VM and VSE.
DB2 Enterprise Edition: Includes all the functionality of DB2 WorkGroup Edition, plus support for host connectivity providing users with access to DB2 databases residing on host systems including MVS/ESA, OS/390, OS/400, VM and VSE.
DB2 Client Application Enabler: Enables a client workstation to access the DB2 Server. Refer to DB 2 documentation for supported platforms.
DB2 Universal Database Personal Edition: Formerly know as DB2 Single Server. Enables you to create and use local databases, and to access remote DB2 databases. Available for OS/2 Win 95 and WINNT.
DB2 Connect Enterprise Edition: Formerly know as DDCS Multi-User gateway. Provides access from clients on the network to DB2 databases that reside on hosts such as MVS/ESA, OS/390, OS/400, VM and VSE.
DB2 Connect Personal Edition: Formerly know as DDCS Single-User. Provides access from a single workstation to DB2 databases residing on hosts such as MVS/ESA, OS/390, OS/400, VM and VSE. This product is only available for OS/2, Windows 95 and Windows NT.
Refer to the documentation provided with IBM DB2 Universal Database (the manual entitled "Road Map to DB2 Programming", Appendix A, "About DB2 Universal Database").
Connectivity to DB2 on AS/400
Direct DB2/400 Connectivity
DB2 Connect Personal Edition
is the only required DB2 software for connectivity. There is no need for a DB2 Client such as DB2 CAE.
1. One Server connecting to DB2/400
Install
IBM DB2 Connect Personal Edition Version 5
on the Server machine.
Bundled with Connect Personal Edition is an SNA Server. Install the SNA Server with the SNA over APPC option. It must be over APPC; the AS/400 requires APPC for DB2 connectivity. Also, in this stand alone environment the SNA over APPC is self sufficient; there is no general network need for APPC and SNA in the network.
Refer to the
IBM DB2 Connect Personal Edition Quick Beginnings Version 5
document (numbered S10J-8162-00) as a means to begin the installation. It states to use a user name and password that are a user name and password on the DB2/400. This will allow the installation to perform operations on the AS/400 without intervention.
This option does not require the installation of software to the AS/400.
2. Multiple Servers connecting to DB2/400
Install
IBM DB2 Connect Enterprise Edition Version 5
This will install a gateway to DB2/400. A gateway allows access to the DB2/400 data from multiple Servers. This software is only necessary if you plan to have more than one Server.
The Connect Enterprise Edition does not come with bundled SNA software, so it is up the user to install an SNA Server, such as Microsoft's SNA Server or the OS/2 Communication Manager software.
If the DB2 Connect Enterprise Edition is not installed on the machine, then a DB2 Client such as DB2 CAE needs to be installed onto the machine. This client is needed to perform the direct connection from the Domino Server to DB2.
This option does not require any software installed to the AS/400.
3. Server connecting to DB2/400 with DDCS
Requirements: Installed DDCS and SNA Server.
This option is for customers with an existing DDCS installation. This option only exists for customers who have DDCS already in house, because at this time only the latest
DB2 Connect Version 5
software is available for purchase.
DDCS Single User or Gateway can be used to connect to DB2/400. With DDCS, there is also a requirement for an SNA server over APPC. Therefore, you will need SNA software such as Microsoft SNA or OS/2 Communication Manager.
If DDCS is not installed on the Server machine, then a DB2 Client such as DB2 CAE needs to be installed on the Server machine. This client is needed to perform the direct connection from the Server to DB2/400.
This option does not require any software installed to the AS/400.
ODBC DB2/400 Connectivity
Several software packages support connectivity to DB2/400 through ODBC. The preferred approach to connectivity is through the DB2 Client. This gives the Server the advantage of straight connectivity, speed and datatype access without the ODBC layer. However, should a user prefer to install such products as Rhumba or IBM's Client Access for AS/400, then the connectivity would be through the ODBC Link.
Be certain to verify the requirements of the individual packages, in most cases an SNA server is still a requirement.
This option may or may not require additional software installed to the AS/400.
&Arial
5Courier New
DECS offer native connectivity to DB2. This provides a direct connection to DB2 on all DB2 supported platforms, and enhances the DB2 connectivity previously provided through ODBC. The native interface offers improvements in speed and support for native datatypes not accessible through ODBC. This section contains information on configuring native DB2 connectivity through DB2 CAE and DDCS.
Getting Started
Network communications programs must be installed to the Server and the DB2 system to establish a network connection for data transfer. Depending on the platform you are using to operate the Server, and the operating system used to store DB2, your requirements are either to install CAE/2 (Client Application Enabler/2) or DDCS (Distributed Database Connection Services). These communications products are available from IBM. The machines must have connectivity through the DB2 CAE (Client Application Enabler) or other DB2 run-time environment (i.e., DB2 Server). CAE/2 must be version 2.1.0 or above and must be native for the operating system it is running on (i.e., on OS/2, you must have CAE for OS/2 Warp; there is a separate version available for Windows NT).
For DDCS or Client Application Enabler OS/2 systems to access DRDA Application Servers such as DB2 for MVS/ESA, DB2 for VSE and VM, and DB2 for OS/400, you must also have the APPC protocol support installed. Instructions to do this are included below in the section
&Communications Manager/2 Setup for DB2/2 to DB2/400 Server
For DDCS for Windows NT to access DRDA Application Servers such as DB2 for MVS/ESA, DB2 for VSE and VM, and DB2 for OS/400, the APPC protocol support must also be installed on your system. The program required to do this is Microsoft SNA Server version 2.11 or later.
Before attempting to connect, verify connectivity through the DB2 Command Line program (supplied with DB2) or the LCTEST connectivity test program, described at the start of this s
ection.
Sample Steps for DB2 Configuration
The following illustrates some sample steps you may wish to follow when configuring your DB2 connectivity. For full details, refer to the DB2 manual "Install/Use DB2 Clients for xxx" where xxx is your operating system. The steps below assume you are installing the CAE for the Server machine running on OS/2, Windows NT or HP-UX, and are using TCP/IP. Note that you must install CAE Version 2.1 or above. The steps will be much the same if you instead install the DB2 Server on this machine.
Install the DB2 CAE software.
Ensure the Server machine can resolve the DB2 Server TCP/IP host address (i.e., you should be able to ping the server). If it can't, you need to either have the Domain Name Server updated to include the DB2 Server name and address or add an entry to your Server machine's hosts file. For example, on WARP this would consist of running the TCP/IP Configuration Utility and adding the DB2 Server Name and IP address in the Hostnames dialog. On Windows-NT and HP-UX, you must manually edit the hosts file (NT: c:\winnt35\system32\drivers\etc\hosts, HP-UX: /etc/hosts) and add an entry such as 9.21.15.235 tcphost
Ensure the DB2 Server has enabled the TCP/IP protocol through the DB2COMM environment variable. This variable may indicate multiple protocols. Make certain it includes "TCPIP". This variable must be set at the time the DB2 Server is started.
Ensure the services file on the DB2 Server machine contains an entry for TCP/IP support for each database manager instance you plan on accessing. A second entry is required to support TCP/IP interrupt from DB2 V1.x Client and is not required if all your clients are V2.0 or above.
db2inst1c 3700/tcp # DB2 connection service port for V1 and V2.
# Also serves as an interrupt
# connection service port for DB2 V2.
db2inst1i 3701/tcp # DB2 interrupt connection service port
# for V1.x client releases
where db2inst1c is the value of the service_name parameter, db2inst1i is arbitrary. 3700 and 3701 are the port numbers for the connection and interrupt port, and TCP is the protocol. The port number 3700 is arbitrary, but must be unique within the file. The second port number must also be unique, and equal to the first number plus one. These same numbers must be used when configuring the services file on the Server machine (step 6).
On the DB2 Server, ensure the database manager is listening for connections for the DB2 instance. This is done by issuing the following command from the DB2 command line processor at the server:
UPDATE DATABASE MANAGER CONFIGURATION USING SVCENAME db2inst1c
where db2inst1c is the service name.
For the changes to take effect, restart the database manager at the server (issue db2stop and db2start in succession at the server).
NOTE:
The svcename used must match the service name configured in the services file on both the client and the server.
Ensure the services file on the Server machine contains an entry matching the entry on the DB2 Server. Depending on the version of DB2 server you are connecting to, you need one or two entries in the services file:
db2inst1c 3700/tcp # DB2 connection service port for V1 and V2.
# Also serves as an interrupt
# connection service port for DB2 V2.
db2inst1i 3701/tcp # DB2 interrupt connection service port
# for V1.x client releases
NOTE:
You only need the first entry if you are connecting to a DB2 Version 2 server. This must match the service name entry in the server's services file.
You need both entries if you are connecting to a Version 1 DB2 server. These entries must match the corresponding server entries. The service name, port number (3700 and 3701 in our example) and protocol must be identical.
On the Server machine, catalog the DB2 Server and Database. To catalog the server, use the DB2 command line processor on the Server machine and enter the command:
CATALOG TCPIP NODE nodename REMOTE hostname SERVER servicename
where nodename is a name you pick to refer to this connection, hostname is the TCP/IP name of the DB2 Server machine, and servicename is the instance name you entered in the services file (you only need to do this once using the first port even if you also entered an interrupt connection service port in the services file).
Next, catalog the database with the command:
CATALOG DATABASE databasename AS local_database_alias AT NODE nodename
where databasename is the name of the database on the DB2 Server, local_database_alias is a name you pick which you will use to connect to the database from the Server machine, and nodename is the name you used in the previous CATALOG TCPIP command.
Exit and restart the DB2 command line processor. Try connecting to the DB2 database with the command:
CONNECT TO local_database_alias USER username
where local_database_alias is the alias you cataloged and username is a valid DB2 username.
You may now verify that will have connectivity to DB2 by running the LCTEST.EXE program found in the Domino program directory. This program will prompt you for the database name (local_database_alias), userid, and password.
When to use IBM Distributed Database Connection Services (DDCS)
DDCS has been replaced by DB2 Connect Personal Edition and DB2 Connect Enterprise Edition. The following information is provided for environments which may not yet have acquired either of these new connectivity packages.
When connecting to DB2 for MVS/ESA, DB2 for VSE and VM(SQL/DS), or DB2 for OS/400, you can use DDCS. DDCS can also be used to connect to any other DB2 server (e.g., WIN-NT, AIX, etc.), but it is more direct and efficient to go from the local machine using CAE
rectly to the DB2 server.
It does not matter where DDCS is installed as long as the Domino Server machine can connect to the DDCS machine through TCP/IP, SPX or any other DB2 supported protocol.
Refer to the DDCS Install/Configuration document for instructions and software requirements. Connections to external systems may require additional communications software. For example, to connect DDCS on OS/2 to MVS or AS400, the OS/2 machine must have APPC connectivity, namely IBM Communications Manager/2 Version 1.1 or later or IBM Communications Server for OS/2 Warp Version 4.
Sample Steps for using DDCS
As an example of how DDCS would work with the Server, lets assume the following:
The Server is running on an Windows NT machine called NP1. This machine has DB2 CAE for Windows NT installed and will connect to the DDCS workstation using TCP/IP. DDCS is installed on an OS/2 Warp machine called DB2GW. It also has TCP/IP and IBM Communications Server installed.
Connectivity to a DB2 database on the MVS machine MVS1 is desired and will be made through APPC.
The connectivity between DB2GW and MVS1 must be established though DB2GW's IBM Communications Server and MVS1's VTAM. The details of this configuration and configuration at the MVS host are not covered here, refer to the DDCS Install/Configuration manual for information.
MVS1's node and database is cataloged at the DDCS machine. The following commands are issued to catalog the remote node and database:
CATALOG APPC NODE db2node REMOTE db2pic SECURITY PROGRAM
where db2node is a name you pick to refer to this host, db2pic is the Symbolic Destination Name you defined when you configured MVS1 in the IBM Communications Server.
CATALOG DATABASE db2db AS mydb AT NODE db2node AUTHENTICATION DCS
where db2db is the MVS database name, mydb is the database alias, and db2node is the node defined in the previous command.
The services file on the DDCS machine (DB2GW) is modified to include an entry for a database instance (inst1c) and an interrupt connection (inst1i). The following DB2 command must be used to tell the database manager to listen for connections to the instance from remote clients to the instance.
UPDATE DATABASE MANAGER CONFIGURATION USING SVCENAME inst1c
The environment variable DB2COMM is set to TCPIP. DDCS is started with the operating system command DB2START.
Connectivity from NP1 is established through the DB2 CAE by defining the target database:
CATALOG TCPIP NODE gw1 REMOTE db2gw SERVER inst1c
CATALOG DATABASE mydb AS mvsdb2 AT NODE gw1
where gw1 is the alias that will refer to the DDCS Gateway and will be used by the Server, db2gw is the TCP/IP name of the DDCS Gateway machine, and inst1c is the service name defined in the step 3 above. mydb is the alias defined in step 2 above, mvsdb2 is the alias that will be used by DECS.
MDI Gateway
DECS, the LotusScript Extension for Lotus Connectors, and Enterprise Integrator include built-in support for the use of an MDI Gateway with DB2. MDI Gateway is a Sybase product that enables Sybase clients to access DB2 data.
Helvetica
Times
LotusFrute
Symbol
Times New Roman
5Courier New
This chapter provides information about setting up connectivity to an EDA/SQL data source.
RSymbol
The EDA/Client software for the host operating system. The EDA/Client version must be Release 3.2 or later and must be 32-bit on Windows NT and OS/2.
An EDA Server on the platform where the EDA supported database resides.
Connectivity to the EDA server.
Helvetica
Times
LotusFrute
Symbol
Times New Roman
5Courier New
The EDA connectivity test checks connectivity between EDA and the database. To test for connectivity:
Run the version of the test program LCTEST, located in the Domino program directory, appropriate to your operating system. See Chapter 2 for more information.
Select EDA/SQL from the program menu.
Enter the EDA Server, user name, and password as prompted. The program then attempts to connect to the EDA data source.
A message appears indicating whether the test was successful or not.
You can retry a connection by entering Y at Try Again? This provides the opportunity to re-enter all of the required information, in case a mistake was made in spelling or you gave the wrong User Name, Password or EDA Server.
Helvetica
Times
LotusFrute
Symbol
Times New Roman
5Courier New
This chapter provides information about setting up connectivity an ODBC data source.
RSymbol
The ODBC driver appropriate to the operating system.
The driver must be 32-bit on NT and OS/2.
The ODBC driver must be thread-safe.
The ODBC Administrator must be present.
There must be correctly defined ODBC data sources in that ODBC Administrator.
Helvetica
Times
LotusFrute
Symbol
Times New Roman
5Courier New
The ODBC connectivity test checks connectivity between ODBC and the database. To test for connectivity complete the following steps:
Run the version of the test program LCTEST, located in the Domino program directory, appropriate to your operating system. See Chapter 2 for more information.
Select ODBC from the program menu.
Enter the data source, user name, and password when the program prompts for them.
Choose (Y/N) whether or not you want detailed driver information.
You can produce a printed report for diagnostic purposes. When asked, you can choose to output to a file (Y) or not (N). If you do not choose output to a file, the results appear on your monitor.
If you chose file output, supply a name for the file, then press Enter. The program then attempts to connect to the ODBC data source.
A message appears telling whether the test was successful or not.
You can retry a connection by entering Y at Another Data Source?.
Helvetica
Times
LotusFrute
Symbol
Times New Roman
5Courier New
This chapter provides information about setting up connectivity to an Oracle Server.
RSymbol
With an OS/2-based Server: Oracle SQL*Net version 2.
With a Windows NT-based Server: Oracle SQL*Net version 1 or 2.
In either case, SQL*Net must be same version as SQL*Net installed on the Oracle data server. A network connection must exist between the Server machine and the Oracle data server machine via SQL*Net.
Native Oracle connectivity support requires Oracle version 7.2 or later.
OS/2 works only with Oracle 7.3.
Oracle Version 7.3 and HP-UX: You must obtain the Oracle Fix for Bug #441647. This applies patches to Oracle's libclntsh.sl.
Oracle 8: Enterprise Integrator and DECS link with Oracle 7.3 libraries, which use SQL*NET for the communications layer. If you are using Oracle 8 with DECS or Enterprise Integrator, you must install Oracle SQL*NET. You can use SQLNET Easy Config utility to configure SQL*NET.
When connecting from an Oracle 8 client to an Oracle 8 server, use of Oracle SQL*NET may be required. If you encounter access problems, install SQL*NET.
Helvetica
Times
LotusFrute
Symbol
Times New Roman
5Courier New
You should test for connectivity between the Domino Server and the Oracle servers. Complete the following steps to test connectivity:
Run the version of the test program LCTEST, located in the Domino program directory, appropriate to your operating system. See Chapter 2 for more information.
Select Oracle Server from the program menu.
When the program prompts for an Oracle User Name, Password, and Connection String, enter a valid Username and Password.
The Connection String can be for either SQL*Net V1 or SQL*Net V2, depending on what software you have configured on your Oracle Server and Domino Server.
The general format for a V1 string is network_prefix:server_name:sid.
The format for V2 consists of a single identifier, service_name.
Refer to your Oracle SQL*Net documentation for further information on the format of Connection Strings.
After entering a User Name, Password, and Connection String, the program attempts to connect to the Oracle Server.
A message appears telling whether the test was successful or not.
You can retry a connection by entering Y at Try Again? [N]. This provides the opportunity to re-enter all of the required information, in case a mistake was made in spelling or you gave the wrong Username, Password or Connection String.
Helvetica
Times
LotusFrute
Symbol
Times New Roman
5Courier New
This chapter provides information about setting up connectivity a Sybase Server.
RSymbol
With an OS/2-based or Windows NT-based: System 10 Netlib.
A network connection must exist between the Domino Server and the Sybase SQL Server via Netlib.
Helvetica
Times
LotusFrute
Symbol
Times New Roman
5Courier New
You should test for connectivity between the Domino Server and the Sybase SQL Server servers. Complete the following steps to test for connectivity:
Run the version of the test program LCTEST, located in the Domino program directory, appropriate to your operating system. See Chapter 2 for more information.
Select Sybase Server from the program menu.
Enter the server name, user name, and password as prompted. The test program then attempts to connect to the Sybase SQL Server machine.
A message appears telling whether the test was successful or not.
You can retry a connection by entering Y at Try Again? [N]. This provides the opportunity to re-enter all of the required information, in case a mistake was made in spelling or you gave the wrong user name, password or server name.
If problems persist, check to make sure you have the client software properly installed.
10/08/98 09:25:27 AM Scott Prager/CAM/Lotus deleted Scott Prager/CAM/Lotus
10/08/98 09:25:24 AM Scott Prager/CAM/Lotus updated -Default-
09/11/98 10:15:11 AM Scott Prager/CAM/Lotus updated Scott Prager/CAM/Lotus
09/11/98 10:15:11 AM Scott Prager/CAM/Lotus added Scott Prager/CAM/Lotus
(.txt)