Knowledge Base: J-Integra : J-Integra for COM : INFO

Supported JDKs and Platforms

J-Integra KB Admin — Wed, 12 Aug 2020 08:08:00 GMT

Abstract:

Supported JDKs and Platforms

All J-Integra products are supported on the following JDKs and Platforms. Customers are also using our J-Integra products on additional JDK/Platform combinations not listed below, including non-Windows platforms such as Linux. If you experience technical issues with any JDK/Platform not listed below, please contact support and we will take all commercially reasonable steps to support it.

Supported JDKs

Sun Microsystems JDK 1.2
Sun Microsystems JDK 1.3
Sun Microsystems JDK 1.4
Sun Microsystems JDK 5
Sun Microsystems JDK 6
Oracle JDK 7-14
IBM JDK 1.3*
IBM JDK 1.4

* Embedding ActiveX controls will not work with IBM's JDK 1.3.x because it does not support Sun's AWT Native Interface (jawt.dll). However, this is the only limitation with this version of the IBM JDK (all other J-Integra functionality is supported).

Notes:

EJB 3.0 (specifically "annotations") is not supported.

Supported Microsoft Windows Platforms

Microsoft Windows NT 4.0 (including SP6)
Microsoft Windows 2000 (including SP4)
Microsoft Windows XP (including SP3)
Microsoft Windows Server 2003 (including R2 and SP2)
Microsoft Windows Server 2008 (including R2 and SP2)
Microsoft Windows Server 2012 (including R2)
Microsoft Windows Vista (including SP2)
Microsoft Windows 7
Microsoft Windows 8 and 8.1
Microsoft Windows 10 (see note below)

Notes:

Both 32-bit and 64-bit Windows platforms are supported.
Windows 10 1809+ requires a workaround to support certain DCOM configurations. See this KB artic

Windows - User Account Control (UAC)

J-Integra KB Admin — Thu, 03 Jan 2013 03:40:00 GMT

Abstract:

Windows - User Account Control (UAC)

Windows (starting with Vista) introduced a new security component known as User Account Control (UAC) that is designed to help prevent malicious programs from silently installing and computer-wide infections from occurring. With UAC enabled, an account with administrative privileges runs applications as a standard user unless the application has been approved to run at an "elevated" level.

If you are experiencing problems running J-Integra on Windows (Vista or later), please try disabling UAC by doing the following:

In (Windows 7) Control Panel -> User Accounts -> User Accounts, click on "Change User Account Control settings". In the next screen, drag the slider to the bottom and click OK. You may be prompted to reboot your machine in order for the change to come into effect.

For more information about Windows UAC, please refer to the User Account Control Step-by-Step Guide.

Precompiled Java Proxy JAR Files

J-Integra KB Admin — Mon, 22 Nov 2010 02:00:00 GMT

Abstract:

Precompiled Java Proxy JAR Files

We have provided the following proxy JAR files for your convenience. These JAR files contain Java proxy files for specific COM applications (already generated by com2java, compiled, and JAR'd). Using these JAR files allows you to avoid having to generate and compile the proxy files manually.

Feel free to download any JAR file below you wish to use. To use a proxy JAR file, simply unzip the corresponding zip file and place it in your Java application's CLASSPATH.

activeds.jar - Microsoft Active Directory Library

access2003.jar - Microsoft Access 2003 (11.x)

access2007.jar - Microsoft Access 2007 (12.x)

cdo.jar - Microsoft Collaboration Data Objects, CDO 1.2.1 v6.5.7233

cdo2007.jar - Microsoft Collaboration Data Objects, CDO 1.2.1 v6.5.7888

excel2000.jar - Microsoft Excel 2000 (9.x)

excelXP.jar - Microsoft Excel XP (2002 10.x)

excel2003.jar - Microsoft Excel 2003 (11.x)

Improving J-Integra's Performance When Accessing Bloomberg® Software

A number of customers have commented that their system performance takes quite a hit when using J-Integra to access Bloomberg® software. From the feedback we have received, we have gathered together some recommendations which may help improve overall performance.

1. The first thing you should do is upgrade to the latest version of J-Integra. Each new release contains many bug fixes and performance enhancements. You can download this version from our website.

2. If you are currently running in DCOM mode, we suggest that you run in Native mode, as this will improve the performance significantly. To run in Native mode, you need to include a command line property when you run your Java client...

java -DJINTEGRA_NATIVE_MODE MyClient

3. Because the Bloomberg® software can pass back huge amounts of data in one transaction, an upgrade of the machine running J-Integra may be necessary. However, even though an upgrade may provide enough extra memory to keep the application from crashing, there will still be a significant performance hit.

4. Besides the fact that the Bloomberg® software can pass large amounts of data back to Java in a single transaction, the other reason it causes such a performance hit is because the data that is passed back is often carried in a two-dimensional array of Variants. This is fine when you are accessing this data from a Visual Basic client, as Variants are inherent to VB. But there is no such thing as a Variant in Java, so J-Integra must convert every one of these COM Varian

J-Integra and ADO Disconnected Recordsets

J-Integra KB Admin — Tue, 08 Sep 2009 05:32:00 GMT

Abstract:

J-Integra and ADO Disconnected Recordsets

SYMPTOMS

Using disconnected Recordsets in DCOM mode is not supported by J-Integra's DCOM mode. For example, you may one of these error messages below.

java.lang.NullPointerException
AutomationException: 0x800a0e78 - Operation is not allowed when the object is closed. in 'ADODB.Recordset'

For instance, if you have a Java client accessing VB program, the VB functionGetConnectedRecordset() can be successfully invoked from Java but the VB function GetDisconnectedRecordset() will fail.

Public Function GetConnectedRecordset() As ADODB.Recordset
Dim c As ADODB.Connection
Set c = New Connection
c.Open "driver=Microsoft Access Driver (*.mdb);dbq=C:\\pure\\products.mdb", , , -1
Set GetRecordset = c.Execute("SELECT * FROM Products", , -1)
End Function

Public Function GetDisconnectedRecordset() As ADODB.Recordset
Dim rs As New ADODB.Recordset
rs.Open
Set GetRecordset = rs
End Function

CAUSE

J-Integra does not supp

Using J-Integra with a Firewall or Load Balancer

J-Integra KB Admin — Mon, 10 Aug 2009 03:16:00 GMT

Abstract:

Using J-Integra with a Firewall or Load Balancer

1. Introducation

You may still get one of these errors after configuring DCOM if you use J-Integra in DCOM mode with firewalls or load balansers:

AutomationException: 0x80070005 - General access denied error
AutomationException: 0x5 - Access is denied

There are some limiations in DCOM itself involving firewalls or load balancers. This is not caused by J-Integra and happens in all DCOM applications including VB and VC++ programs.

2. Non-NAT Based Firewalls

J-Integra uses DCOM, layered over TCP/IP to talk from a Java client to a COM component. A DCOM application needs to open a socket to port 135 on the NT box to send a DCOM "remote activation" request to the DCOM SCM (a k

Will J-Integra Support any COM Component that has a Type Library

J-Integra KB Admin — Fri, 17 Jul 2009 03:00:00 GMT

Abstract:

Will J-Integra Support any COM Component that has a Type Library?

Unfortunately, unless you are very familiar with MIDL (the common language that Microsoft uses to expose COM to other programming languages), the best way to find out is to try your component with J-Integra. We can, however, provide a more technical answer to this question.

The answer has to do with marshalling - or the packaging/unpackaging of parameters/method calls across the wire to the actual object. There are three types of marshalling that COM uses - type library marshalling, standard marshalling and custom marshalling.

Type Library Marshalling

Type library marshalling means that a COM component exposes it's functionality through a type library file, which is basically a file that describes what parameters every exposed method accepts and what its return value is using MIDL. Type libraries are either included (embedded) in the DLL/OCX/EXE, or come as a separate '.TLB' file. The requirement for type library marshalling, also known as automation marshalling, is that interfaces must derive from IDispatch, and all parameters must be automation compatible. This is the type of COM component that J-Integra works with. The com2java tool will create Java "proxies" by reading in this type library, so that the Java developer can make calls in to the component via Java.

Standard Marshalling

Standard marshalling also requires a type library, but the interfaces and their parameter types are allowed more freedom - they do not necessarily have to be automation compatible (and interfaces do not have to derive from IDispatch). The cost of this however, is that proxy/stub DLL's need to be regi

Using the J-Integra Logging Mechanism

J-Integra KB Admin — Thu, 30 Oct 2008 03:58:00 GMT

Abstract:

Using the J-Integra Logging Mechanism

By default, J-Integra does not log any messages to a file. If this is desired for your application, we advise you to use the jintegra_reduced_logging.jar runtime file instead of jintegra.jar. Simply include jintegra_reduced_logging.jar in your Classpath instead of jintegra.jar. This will result in better overall performance. However, if you require some form of logging you will have to use the jintegra.jar runtime file.

Turning on J-Integra Logging

There are two methods you can use to turn on J-Integra logging:

Setting Java Properties During Runtime

  java -DJINTEGRA_LOG_FILE="c:\temp\jintegra.log" -DJINTEGRA_LOG_LEVEL=3

Setting Java Properties in Source Code

Public static void main(String args[]) {
  System.setProperty("JINTEGRA_LOG_FILE", "c:\\temp\\jintegra.log");
  System.setProperty("JINTEGRA_LOG_LEVEL", "3");
  ...
}
Public static void main(String args[]) {
  com.linar.jintegra.Log.logImmediately(3, "c:\\temp\\jintegra.log");
  ...

Description of Logging Levels

There are four possible logging levels:

  SILENT  = 0  Does not create a log file
  ERROR   = 1  Only logs the errors
  BRIEF   = 2  Reports only significant events
  VERBOSE = 3  Reports everything

Whenever sending logs to J-Integra Support, a logging level of VERBOSE should be used.

Questions Regarding JCOM

J-Integra KB Admin — Tue, 22 Jul 2008 03:21:00 GMT

Abstract:

Questions Regarding JCOM

JCOM is a version of J-Integra which BEA ships with their WebLogic Server (WLS). They have licensed the J-Integra source code and integrated it into WLS. BEA has asked that all JCOM support requests go through BEA Support (not through J-Integra Support). So if you wish to use the WLS version of J-Integra (JCOM), then you will have to send JCOM support requests to BEA directly.

Updating JCOM to the latest version of J-Integra

The JCOM classes that are shipped with WLS are based on older versions of J-Integra. If you wish to test your JCOM application with the latest version of J-Integra (e.g. to see if there are any differences in functionality), do the following:

1. Download and install a copy of the latest version of J-Integra from our website. Simply ignore the 30-day evaluation license. J-Integra is fully functional and a production license is not required if you have a valid WebLogic license.

2. Update the startWebLogic.cmd startup script by adding a JINTEGRA_HOME variable and prefixing the CLASSPATH with the jintegra.jar. The jintegra.jar must be placed in front of the WEBLOGIC_CLASSPATH in order to ensure that the updated classes will be used instead of the ones in weblogic.jar (WLS 8.1 and earlier) or jcom.jar (WLS 10.0).

* Note: If you are using the examplesServer on WLS 8.1, you need to update the startExamplesServer.cmd script instead.

3. Add a system PATH variable that places the J-Integra \bin directory in front of the existing PATH. Doing so ensures that the updated J-Integra tools (i.e. jintmk.dll, ntvinv.dll, etc.) are used instead of their JCOM \bin directory counterparts. This also ensures that the tools are the same version as the J-

Limiting the Range of Ports for Java-COM Communication

J-Integra KB Admin — Tue, 18 Dec 2007 06:22:00 GMT

Abstract:

Limiting the Range of Ports for Java-COM Communication

The following example scenario (Java client accessing a COM component on remote machine) will demonstrate how to do this.

You'll need to experiment with the JINTEGRA_LOCAL_PORT_START and JINTEGRA_LOCAL_PORT_END properties on the Java side to limit the range of ports the client uses.

On the server side, you'll need to limit the port range for the COM component. To do this:

Launch DCOMCNFG
Click on the Default Protocols tab
Click on Connection-Oriented TCP/IP
Add the required port range (note that this setting will be used for all components - we are unsure if there is a way to specify for a single component).

This should now limit both servers to the specific port range.

Mapping VB Code to Java Code

J-Integra KB Admin — Tue, 04 Sep 2007 04:45:00 GMT

Abstract:

Mapping VB Code to Java Code

Because the Java proxies generated by com2java tool are simply mapped from the original COM programming API, you need to refer to the original documentation of the COM API to understand what each corresponding Java proxy does. The comments in the Java proxies are based on the comments found from the COM IDL file. The easiest way to start programming Java source code (which uses J-Integra for COM to access a COM component) is to find a VB example first, and then map the VB code to Java. This article covers some basic principles to map VB code to its equivalent Java code.

Object
1.1 Creating a New Object
1.2 Retrieving an Existing Active Object
1.3 Casting an Object into Another Object
1.4 Embedding an ActiveX Control sun.* packages are "Sun proprietary API and may be removed in the future."
Normally, sun.* packages should never be used by developers since they may change in future releases. Direct calls to the sun.* packages are not guaranteed to work on all Java-compatible platforms and thus are not supported by Sun. Please see the Sun article, "Why Developers Should Not Write Programs That Call 'sun' Packages", for more details.
However, since J-Integra for COM's java2com tool creates a one-to-one mapping to Java packages, references to sun.* packages need to be made. This will not impact the functionality of J-Integra. If you're experiencing problems with the generated proxies, please try regenerating them using the same Java version as your runtime. This will ensure that the proxies make reference to the same "versions" of the sun.* packages as your runtime.
Unfortunately, these warnings cannot be suppressed at compile time. Please see Sun Bug 6476630 for more information regarding these warnings.

Warning Messages When Accessing Microsoft Outlook

J-Integra KB Admin — Wed, 18 Apr 2007 03:10:00 GMT

Abstract:

Warning Messages When Accessing Microsoft Outlook

When sending messages in Outlook via J-Integra, you will get a warning message saying that a program is trying to automatically send e-mail on your behalf.

Note that this is a security design of Outlook and has nothing to do with J-Integra. You will get the same warning message if the application accessing Outlook is written in pure VB. Here's an excerpt from MSDN regarding programmatic behavior of Outlook:

If other applications try to use Outlook on your behalf, you receive a warning message and you are prompted to confirm what the other application is doing. You receive warning messages when another application tries to do anything in the following list:

Send mail on your behalf
Access your address book
Access e-mail names from your messages
Access e-mail information from your contacts or other types of items
Save your messages to the file system
Search your messages for content
Use Simple Messaging Application Programming Interface, Simple MAPI, to send messages without your consent

One workaround is to install third-party software that handles these pop-up messages. Hereí»s a link to one of them: http://www.contextmagic.com/express-clickyes/

A better workaround might be to use CDO (Collaboration Data Objects) via J-Integra for Exchange. CDO exposes objects and

Using J-Integra with Eclipse

J-Integra KB Admin — Thu, 12 Apr 2007 03:54:00 GMT

Abstract:

Using J-Integra with Eclipse

Eclipse is an IDE developed by www.eclipse.org. It uses its own environment variables instead of using the PATH and CLASSPATH variables defined by the system. In order to use J-Integra within Eclipse, you need to add jintegra\lib\jintegra.jar in Eclipse's classpath and include jintegra\bin in Eclipse's java.library.path. To do this:

Right click on your project and then click on "Properties" or select the menu "Project" and click on "Properties".
Go to "Java Build Path" and then click on the button "add External JARs...". Select the jintegra.jar located in the C:\jintegra\lib\
Add C:\jintegra\bin to the java.library.path by going to Run -> Runí¡ . Select the Arguments tab and under VM arguments, add the variable -Djava.library.path=C:\jintegra\bin

Changes to Daylight Saving Time in 2007

J-Integra KB Admin — Thu, 15 Feb 2007 06:59:00 GMT

Abstract:

A number of our customers have been asking us if J-Integra is affected by the upcoming changes to Daylight Saving Time. The short answer is no - J-Integra will not be affected by these changes and you will not need to update your J-Integra software. As long as your Windows and Java underlying systems (and applications, if necessary) are properly updated, J-Integra will simply pass the correct date/time information bi-directionally between applications.

For more information on how Windows and Java systems are affected by the changes, please see the following links...

Deploying Your J-Integra Application

J-Integra KB Admin — Fri, 09 Feb 2007 08:14:00 GMT

Abstract:

Deploying Your J-Integra Application

1. Introduction

There are many ways to use J-Integra. The following tables will help figure out which files need to be deployed in the various application scenarios. J-Integra offers two modes: DCOM Mode and Native Mode.

2. Java Accessing COM

* Indicates the tool is required for configuration, but not used at runtime.

Mode

Client

Server

DCOM

Java client app
Java proxy files (generated by com2java)
jintegra.jar or jintegra_reduced_logging.jar
If using native authentication:
- ntvauth.dll
- ntvauthEnglishResourceDll.dll

COM server app
setdllhost.exe*
setdllhostEnglishResourceDll

Mapping COM Currency Types to Java and Java Long Values to COM

J-Integra KB Admin — Thu, 21 Sep 2006 05:09:00 GMT
Abstract:
Mapping COM Currency Types to Java and Java Long Values to COM
?
There is occasionally confusion about how to map COM Currency types to Java, and how to map Java long values to COM.
COM Currency in Java
Internally, the Currency data type is actually a 64-bit integer. However, COM languages such as VB, ASP, and Delphi scale such values down by a factor of 10,000 to produce four digits after the decimal point. So, although the data type is a 64-bit integer, COM languages will display the value of any Currency-type variable as having a decimal point followed by four digits. For more details, see the J-Integra documentation.
Therefore, in order to display a 64-bit value correctly in a Java application, you must first divide the result by 10,000. This will shift the decimal point, resulting in the display of the actual value. This is a COM specification and the problem is not caused by J-Integra.
This behavior is by design, although we appreciate it isn't obvious. We didn't want to run the risk of losing accuracy by mapping a fixed point value (currency) to a floating point value (double), which at first glance might be the obvious mapping. Using a long was the only option.
Java long in COM
The long data type in Java is mapped to the Currency type in Visual Basic. This is because in Java a long is a 64-bit data type, while in Visual Basic, a long is a 32-bit data type. The only 64-bit data type in Visual Basic is a Currency.
The following information was found on www.vbapi.com (as of August 2, 2002):
"Internally,

Knowledge Base: J-Integra : J-Integra for COM : INFO

Supported JDKs and Platforms

Supported JDKs and Platforms

Supported JDKs

Notes:

Supported Microsoft Windows Platforms

Notes:

Windows - User Account Control (UAC)

Windows - User Account Control (UAC)

Precompiled Java Proxy JAR Files

Precompiled Java Proxy JAR Files

Improving J-Integra's Performance When Accessing Bloomberg® Software

J-Integra and ADO Disconnected Recordsets

J-Integra and ADO Disconnected Recordsets

Contents

SYMPTOMS

CAUSE

Using J-Integra with a Firewall or Load Balancer

Using J-Integra with a Firewall or Load Balancer

Contents

1. Introducation

2. Non-NAT Based Firewalls

Will J-Integra Support any COM Component that has a Type Library

Will J-Integra Support any COM Component that has a Type Library?

Type Library Marshalling

Standard Marshalling

Using the J-Integra Logging Mechanism

Using the J-Integra Logging Mechanism

Turning on J-Integra Logging

Description of Logging Levels

Questions Regarding JCOM

Questions Regarding JCOM

Updating JCOM to the latest version of J-Integra

Limiting the Range of Ports for Java-COM Communication

Limiting the Range of Ports for Java-COM Communication

Mapping VB Code to Java Code

Mapping VB Code to Java Code

Warning Messages When Accessing Microsoft Outlook

Warning Messages When Accessing Microsoft Outlook

Using J-Integra with Eclipse

Using J-Integra with Eclipse

Changes to Daylight Saving Time in 2007

Deploying Your J-Integra Application

Deploying Your J-Integra Application

Contents

1. Introduction

2. Java Accessing COM

Mapping COM Currency Types to Java and Java Long Values to COM

Mapping COM Currency Types to Java and Java Long Values to COM

COM Currency in Java

Java long in COM