Lotus资料交换.doc

此文档收集于网络，如有侵权，请联系网站删除Lotus ConnectorsLotus Connectors provide native access to a wide variety of DBMS products , ODBC , the platform File system, Enterprise Resource Planning systems , and Transaction Processing systems.1, Connectivity GuideThe information provided here is related to enterprise connectivity for IBM Lotus Enterprise Integrator for Domino(LEI), Domino Enterprise Connection Services(DECS), and Lotus Connector LotusScript Extensions(LC LSX).These help topics provide information about the software required to connect to external data sources and access the data in those external sources, as well as instruction on how to use the Lotus Connector connectivity test programs DCTEST and CONTEST.Chapter 1 DCTEST and CONTESTThis chapter provides information about DCTEST and CONTEST. These programs test system and application connectivity to external data sources.OverviewAfter installing LEI or DECS, you should test your external system client connectivity using DCTEST. Once you have confirmed that your external system client connectivity is operational, you can begin the process of creating LEI or DECS Activities and Connections. However, before you execute an LEI Activity that uses one or more of these connections, you should test your connections using CONTEST. CONTEST tests that a specific Lotus connection can actually access the external system. For example, when you create a named connection using an LEI Connection Document, run CONTEST on that connection name before running any Activity that uses it.LEI and DECS are supplied with connectivity testing software. Both LEI and DECS supply the DCTEST utility, while LEI also supplies the CONTEST utility.DCTEST is a client-specific test program. It tests system connectivity to external data sources. For example, you could use DCTEST to test connectivity between your DB2 client and your DB2 server. CONTEST is a connector testing program, for use with LEI only, that tests specific LEI connections.Supported Data SourcesDCTEST and CONTEST test system connectivity to the following supported data sources:DB2、ODBC、Oracle 7、Oracle 8、OLE DB、SybaseNote The iSeries platform currently supports the Lotus Connector for DB2, Notes, ODBC, SAP R/3, File System, and Text. It also supports the LEI Metaconnectors.Testing Connectivity to External Data Sources with DCTESTDCTEST is a connectivity test that establishes whether the client data source access libraries are available and functional on the Domino server. DCTEST ensures that the communications and client software required to access a specific data source is available and properly configured. It does not test for specific product functionality.Before running DCTEST, you must install the appropriate external system client connectivity software (for example DB2, Sybase, and so on) onto the Domino server that hosts the LEI server and that also hosts the LEI Administrator. If your LEI server and Domino server are on two different machines, you must install the external system client connectivity software onto both of those machines. You do not need to install the external system client connectivity software onto your Notes client.On the iSeries, the appropriate connectivity software is automatically installed with LEI.Use DCTEST to test that your external system client connectivity software is operational. Once you have determined that it is working properly, use CONTEST (LEI only) to test specific Lotus connections prior to running LEI Activities that use them.Note LEI uses server-side browsing, not client-side browsing from the LEI Administrator. DECS uses server-side browsing, not client-side browsing from the DECS Administrator. Both LEI and DECS browse databases on the external system using client connectivity from the Domino server that hosts the LEI or DECS Administrator, not from the Notes client.When using a Domino partitioned server on a Win32 platform, you must run DCTEST from the Domino data directory in which your LEI or DECS-configured notes.ini file resides.SyntaxThe syntax for using DCTEST is as follows: ndctestRunning DCTESTFollow the steps below to run DCTEST.1. Locate the DCTEST program specific to your operating system platform in the Domino program directory. The DCTEST program has the following names for each of the associated operating system platforms：Windows (Win32) platforms ndctest.exeUNIX platforms dctestiSeries platform - RUNDOMCMD SERVER(domServer) CMD(CALL PGM(DCTEST) BATCH(*NO) where domServer is the name of a Domino server where LEI is installed.Note When working with a case-sensitive OS such as UNIX, enter the DCTEST program name using lowercase characters.Note When you use DCTEST on a UNIX platform, be sure that the shared library path points to the directory where the DCTEST utility resides. If you use the current directory as the shared library path, you will not be able to use DCTEST. Once you have completed your test with DCTEST, revert to the original shared library path setting.2. Invoke the dctest program to display the DCTEST utility instructions and choices.3. Enter the number of the test you want to run and press Enter.4. Depending on the type of external system you are testing, for example DB2, you are prompted to enter additional information as required to log in to the specified data source. After entering the external system database, user name, and password, the program attempts to connect to the external system server.5. A message appears indicating whether the test was successful or not.6. You can retry a connection by entering Y at the Try Again? N prompt. This provides the opportunity to reenter the required information.Note Testing an ODBC connection with DCTEST can provide you with information regarding the minimum version and conformance level required of ODBC drivers so that they work with LEI or DECS. To obtain this information you must respond Y when DCTEST prompts you for a full report.Testing LEI Connections with CONTESTCONTEST attempts to connect using LEI connections defined in the LEI Administrator. It tests the ability to make a connection using the information found in the LEI Connection Document. CONTEST must be run with an active LEI server.SyntaxThe syntax for using CONTEST is as follows:ncontest Options .Optionsn denotes the optional parameter: -p. This parameter displays the connector properties. denotes actual connection names (use quotation marks if spaces exist in the connection names). Typing ncontest with no input parameters results in Help information being displayed.Running CONTESTFollow the steps below to run CONTEST. 1. Open a Command Prompt/DOS window or a UNIX shell.2. Locate the CONTEST program specific to your operating system in the Domino program directory. The CONTEST program has the following names for each of the associated operating system platforms: Windows (Win32) platforms ncontest.exe、UNIX platforms contest、iSeries platform - RUNDOMCMD SERVER(domServer) CMD(CALL PGM(CONTEST) BATCH(*NO) where domServer is the name of a Domino server where LEI is installed. Note Because UNIX is case sensitive, be sure to enter the CONTEST program name using lower-case characters.3. At the command line, type the command appropriate to your platform and press Enter.Note CONTEST runs in a command window.Note Information about the connection displays when you use the optional parameter -p. When you enter ncontest without the parameter, only information about the successfulness of making the connection displays.ExamplesExample 1 (Windows platform): C:LotusDominoncontest NotesDb on MyOracleSample Output: Testing NotesDb on MyOracleNotesDb on MyOracle Connect SuccessfulExample 2 (UNIX Platform):C:lotus/dominocontest Oracle on MyOracle Sybase 11 on MySQLServerSample Output: Testing Oracle on MyOracleOracle on MyOracle Connect SuccessfulTesting Sybase 11 on MySQLServerSybase 11 on MySQLServer Connect SuccessfulChapter 2 ConnectivityThis chapter provides instructions and information for setting up and testing connectivity to the following database systems:DB2、Notes、ODBC、Oracle 7、Oracle 8、OLE DB、SybaseClient libraries of the external systems to be accessed must be installed on the LEI server and the Domino server. When running activities, if the LEI server that you want the activity to run on and the Domino server where the LEI Administrator resides are on separate machines, the client libraries must be installed on both machines.Note Access to other iSeries DB2/400 servers is integrated into OS/400. No additional software installation is required when using the Lotus Connector for DB2 on iSeries.DB2 ConnectivityThis section lists supported platforms and configurations. It also lists specific LEI activities supported by the Lotus Connector for DB2.Supported Activitiesl Direct Transfern Source/destination connectionsn Destination metadata creation (“Create Target MetaData”)l Commandl Archivel Advanced RealTime (Virtual Documents and Virtual Agents), Virtual Fields, and DECS Real Timen Create, Open, Update, and Delete eventsl Replicationl Master and Target connectionsl Scriptedl Pollingl JavaConnectivity to DB2This 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.The following DB2 product editions contain the Administration client and the Application Development client. These two items provide all the connectivity software you need for successfully connecting to a DB2 database server. The specific edition to use will depend on your environment. l DB2 Universal Database (UDB) Workgroup Edition l DB2 Universal Database (UDB) Enterprise Editionl DB2 Universal Database (UDB) Personal Editionl DB2 Connect Enterprise Edition l DB2 Connect Personal EditionFor details about these Editions, see the appropriate DB2 user documentation. For the UDB Editions, see the manual entitled Road Map to DB2 Programming, Appendix A, About DB2 Universal Database. See also the /software/network/commserver for related information. Note Only the administration client is necessary for successful connectivity to a DB2 database server.On Solaris, due to similarities between the ODBC and DB2 application program interfaces, errors are seen when using concurrent connections to ODBC and DB2 in DECS. To avoid these errors, use the ODBC DB2 driver for DB2 connections rather than the DECS DB2 Connection.Connectivity to DB2 on iSeriesThis section describes connectivity considerations between DB2 on a Windows workstation and DB2/400. None of the options described require the installation of software to the iSeries.When connecting to a DB2/400 server remotely, you must use DB2 Connect in order to specify OS/400 as the target DB2 database. The UDB Editions do not allow you to specify the target database operating system.DB2/400 is part of the base operating system on the iSeries and has support to be both a requester and server of remote DB2 requests. DB2/400 can be the target of DB2 connection requests from platforms such as NT, AIX, etc. It can also request DB2 connections to other DB2 databases in the network. DB2/400 supports both SNA and TCP/IP connections. See the Connecting to Remote DB2 from iSeries section for more details. Because DB2/400 is part of the base operating system, if you are running LEI native on the iSeries you do not need to install additional DB2 software on the iSeries. All DB2 databases being connected to, including the local DB2/400 database, must be registered in the Relational Database Directory (see WRKRDBDIRE). You can also connect to DB2 on an iSeries or mainframe using DDCS gateway.Connecting to a DB2 Data Source on iSeriesAll connections originating from the iSeries to DB2 databases (including the local DB2/400), require that the target DB2 database be registered in the Relational Database Directory on the requesting iSeries. Register DB2 data sources using the WRKRDBDIRE CL command. You can register your remote connections as either *SNA or *IP. If using SNA, communication configuration is required to connect to the remote database as described in the appropriate iSeries documentation. If using *IP, provide the target IP address or remote location name and verify that the target database is active on the designated port. The default IP port for *DRDA is 446. If the target database is another DB2/400 using a *IP connection, make sure that the DDM server job on the target iSeries is listening for the connection request. This occurs by entering a STRTCPSVR *DDM command on the target iSeries. The command starts the QRWTLSTN job on the iSeries in QSYSWRK subsystem. This job monitors the DRDA port. Note If you are connecting to a remote DB2/400, the password in the Connection Document should be in uppercase characters.Direct DB2/400 ConnectivityThis section describes direct DB2/400 connectivity considerations. One Server Connecting to DB2/400This configuration does not require the installation of software to the iSeries. You can use an *IP connection. If you are using SNA as your connection protocol, bundled with Connect Personal Edition is an SNA server. Install the SNA server with the SNA over APPC option. It must be over APPC; iSeries requires APPC for DB2 connectivity when using an SNA connection. 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 document (numbered S10J-8162-00) as a means to begin the installation. Use a user name and password that exist also on the DB2/400. This will allow the installation to perform operations on the iSeries without intervention.Multiple Servers Connecting to DB2/400This configuration does not require any software installed to the iSeries.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. You can use an *IP connection. If using SNA as your connection protocol, the Connect Enterprise Edition does not come with bundled SNA software. You must install an SNA server, such as the Microsoft SNA server. If the DB2 Connect Enterprise Edition is not installed on the machine, then a DB2 client such as DB2 Administration Client needs to be installed on the machine. This client is needed to perform the direct connection from the Domino server to DB2. Server Connecting to DB2/400 with DDCSA Distributed Database Connection Services (DDCS) and SNA server are required. This configuration does not require the installation of software to the iSeries.This configuration 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 Versions 6.1 and 7.1 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 need SNA software such as Microsoft SNA. If DDCS is not installed on the server machine, a DB2 Client such as DB2 Administration Client must be installed on the server machine. This client is needed to perform the direct connection from the server to DB2/400.ODBC DB2/400 ConnectivityODBC DB2/400 connectivity is facilitated through the DB2 client. This gives the server the advantage of straight connectivity, speed, and data type access without the ODBC layer. However, if you install products such as IBMs Client Access for iSeries, then the connectivity is through the ODBC link. Be certain to verify the requirements of the individual packages; in most cases an SNA server is still a requirement. Note This option may require that additional software be installed on the iSeries.Connection for DB2 CAE and DDCSLEI offers 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 data types not accessible through ODBC. This section contains information on configuring native DB2 connectivity through Distributed Database Connection Services (DDCS). Getting StartedNetwork 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 the Administration Client or DDCS. These communications products are available from IBM. The Administration Client is also available on your DB2 Edition CD-ROM. The machines must have connectivity through the Administration Client or a DB2 run-time environment such as DB2 server. For DDCS for Windows NT to access DRDA Application servers such as DB2 for MVS/ESA, 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 DCTEST connectivity test program.Sample Steps for DB2 Administration Client Configuration on NTThe following illustrates some sample steps you may wish to follow when configuring your DB2 connectivity using the Administration Client on NT. For full details, refer to the DB2