bea.com | products | dev2dev | support | askBEA |
|
e-docs > WebLogic Server > Programming WebLogic jCOM |
Programming WebLogic jCOM |
An Important Note on Terminology
Planning Your WebLogic jCOM Application
Advantages and Disadvantages of Zero-Client Deployment
Advantages and Disadvantages of Each Binding Model
The Early Binding and Late Binding Examples
Advantages and Disadvantages of Native Mode
Calling into WebLogic Server from a COM Client Application
Special Requirement for Native Mode
Calling WebLogic Server from a COM Client: Main Steps
Generate Java Wrappers and the IDL File—Early Binding Only
Enable COM Calls on the Server Listen Port
Granting Access to java.util.Collection and java.util.Iterator
Granting Access to ejb20.basic.beanManaged
Configure Other Console Properties
WebLogic Server Class Files—Native Mode Only
Obtain an Object Reference Moniker from the WebLogic Server Servlet—Zero Client Only
Generate Java Wrappers and the IDL File—Early Binding Only
Some Notes about Wrapper Files
Register the WebLogic Server JVM in the Client Machine Registry
Select Native Mode, If Applicable
Code the COM Client Application
Running COM-to-WLS Applications in Native Mode
Native Mode with the JVM Running Out-of-Process
Native Mode with the JVM Running In-Process
Calling into a COM Application from WebLogic Server
Special Requirements for Native Mode
Calling a COM Application from WebLogic Server: Main Steps
Generate Java Classes with the com2java GUI Tool
Package the Java Classes for WebLogic Server
Enable COM Calls on the Server Listen Port
Enable Native Mode, If Desired
Configure Other Relevant Console Properties
Prepare Your Server Code to Call the COM Objects
Using Java Classes Generated by com2java
Using Java Interfaces Generated from COM interfaces by com2java
A Closer Look at the jCOM Tools
Specifying the Java Package Name
The User Interface of the regjvm GUI Tool
DCOM Mode Options for the regjvm GUI Tool
Native Mode Options for the regjvm GUI Tool
Native Mode in Process Options for the regjvm GUI Tool
Advantages of Implementing jCOM 8.1