|Oracle® Services for Microsoft Transaction Server Developer's Guide
11g Release 1 (11.1) for Microsoft Windows
|PDF · Mobi · ePub|
This chapter contains these topics:
Note:The Microsoft application demo is not included with Microsoft Transaction Server on Windows 2000, Windows XP, or Windows Server 2003.
You can use the Oracle Call Interface (OCI) with the sample banking application demo that Microsoft provides with Microsoft Transaction Server. In most cases, OCI is automatically integrated with the Microsoft application demo. Determine if OCI and the Microsoft application demo are integrated, and what you can do if they have not been integrated.
If the Microsoft Transaction Server is already installed when you install OraMTS, then the Oracle Universal Installer automatically backs up and substitutes several Visual C++ files of the banking demo with files that integrate the
oramts.dll files. This enables you to use OCI with the banking demo.
If the Microsoft Transaction Server is not installed when you install OraMTS, then do the following:
Install Microsoft Transaction Server.
vcacct.dll file in
\oramts\samples\account.vc\release to the directory listed in Step 2.
The Microsoft application demo is installed in the
oramts\samples\account.vc directory and is an OCI implementation of the Visual C++ Sample Bank package that ships with Microsoft Transaction Server. The demo component uses the user account
scott and password
tiger to connect to a database whose net service name is
mtsdemo. You can change this information in the
oramisc.h file. The demo also uses
These tables are part of the user
scott schema in the default Oracle Database created during installation.
See Also:Unlocking the Sample Tables in SQL*Plus User's Guide and Reference for more information on unlocking the sample schemas
If the default database is not being used, or the database does not include the user
scott, create the tables required to run the sample banking Microsoft application demo in the relevant user's schema.
To ensure the database includes the proper tables, determine if the database includes the proper tables:
If you create the database automatically (using the General Purpose, Transaction Processing, or Data Warehouse database configuration type of Oracle Universal Installer or Database Configuration Assistant) or manually (using a custom SQL script, and then explicitly running the
scott.sql script followed by the
omtssamp.sql script), then the database includes the proper tables.
If you create the database by manually using a custom SQL script and do not run
omtssamp.sql against the database, using the
DATABASE syntax in SQL*Plus line mode, or in any available method on Solaris or any other operating system, then the database does not include the proper tables. Perform steps 0 through 6 in this section before proceeding to "Running the Microsoft Application Demo".
If the database does not include the proper tables, you must create them manually.
To manually create the proper tables:
C:\> sqlplus /NOLOG
Connect to the database:
SQL> CONNECT username Enter password: password@net_service_name
net_service_name is the net service name that connects to the database. If you connect to the database with a username other than
scott, you must change the username and password in
oramisc.h and rebuild
SQL> CREATE USER mtsdemousr IDENTIFIED BY mtsdemousr_password;
This creates the user
mtsdemousr, which runs the Microsoft sample application.
Assign the following roles to user
SQL> GRANT CREATE SESSION,RESOURCE TO mtsdemousr;
SQL> CONNECT mtsdemousr Enter password: mtsdemousr_password@net_service_name
This creates the
receipt tables in the schema of user
This section describes how to run the Microsoft application demo:
Ensure that you have installed the Sample Bank Client application shipped with Microsoft Transaction Server. The sample component DLLs are typically installed under
Back up the file
vcacct.dll installed under
vcacct.dll with the one you built in step 3.
From the Start menu, choose Programs, then Windows Option Pack, then Microsoft Transaction Server, then Bank Client.
This starts the Sample Visual Basic bank application and runs
vbbank.exe to test the component.
Click the Visual C++ radio button of the Language field.
Click the Account or the MoveMoney radio boxes under the Component field.
Enter the account numbers and the amount for the operation.
C:\> sqlplus /NOLOG
SQL> CONNECT scott Enter password: tiger
Verify the success of the operation:
You can use Oracle Open Database Connectivity (ODBC) Driver 11g Release 1 (11.1) with the Microsoft sample application.
See Also:"Programming with Microsoft Transaction Server and an Oracle Database" for instructions on integrating the Oracle ODBC Driver with the sample application
You can use Oracle Provider for OLE DB 11g Release 1 (11.1)with the Microsoft sample application.
See Also:Oracle Provider for OLE DB Developer's Guide for information about using Oracle Provider for OLE DB with Microsoft Transaction Server