COM+ Server Setup

Table of Contents [Hide/Show]

{outline||. |. |<1>. }

Scope

The following are the tasks that need to be performed in order to configure a server to be a COM+ server. There are some links provided at the bottom of this document for an in-depth explanation of how to perform the configuration.

Setup Procedure

Operating System and COM+ Setup

The following procedure will setup the server to perform all COM+ processing.

1. Install Windows 2000, Service Pack 2 (or higher) on the server.

2. Run Windows Update (http://www.windowsupdate.com).

3. Install MDAC 2.6

4. If the calling program is on a different Windows NT domain than the server, then for each user profile under which the client app will run, create a local user account with the same username and password on the server.

5. Install IIS

a) Control Panel => Add/Remove Programs => Add/Remove Windows Components => Internet Information Services => Details button => check SMTP Service checkbox => OK button => Next button => Next button.

b) Wait for installation to complete.

6. Configure SMTP

a) Navigate to Control Panel => Administrative Tools => Internet Services Manager => Default SMTP Virtual Server => Properties => Delivery tab => Advanced button

b) Set Smart Host to your SMTP server name.

DB2 Setup

The following procedure will enable the COM+ applications to connect to the desired DB2 database(s).

1. Install DB2 7.2 (or higher) client on the server.

2. Install the lated DB2 Fixpack to resolve a known bug where DB2 fails to rollback a COM+ transaction when requested.

3. Using the DB2 Client Configuration Assistant, add database alias(es) to the database want your COM+ applications to connect to.

DB2 BLOB Support

Note: In order to enable ADO components to read and write BLOB fields into a DB2 database, the following settings should be added to the db2cli.ini file, under the catalog to Production OLA, in C:\Program Files\SQLLIB directory.

LONGDATACOMPAT=1
LOBMAXCOLUMNSIZE=33554431

Example:

; Comment lines start with a semi-colon.

[tstcli1x]
uid=userid
pwd=password
autocommit=0
TableType="'TABLE','VIEW','SYSTEM TABLE'"
LONGDATACOMPAT=1
 
[tstcli2x]
; Assuming dbalias2 is a database in DB2 for MVS.
SchemaList="'OWNER1','OWNER2',CURRENT SQLID"
 
[MyVeryLongDBALIASName]
dbalias=dbalias3
SysSchema=MYSCHEMA
 
[OLAPROD]
DBALIAS=OLAPROD
 
[OLA2]
DBALIAS=OLAPROD2
 
[OLA]
DBALIAS=OLA
 
[OLAP1000]
DBALIAS=OLAP1000
LONGDATACOMPAT=1
LOBMAXCOLUMNSIZE=33554431
 
[HOLOLA]
DBALIAS=HOLOLA
 
[OLAP4000]
DBALIAS=OLAP4000
LONGDATACOMPAT=1
LOBMAXCOLUMNSIZE=33554431
 
[TOPS]
DESCRIPTION=TOPS
DBALIAS=TOPS
 
[OLAX662]
DBALIAS=OLAX662
 
[OLAP1100]
DBALIAS=OLAP1100

Oracle Setup

The following procedure will enable the COM+ applications to connect to the desired Oracle database(s). A detailed document can be found at the URL indicated below.

http://support.microsoft.com/support/complus/mtsandoracle.asp?GSSNB=1

1. Install Oracle Client 8.1.7

2. Install patches Oracle Patch 8.1.7.1.5 or above.

3. The following registry entries under HKLM\Software\Microsoft\MSDTC\MTxOCI should be changed to enable Microsoft ODBC driver for Oracle to work properly.





4. Download and install the Microsoft Oracle Connection Stress Test Program from the following URL http://download.microsoft.com/download/transaction/Utility/1/NT5/EN-US/DTCOra.exe

5. Execute the stress test via one of the following two commands. The servicename should be as contained in the TNS file. All the tests should show as Successful.

msdtcora.exe -Uuserid -Ppassword -Sservicename

- OR -

TestOracleXaConfig.exe -Uuserid -Ppassword -Sservicename

OLA database Configuration Changes

The following configuration settings must be changed in order to allow the clients connected to perform large queries.

QUERY_HEAP_SZ

This property is by default set to below 1000 pages. (4kb per page). Production needs to be increased to 10000 pages.