| Oracle® COM Automation Feature Developer's Guide 10g Release 1 (10.1) Part Number B10116-01 |
|
|
View PDF |
| Oracle® COM Automation Feature Developer's Guide 10g Release 1 (10.1) Part Number B10116-01 |
|
|
View PDF |
This chapter provides an overview of the Oracle COM Automation installation and postinstallation configuration tasks.
This chapter contains these topics:
The Oracle COM Automation Feature package is included as part of your Oracle installation. It contains the features and demos that illustrate how to use this product to solve real-world problems.
The COM Automation package includes the following PL/SQL and Java components:
Oracle COM Automation demonstration programs
Message files (such as comus.msb)
Oracle COM Automation PL/SQL feature orawpcomVER.dll is located in the ORACLE_BASE\ORACLE_HOME\bin directory.
All other components are located in the ORACLE_BASE\ORACLE_HOME\com directory.
Note the following system requirements.
Oracle COM Automation Feature requires:
Windows NT, Windows XP, Windows 2000, or Windows Server 2003.
A functioning database on the computer before installation takes place
Any COM Automation Server: For example, the COM Automation Feature demonstrations require that you first install the applications that are used in the demonstration programs.
The Microsoft Word, Excel, and PowerPoint demos require Microsoft Office 2000 or higher.
The Messaging Application Programming Interface (MAPI) demo requires Microsoft Outlook 2000 or higher.
The demonstrations and installations are discussed in "Overview of PL/SQL Demos " and "Oracle COM Automation Feature Java Demos Overview".
For this release, the right to execute orawcom.dll to PUBLIC, which was granted for Oracle9i must be revoked. Note: in Oracle Database 10g, orawcom.dll is renamed to orawcomVER.dll where VER is the release version.
To upgrade from Oracle9i to Oracle Database 10g, do the following:
Reinstall Java classes.
Run grant.sql.
Reinstall demos.
|
See Also: "Configuring Oracle COM Automation Feature for PL/SQL" for information on re-runningcomwrap.sql |
For Oracle9i, Oracle renamed com81.dll to orawpcom.dll and for Oracle Database 10g renamed orawpcom.dll to orawpcomVER.dll where VER is the release version. Therefore, if you are migrating from Oracle8i, you must re-run comwrap.sql to continue using Oracle COM Automation Feature for PL/SQL.
To upgrade from Oracle8i to Oracle Database 10g, do the following:
Rerun comwrap.sql.
Reinstall demos.
|
See Also: "Configuring Oracle COM Automation Feature for PL/SQL" for information on re-runningcomwrap.sql |
Configuration procedures differ for PL/SQL and for Java.
To configure Oracle COM Automation Feature for PL/SQL:
Start SQL*Plus.
Connect to the database as SYSTEM.
SQL> CONNECT SYSTEM/password@net_service_name
Grant the CREATE LIBRARY privilege to the database users that will use Oracle COM Automation Feature. For example:
SQL> GRANT CREATE LIBRARY TO hr;
Connect to the user that will use Oracle COM Automation Feature and run the comwrap.sql script at the SQL*Plus prompt:
SQL> CONNECT hr/hr; SQL> @ORACLE_BASE\ORACLE_HOME\com\comwrap.sql
where ORACLE_BASE\ORACLE_HOME represents the Oracle home directory where Oracle COM Automation Feature is installed.
You will receive several ORA-04043: object XXXX does not exist messages when you run this script for the first time. These messages are normal.
To configure Oracle COM Automation Feature for Java:
Connect to the database as system using SQL*Plus. For example:
SQL> CONNECT SYSTEM/password@net_service_name
Run grant.sql with the name of the user that will be using COM Automation. You may need to capitalize all the letters in the user's name. For example:
SQL> @ORACLE_BASE\ORACLE_HOME\com\java\grant.sql HR
Run loadjava on the command prompt as follows:
loadjava -force -resolve -user hr/hr
ORACLE_BASE\ORACLE_HOME\com\java\orawcom.jar
where hr is the user that uses Oracle COM Automation Feature.
When using Oracle COM Automation Feature for PL/SQL, there are specific requirements for the listener.ora and tnsnames.ora files that are described in this section.
For Oracle COM Automation Feature for Java, no special modifications to these files are required.
Because Oracle COM Automation Feature for PL/SQL relies on listener callouts, you must configure the listener and Oracle Net remote procedure call (RPC) mechanism for the feature to work.
The following are examples of listener.ora and tnsnames.ora files that can be used with inter-process communication (IPC) to invoke external stored procedures.
|
See Also: Oracle Net Services Administrator's Guide for additional information on configuring thelistener.ora and tnsnames.ora files for external procedures |
LISTENER =
(ADDRESS_LIST =
(ADDRESS=
(PROTOCOL= IPC)
(KEY= EXTPROC0)
)
)
STARTUP_WAIT_TIME_LISTENER = 0
CONNECT_TIMEOUT_LISTENER = 10
TRACE_LEVEL_LISTENER = off
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = ORCL)
)
(SID_DESC =
(SID_NAME = plsextproc)
(PROGRAM=extproc)
)
)
PASSWORDS_LISTENER = (oracle)
EXTPROC_CONNECTION_DATA=
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=IPC)
(KEY=EXTPROC0)
)
(CONNECT_DATA=(SID=plsextproc))
)
)
An "ORA-28575: unable to open RPC connection to external procedure agent" error message indicates one of two possible listener problems.
Problem: The listener is not started.
Action: You must start the OracleHOME_NAMETNSListener service from the Control Panel or the command prompt.
To start Oracle services from the Control Panel:
Choose Start > Settings > Control Panel.
The Control Panel window appears.
Double-click Services.
The Services dialog box appears.
Find OracleHOME_NAMETNSListener in the list and verify that it has a status of Started. If it does not, select it and click Start.
To start Oracle services from the command prompt:
Enter the following command to start an Oracle service at the command prompt:
C:\> net start service
where service is a specific service name, such as OracleHOME_NAMETNSListener.
Problem: The listener is not configured correctly.
Action: You must modify the listener.ora and tnsnames.ora files.
Oracle COM Automation feature supports the use of Distributed Component Object Model (DCOM) to access remote Component Object Model (COM) objects over a network.
In order to authenticate the client's access to the remote computer, DCOM passes the appropriate security credentials to the remote computer. The remote computer validates the security credentials and allows DCOM to proceed.
These security credentials are based on the domain user's privileges associated with either the client's listener service or database service. Table 2-1, "Services That Determine Security Credentials" indicates the determining service for COM Automation for PL/SQL and Java.
Table 2-1 Services That Determine Security Credentials
| COM Automation Feature for... | Is Determined by This Service |
|---|---|
| PL/SQL | listener |
| Java | Oracle database service |
In order to use DCOM, you must configure security settings on the following:
The computer that is running the database instance
The computer that contains the remote COM object
The configuration for the computer running the database instance requires setting the listener and the database service to the same domain user.
In this procedure for setting a service to a domain user, the service to be set is selected in step 3.
You must follow this procedure twice, once to set the listener and once to set the database service. The order is unimportant.
To set a service to a domain user:
Choose Start > Settings > Control Panel. The Control Panel window appears.
Double-click Services. The Services dialog box appears.
Select the service and click Startup. The service should be either OracleHOME_NAMETNSListener or the database service.
Click the This Account radio button.
Enter the name or browse for a domain user.
Enter and confirm the password of the selected domain user.
Click OK to save the changes.
Configuring the computer containing the remote object requires using the dcomcnfg.exe tool provided by Microsoft to configure the computer's DCOM security settings.
This tool enables you to set the access permissions, launch permissions, and configuration permissions for a specific COM object or all COM objects on a computer.
Using the dcomcnfg.exe tool, set the following:
Set the DCOM security privileges so that the appropriate service (that is, listener for PL/SQL and database service for Java), operating as a domain user, has sufficient privileges to instantiate and manipulate the remote COM object.
Set the remote COM object to execute with the same privileges as the service.
If the COM object attempts to perform an action for which it does not have permission, DCOM denies the operation and returns a security violation to Oracle COM Automation Feature. It is essential that you configure the DCOM security properly and provide the Oracle database with the necessary permissions.
|
See Also: Microsoft documentation for more information on:
|
|
 Copyright © 1999, 2003 Oracle Corporation All Rights Reserved. |
|