How do I Install CDO (Collaboration Data Objects)?

J-Integra KB Admin — Tue, 22 Apr 2008 04:32:00 GMT

Abstract:

How do I Install CDO (Collaboration Data Objects)?

There are a few ways to install CDO. The method to use depends on what version of Microsoft Outlook you currently have installed (if any). Since different copies of CDO cannot co-exist on the same machine, please only follow the instructions that apply to your system configuration.

1. Microsoft Outlook is not installed

Download and install the stand-alone Messaging API (MAPI) client version available here.

2. Microsoft Outlook 2007

Beginning in Outlook 2007, Microsoft no longer provides CDO as part of the product installation. However, since Outlook is a MAPI client itself, the stand-alone version that does not come pre-packaged with the MAPI client must be used. This version of CDO can be downloaded here.

3. Microsoft Outlook 2003 and earlier

In Outlook 2003 and ealirer, CDO is bundled as a component in MS Outlook; however, it is not installed by default when you install MS Outlook. The following steps demonstrate how to install CDO as a component of Outlook using a Windows XP machine. Similar steps apply for other operating systems.

Open Add or Remove Programs under Settings > Control Panel.

Click on Change or Remove Programs on the left side bar and select Microsoft Office on the Currently Installed Programs box on the right. Then, click on Change.

Working with Custom Document Properties in Microsoft Word 2003

J-Integra KB Admin — Tue, 22 Apr 2008 03:23:00 GMT

Abstract:

Working with Custom Document Properties in Microsoft Word 2003

There is a glitch in the type library of Microsoft Word 2003 which makes it confusing for Word developers to work with Custom Document Properties programmatically. If you browse through the Word type library (MSWORD.OLB) using Visual Basic's Object Browser and look for CustomProperties, you will see that the Add function has the following signature:

Function Add(Name As String, Value As String) As CustomProperty Member of Word.CustomProperties

Note that the function accepts two string parameters. Consequently, com2java will generate the corresponding Java method for this function as follows:

public word.CustomProperty add(String name, String value)

When you then call CustomProperties.Add() from Java passing it two valid String parameters, you will get an exception from your Java client that looks as follows:

java.lang.ClassCastException: A COM object reference via iid
00020400-0000-0000-c000-000000000046 does not support COM
interface b923fde1-f08c-11d3-91b0-00105a0a19fd
at com.linar.jintegra.Dispatch.b(Unknown Source)
at com.linar.jintegra.Dispatch.vtblInvoke(Unknown Source)
at word.CustomPropertiesProxy.add(CustomPropertiesProxy.java:212)
at CustomDocProperties.main(CustomDocProperties.java:37)

When to attempt to call the same function from VB passing it 2 string parameters as required by the function signature, you will get the following error:

Run-time error '450': Wrong number of arguments or invalid property assignment

Supported JDKs and Platforms

J-Integra KB Admin — Mon, 07 Apr 2008 08:03: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
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 JDK (all other J-Integra functionality is supported).

Notes:

Only 32-bit JVMs are supported. There are no plans to support 64-bit JVMs.
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 SP2)
Microsoft Windows Server 2003 (including R2 and SP3)
Microsoft Windows Vista

Notes:

Both 32-bit and 64-bit Windows platforms are supported.

Supported Microsoft Exchange Platforms

Microsoft Exchange 5.5
Microsoft Exchange 2000
Microsoft Exchange 2003
Microsoft Exchange 2007

Questions Regarding JCOM

J-Integra KB Admin — Tue, 18 Mar 2008 07:10: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 a copy of the latest version of J-Integra from our website. A J-Integra 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-Integra runtime (i.e. jintegra.jar).

* Note: If the tools (ie, the DLLs and EXEs

Embedding a Microsoft Office Document in a Java Frame

J-Integra KB Admin — Mon, 18 Feb 2008 03:16:00 GMT
Abstract:
Embedding a Microsoft Office Document in a Java Frame

According to Microsoft Knowledge Base article 242243 and article 311765, Microsoft Office documents (including Word, Excel, PowerPoint, Project, and Visio documents) are ActiveX Document servers, not ActiveX Controls. Visual Basic does not support a native control to host ActiveX Documents. Instead, Visual Basic uses the OLE container control to embed an ActiveX Document. Therefore you cannot directly embed ActiveX Documents in a Java frame either. There are three workarounds:
1. Use the WebBrowser ActiveX Control
The WebBrowser control that comes with Internet Explorer (version 3.0 and higher) does support this form of in-place containment. It is possible to use this control to open an Office document as an ActiveX Document as mentioned in Microsoft Knowledge Base Article - 243058.
Run J-Integra's com2java tool and select C:\WINDOWS\system32\shdocvw.dll as the type library. Check the "Generate extra classes for embedding ActiveX controls in AWT components" option and use shdocvw as the package name. Generate the proxies to a subdirectory named shdocvw.
Note: Due to a method naming conflict between java.awt.Component and shdocvw.WebBrowser, you will receive the errors below when attempting to compile the generated proxies. T

Send an HTML Message

J-Integra KB Admin — Wed, 09 Jan 2008 09:27:00 GMT
Abstract:
How to Send an HTML Message
The following example demonstrates a workaround to send an HTML message using CDO (which does not support the automatic generation of HTML for HTML messages) and J-Integra for Exchange. The code below writes the HTML information to one of the Message object's fields. For more information about Field objects, please refer to the Microsoft CDO reference. Before running this code, please ensure that CDO has first been configured.
Java Application Code (HTMLTest.java):
import com.linar.jintegra.Cleaner;import com.intrinsyc.cdo.*;import java.io.*;public class HTMLTest { public static void main(String[] args) { //TODO: Change the following parameters based on your setup and configuration String domain = "domain"; String username = "username"; String password = "password"; String CDOmachine = "0.0.0.0"; String exchangeServer = "0.0.0.0"; String mailbox = "mailbox"; String tempFile = "HTMLTest.txt"; try { // authenticate to Windows com.linar.jintegra.AuthInfo.setDefault(domain, username, password); // create a Session in the CDOmachine Session session = new Session(CDOmachine); // logon to the Exchange Server session.logon(null, null, new Boolean(false), new Boolean(true), new Boolean(false), new Boolean(false), exchangeServer + "
" + mailbox); // create a message in the Outbox Integer folderType = new Integer(CdoD

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.

Retrieve the Members of a Private Distribution List

J-Integra KB Admin — Thu, 01 Nov 2007 05:35:00 GMT
Abstract:
How to Retrieve the Members of a Private Distribution List
The following piece of code demonstrates how to retrieve the members of Private Distribution List stored in a user's Contacts folder. For more information about any CDO object or method used below, please refer to the Microsoft CDO reference. Before running this code, please ensure that you have first configured CDO.
import com.intrinsyc.cdo.*;import com.linar.jintegra.Cleaner;public class RetrievePrivateDLMembers { public static void main(String[] args) { System.setProperty("JINTEGRA_RELEASEALL_SHUTDOWN_HOOK", ""); //TODO: Change the following parameters based on your setup and configuration // the logon parameters of the service account you used to configure CDO String domain = "domain"; String username = "username"; String password = "password"; // the DNS name or IP address of the machine where you installed CDO String CDOmachine = "0.0.0.0"; // the DNS name or IP address of the Exchange Server String exchangeServer = "0.0.0.0"; // the mailbox you wish to access (NOTE: this is the same as the user's login name // e.g., if the username is jsmith, mailbox would also be jsmith ) String mailbox = "mailbox"; // field and propset ids String CdoPropSetID3 = "0420060000000000C000000000000046"; String CdoContact_PrivateDLMemberIDs = "0x8054"; try { // use credentials of service account to authenticate to Windows com.linar.jintegra.AuthInfo.setDefault(domain, username, pas

Forward, Copy, or Move a Message

J-Integra KB Admin — Thu, 01 Nov 2007 05:12:00 GMT
Abstract:
How to Forward, Copy, or Move a Message
The following piece of code demonstrates how to Forward, Copy, or Move the most recent message in a user's Inbox. Each independent action (Forward, Copy, and Move) is clearly commented for ease of use and illustration. Please note that the above actions are presented together only for the sake of efficiency, and are not dependent upon one another for proper functionality. For more information about Message objects, please refer to the Microsoft CDO reference. Before running this code, please ensure that CDO has first been configured.
import com.intrinsyc.cdo.*;import com.linar.jintegra.Cleaner;public class ForwardCopyMoveMessage { public static void main(String[] args) { // TODO: Change the following parameters based on your setup and configuration // the logon parameters of the service account you used to configure CDO String domain = "domain"; String username = "username"; String password = "password"; // the DNS name or IP address of the machine where you installed CDO String CDOmachine = "0.0.0.0"; // the DNS name or IP address of the Exchange Server String exchangeServer = "0.0.0.0"; // the mailbox you wish to access (NOTE: this is the same as the user's login name // e.g., if the username is jsmith, mailbox would also be jsmith ) String mailbox = "mailbox"; try { // use credentials of service account to authenticate to Windows. com.linar.jintegra

Retrieve and Store Attachments from Messages

J-Integra KB Admin — Thu, 01 Nov 2007 04:38:00 GMT
Abstract:
How to Retrieve and Store Attachments from a Message
The following pieces of code demonstrate how to extract an attachment (either a data file or an embedded message) from the most recent message in a user's Inbox. For more information about Attachment objects, please refer to the Microsoft CDO reference. Before running this code, please configure CDO first.
Retrieving and Storing an Attached Data File:
import com.intrinsyc.cdo.*;import com.linar.jintegra.Cleaner;import java.io.*;public class GetAttachment { public static void main(String[] args) { //TODO: Change the following parameters based on your setup and configuration // the logon parameters of the service account you used to configure CDO String domain = "domain"; String username = "username"; String password = "password"; // the DNS name or IP address of the machine where you installed CDO String CDOmachine = "0.0.0.0"; // the DNS name or IP address of the Exchange Server String exchangeServer = "0.0.0.0"; // the mailbox you wish to access (NOTE: this is the same as the user's login name // e.g., if the username is jsmith, mailbox would also be jsmith ) String mailbox = "mailbox"; try { // use credentials of service account to authenticate to Windows com.linar.jintegra.AuthInfo.setDefault(domain, username, password); // create a Session in the CDOmachine Session session = new Session(CDOmachine);

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
Errors when Releasing COM Objects from Java Clients

Contents
SYMPTOMS
CAUSE
RESOLUTION
SYMPTOMS
Sometimes COM objects are not released properly by the Java client. The client itself may execute normally. Errors listed below may be present in the jintegra.log file (note that the timestamp and objRefs will be different).
995005188493 *: Received a fault (code:2147549448) in response to IRemUnknown::RemRelease request, with RPC call id 80
995005188573 *: Error releasing batched objRefs: {00000022-013f-0000-3101-000022000000=30, 00000025-013f-0000-3101-000025000000=30, 00000023-013f-0000-3101-000023000000=5, 00000026-013f-0000-3101-000026000000=5, 00000024-013f-0000-3101-000024000000=5, 00000027-013f-0000-3101-000027000000=5} AutomationException: 0x80010108 - The object invoked has disconnected from its clients. in 'Invoke'
995005188673 *: IOException reading from socket: java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read to Net={aaa.bbb.ccc.ddd[xxxx]...
995005188673 *: RPC Connection Handler waitForResponse(2) failed: connection is dead to Net={{ 0x7, aaa.bbb.ccc.ddd[xxxx]}} Sec={{ .....
995005188673 *: Error releasing all objRefs: java.io.EOFException: The DCOM connection to the remote object has been disconnected (waitForResponse2)

CAUSE

Microsoft .NET Framework 3.0 Support

J-Integra KB Admin — Wed, 18 Jul 2007 08:12:00 GMT
Abstract:
Microsoft .NET Framework 3.0 Support
Since .NET Framework 3.0 is an additive release of .NET Framework 2.0, J-Integra for .NET will work normally under a .NET Framework 3.0 environment. Installing .NET Framework 3.0 installs .NET Framework 2.0 first; therefore, there will be no compatibility issues running J-Integra for .NET (using GenService 2.0) on a computer with "only" .NET Framework 3.0 installed.
For more information regarding .NET Framework 3.0 and backwards compatibility, please refer to Microsoft's .NET Framework Versioning and Deployment Q&A here.

"bad class file. class file has wrong version 50.0, should be 4x.0."

J-Integra KB Admin — Tue, 12 Jun 2007 04:36:00 GMT
Abstract:
"bad class file. class file has wrong version 50.0, should be 4x.0."
When compiling your code using the JAR files packaged with J-Integra for COM v2.7 or J-Integra for Exchange v2.7 (excel2007.jar & cdo.jar respectively) , you may receive an error similar to the one below:
SampleProgram.java:28: cannot access com.intrinsyc.cdo.Session
bad class file: C:\Program Files\J-Integra\Exchange\lib\cdo.jar(com/intrinsyc/cdo/Session.class)
class file has wrong version 50.0, should be 48.0
Please remove or make sure it appears in the correct subdirectory of the classpath.
Session session = new Session(CDOmachine);
^
1 error
These types of errors are caused by a Java version mismatch between the compiled proxies and your runtime.
Below are a list of some of the version numbers and their corresponding Java runtimes:
Version 50.0 = Java 1.6.x
Version 49.0 = Java 1.5.x
Version 48.0 = Java 1.4.x
To resolve this issue, regenerate the proxies using com2java and compile them with your version of the Java SDK. Alternatively, you can download some precompiled proxies from our Precompiled Java Proxy JAR Files KB article.

Note: The downloadable proxies were compiled using Java 1.4, except for Excel 2007, which for compatibility reasons, was compiled using Java 1.5.

Embedding Internet Explorer in a Java Frame

J-Integra KB Admin — Fri, 08 Jun 2007 03:06:00 GMT
Abstract:
Embedding Internet Explorer in a Java Frame

This example embeds Internet Explorer inside a JFrame, navigates to an HTML document, and reads/displays the tags in the document to the command prompt. To run this example you will need the Java proxies generated from the mshtml type library, as well as the main Internet Explorer typelibrary (shdocvw.dll).
We assume that you are familiar with Java -- no COM knowledge should be required. You may wish to run through some of the more detailed step-by-step examples in the J-Integra documentation (such as the Excel example) prior to trying this example. We assume you have already downloaded and installed the J-Integra SDK.
Steps: 1. Configure your Environment 2. Download the Java proxies 3. Run the Example
Step 1: Configure your Environment
Create a new folder to where the HTMLDocumentParser.java source file will be downloaded. We assume that you have already configured your DCOM settings and environment variables such as Path and Classpath.
Step 2: Download the Java proxies
We have already generated the Java proxies needed for this example (they can be downloaded below). The two files you need to download are mshtml.zip and shdocvw.zip. Please unzip these fil

Retrieving the Global Address List (GAL) from an Exchange Server

J-Integra KB Admin — Thu, 26 Apr 2007 09:25:00 GMT
Abstract:
Retrieving the Global Address List (GAL) from an Exchange Server
The following example demonstrates how to retrieve the Global Address List (GAL) from an Exchange server using CDO. Before you try this example, make sure that you have installed J-Integra and configured the Exchange server.
For more information about the programming API of CDO, please refer to Microsoft CDO Object Model.
The related article to the right explains how to retrieving additional fields from a contact record.
import com.intrinsyc.cdo.*;
public class GALExample {
public static void main(String[] args) {
//TODO: Change the following parameters based on your setup and configuration
// the logon parameters of the service account you used to configure CDO
String domain = "mydomain";
String username = "jsmith";
String password = "password";
// the DNS name or IP address of the machine where you installed CDO
String CDOmachine = "0.0.0.0";
// the DNS name or IP address of the Exchange Server
Str

Java 6 sun.* Compilation Warnings

J-Integra KB Admin — Thu, 26 Apr 2007 09:08:00 GMT
Abstract:
Java 6 sun.* Compilation Warnings
When compiling proxies created by J-Integra for COM's java2com tool, you may receive warning messages that 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.

Windows Vista - User Account Control (UAC)

J-Integra KB Admin — Thu, 26 Apr 2007 09:03:00 GMT
Abstract:
Windows Vista - User Account Control (UAC)
Windows 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, please try disabling UAC by doing the following:
In Vista's Control Panel -> User Accounts, click on "Turn User Account Control on or off". In the next screen, uncheck "Use User Account Control (UAC) to help protect your computer" and click OK. You will be prompted to reboot your machine in order for the change to come into effect.
For more information about Windows Vista's UAC, please refer to the Microsoft Windows Vista User Account Control Step by Step Guide.

Precompiled Java Proxy JAR Files

J-Integra KB Admin — Thu, 26 Apr 2007 04:01: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)
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

Windows Error 3 occurred while using J-Integra installer

J-Integra KB Admin — Mon, 05 Mar 2007 03:15:00 GMT
Abstract:
Windows Error 3 occurred while using J-Integra installer
You may get the following error when use J-Integra installer.
"Windows error 3 occurred while loading the Java VM."
If the install package crashes when trying to invoke the JVM on your computer, it's usually an indication that your Java Runtime isn't properly configured.
In your Windows "System Properties" -> "Advanced" -> "Environmental Variables", please check that your have the Java bin folder added to your System Path.
Some variations of the path may be (depending on your installation folder and Java runtime version):
C:\Program Files\Java\JRE 1.6.0\bin
C:\Program Files\Java\JDK 1.6.0\jre\bin
If this doesn't fix the installation problem, please go ahead and download the ZIP version of J-Integra for COM: http://j-integra.intrinsyc.com/download/default.aspx?ProductId=com.
The ZIP version is no different from the installer, except that the installer automates some configuration steps for you (CLASSPATH / PATH setup, etc.). For complete installation instructions (for both the ZIP and Installer), please look here: http://j-integra.intrinsyc.com/support/com/doc/#install.html.

Running the COM Accessing Java Early Binding Example (with Events) Using a VC++ Client

J-Integra KB Admin — Tue, 20 Feb 2007 06:34:00 GMT
Abstract:
Running the COM Accessing Java Early Binding Example (with Events) Using a Visual C++ Client

The attachment, EarlyBindExample.zip, contains the COM accessing Java early binding example from the documentation, but also includes a VC++ client in addition to the VB client. To run the example with a VC++ client, do the following:
Download the attachment and extract the files to your hard disk.
Follow the instructions in the readme.txt file to setup and run the example.
To run the VC++ client, open the project file in the cxx client directory.
Select the Build->Rebuild All opti

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...
Microsoft Support: Daylight Saving Time Help and Support Center
Sun Developer Network: U.S. Daylight Saving Time Changes in 2007

Deploying Your J-Integra Application

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

Contents
Introduction
Java Accessing COM
COM Accessing Java
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

How to Access .NET Event from Java

J-Integra KB Admin — Tue, 16 Jan 2007 02:51:00 GMT
Abstract:
How to Access .NET Event from Java

There are two ways to access .NET event from Java Clients:
Registering the event listener (Java way to access event)
Using .NET events (actual .NET events) from Java, wrapping .NET events using a delegate and an equivalent interface exposed to Java
We suggest using the first way to access .NET event, because it treats the .NET event as a normal Java event (add/remove event listener). The second way involves a wrapper class around the class using the events. It’s a little rough around the edges but it works.
Note: for the attached examples, please use Janetor tool to install your J-Integra for .NET license before your test. You can find the janet.xml for each test in \java_client directory after you unzip the attached examples.
1. Registering the event listener
Please find the attached java_csharp_event.zip for this example.
A. Write the .NET Server with event handler:
using System;
using System.Runtime.InteropServices;
using System.Collections;
namespace csharp_server
{
public class Factory : MarshalByRefObject
{
private ArrayList listeners;
public Factory()
{
Console.WriteLine("Factory Created...");
listeners = new ArrayList();
}
public void addMyEventListener(ITestListener l)
{
listeners.Ad

How to Check Free/Busy Information From an Exchange Server

J-Integra KB Admin — Wed, 08 Nov 2006 08:36:00 GMT
Abstract:
How to Check Free/Busy Information From an Exchange Server
The following code demonstrates how to check someone else's schedule for Free/Busy information using J-Integra and Exchange Server's Collaboration Data Objects (CDO 1.2). It is adapted from Microsoft Knowledge Base Article - 186753. Before you run this code, you should first configure your Exchange Server
/*This example is adapted from Microsoft Knowledge Base Article - 186753HOWTO: Check Someone Else's Schedule for Free/Busy Informationhttp://support.microsoft.com/?id=186753*/import com.intrinsyc.cdo.*;import com.linar.jintegra.Cleaner;public class GetFreeBusy{ // Modify the following variables based on your specific Exchange setup static final String domain = "DOMAIN"; //make sure it's all capitalized static final String user = "username"; //username of Exchange super user static final String password = "password"; //password of Exchange super user static final String mailbox = "mailbox"; //mailbox name of Exchange super user static final String CDOmachine = "000.000.000.000"; //IP address of the CDO machine static final String server = "000.000.000.000"; // IP address of Exchange server static final String recipient1 = "joedoe"; // alias/login name of recipient public static void main (String[] arg ){ try{ // authenticate to Windows com.linar.jintegra.AuthInfo.setDefault(domain, user, password); // create a Session in the CDOmachine Session session = new Session(CDOmachine); // logon to the Exchange Server sessi

MIDL2021 duplicate id when use MIDL compile java2com generated IDL

J-Integra KB Admin — Fri, 03 Nov 2006 06:24:00 GMT
Abstract:
MIDL2021 Duplicate ID when use MIDL compile java2com generated IDL
You may get the following error when use midl.exe compile idl file generated by J-Integra java2com tool.
These midl error occur because of nested classes/interfaces. Notice that, in this case, java.io.PrintWriter extends java.io.Writer which in turn implements java.lang.Appendable. Therefore, the java2com tool generates an interface for each of java.io.PrintWriter, java.io.Writer, and java.lang.Appendable.
Because the COM IDL language does not know anything about Java inheritance, it generates 3 append method signatures for JavaLangAppendable, 6 append method signatures for JavaIoWriter, and 9 append method signatures for JavaIoPrintWriter. However, because of the Java inheritance involved, it ends up giving the same method id to the same append method signatures.
To resolve these errors, you need to use the Name Mappings option to tell java2com not to generate IDL definitions for the append() methods in java.io.Writer, and java.lang.Appendable:
Run the java2com (gui) tool.
Click Settings > Name Mappings.
On the left-hand side, click java > io > PrintWriter (its methods will appear to the right).
On the right-hand side, deselect the checkboxes beside the last 6 append methods.
Save settings and regenerate the proxies.
For more informaiton about J-

CDO Filter on AppoinmentItems

J-Integra KB Admin — Wed, 25 Oct 2006 09:36:00 GMT
Abstract:
CDO Filter on AppoinmentItems
According to Microsoft Knowledge Base Article - 192404, when filtering on a collection of Collaboration Data Objects (CDO) AppoinmentItems, the Start and End dates must be reversed to make the filter work as expected.
The following example maps the VB code in the article 192404 to Java.
VB
'You must add a Reference to Microsoft CDO version 1.21.
Set objSession = CreateObject("MAPI.Session")

objSession.Logon
Set objCalendar = objSession.GetDefaultFolder(MAPI.CdoDefaultFolderCalendar)
Set oMsgColl = objCalendar.Messages

Set oMsgFilter = oMsgColl.Filter
oMsgFilter.Fields.Add CdoPR_START_DATE, "10/1/06"
oMsgFilter.Fields.Add CdoPR_END_DATE, "9/1/06"

Set oAppt = oMsgColl.GetFirst
MsgBox oAppt.Subject

Do While (Not oAppt Is Nothing)
MsgBox oAppt.Subject
Set oAppt = oMsgColl.GetNext
Loop
objSession.Logoff
Java
import com.intrinsyc.cdo.*;
import com.linar.jintegra.AuthInfo;
public class CalendarFilter {
//TODO: Change the following parameters based on your setup and configuration
static String domain = "MYDOMAIN";
static String user = "USERNAME";
&

Search Messages and Appointments by Entry ID

J-Integra KB Admin — Wed, 18 Oct 2006 15:15:00 GMT
Abstract:
How to Search and Retrieve Messages and Appointments by their Message ID
The following code demonstrates how to search an appointment item by its entry ID. You can apply the same example in searching for other Exchange item types like messages, contacts, task, etc. For more information on message ID's, please refer to the Microsoft CDO reference. Before you run this code, you should first configure CDO.
import com.intrinsyc.cdo.*;import com.linar.jintegra.AuthInfo;/** * Created by IntelliJ IDEA. * User: fragasa * Date: 18-Oct-2006 * Time: 11:23:31 AM * To change this template use Options | File Templates. */public class GetMessageByID { //TODO: Change the following parameters based on your setup and configuration static String domain = "mydomain"; static String user = "jsmith"; static String password = "password"; static String CDOmachine = "0.0.0.0"; static String exchangeServer = "0.0.0.0"; static String mailbox = "jsmith"; public static void main (String[] arg ){ try { // Authenticate to NT domain via NTLM AuthInfo.setDefault(domain, user, password); // Start a MAPI Session Session session = new Session(CDOmachine); // Logon to the Exchange Server session.logon(null, null, new Boolean(false), new Boolean(true), new Integer(0), new Boolean(true), exchangeServer + "
" + mailbox); // Retrieve appointment items from the Calend

Accessing .NET Components From a Java Client

J-Integra KB Admin — Tue, 17 Oct 2006 02:11:00 GMT
Abstract:
Accessing .NET Components From a Java Client
This step-by-step example shows you how you can use J-Integra to access .NET components from a Java client or embed a .NET form in a Java AWT/SWING frame. If your Java client does not embed a .NET GUI component in a Java frame, you can also use J-Integra for .NET to integrate your Java/J2EE and .NET components. J-Integra for COM uses a COM Callable Wrapper to bridge Java and .NET, whereas J-Integra for .NET uses pure .NET Remoting Protocol to do the bridging.
Contents
Introduction
Configure the .NET environment
Compile and register the C# component
Add the C# component to the GAC
Create a TLB from the C# component
Generate and compile the Java proxies for the C# component
Compile and run the Java client
This example was built using the following:
J-Integra

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,

NullPointerException when Working with ActiveX Controls

J-Integra KB Admin — Thu, 17 Aug 2006 16:55:00 GMT
Abstract:
NullPointerException when Working with ActiveX Controls

When working with ActiveX controls, the control must first be displayed before invoking methods on it. If the control is not displayed first, often you will get a NullPointerException.
As an example, if com.activex.MapControl is an ActiveX component, doing something like this may cause a Null-pointer Exception:

com.activex.MapControl mapcontrol = new com.activex.MapControl();
mapcontrol.zoomIn(); // causes java.lang.NullPointerException
In this case, you may have to display the ActiveX component first, as below:

com.activex.MapControl mapcontrol = new com.activex.MapControl();

// code to display the MapControl should be placed here:
JFrame frame = new JFrame();
frame.setSize(400, 300);
frame.getContentPane().setLayout(new BorderLayout());
frame.getContentPane().add(mapcontrol, BorderLayout.CENTER);
frame.setVisible(true);

mapcontrol.zoomin(); // now it works
Notes:
(1) Actually, not all methods will cause a NullPointerException when called before the ActiveX control is displayed. Any setXX() method can be called beforehand. These setXX() methods will be queued up and automatically called once the ActiveX control is made visible.
(2) ActiveX controls hosted by J-Integra extend com.linar.jintegra.Ocx, which in turn extends java.awt.Canvas (see the generated proxies for details). All java.awt.Canvas components have a property called preferredSize. The preferredSize of any ActiveX control that is hosted by J-Integra defaults to 1

Running a Java Class as an Windows NT/2000/XP/Server 2003 Service

J-Integra KB Admin — Thu, 27 Jul 2006 03:37:00 GMT
Abstract:
Running a Java Class as an Windows NT/2000/XP/Server 2003 Service

Background
Windows 2000 and Windows NT support the concept of services. A service is a software component that runs in the background. Examples include the "Event Log" service which provides logging facilities, and the "DHCP Client" service which manages obtaining an IP address for your machine. If you have IIS on your machine, it runs as a service also.
Service states are controlled by the services control panel (on Windows 2000 select Start->Programs->Administrative Tools->Services). Services respond to a number of control commands including start, stop, pause and resume. So a service must be programmed to handle these events.
The most interesting feature of services is that they are running even when there are no users logged on. So if your application needs to run all the time, with and without users logged on, then it must run as a service.
JavaService by Alexandria Software Consulting
JavaService is an application that allows any Java class to be run as a Service. It is an open source product that was originally developed and distributed by Alexandria Software Consulting. However, the JavaService software is now hosted by the ObjectWeb source forge. It can be downloaded from here (http://javaservice.objectweb.org/index.html).
Please note that Intrinsyc Software does not provide technical support for JavaService.
We have successfully used this product to run the COM to Java bridges in our Application Server examples (suc

Knowledge Base: J-Integra

How do I Install CDO (Collaboration Data Objects)?

How do I Install CDO (Collaboration Data Objects)?

1. Microsoft Outlook is not installed

2. Microsoft Outlook 2007

3. Microsoft Outlook 2003 and earlier

Working with Custom Document Properties in Microsoft Word 2003

Working with Custom Document Properties in Microsoft Word 2003

Supported JDKs and Platforms

Supported JDKs and Platforms

Supported JDKs

Notes:

Supported Microsoft Windows Platforms

Notes:

Supported Microsoft Exchange Platforms

Questions Regarding JCOM

Questions Regarding JCOM

Updating JCOM to the latest version of J-Integra

Embedding a Microsoft Office Document in a Java Frame

Embedding a Microsoft Office Document in a Java Frame

1. Use the WebBrowser ActiveX Control

Send an HTML Message

How to Send an HTML Message

Java Application Code (HTMLTest.java):

Limiting the Range of Ports for Java-COM Communication

Limiting the Range of Ports for Java-COM Communication

Retrieve the Members of a Private Distribution List

How to Retrieve the Members of a Private Distribution List

Forward, Copy, or Move a Message

How to Forward, Copy, or Move a Message

Retrieve and Store Attachments from Messages

How to Retrieve and Store Attachments from a Message

Retrieving and Storing an Attached Data File:

Mapping VB Code to Java Code

Mapping VB Code to Java Code

Errors when Releasing COM Objects from Java Clients

Contents

SYMPTOMS

Microsoft .NET Framework 3.0 Support

Microsoft .NET Framework 3.0 Support

"bad class file. class file has wrong version 50.0, should be 4x.0."

"bad class file. class file has wrong version 50.0, should be 4x.0."

Embedding Internet Explorer in a Java Frame

Embedding Internet Explorer in a Java Frame

Step 1: Configure your Environment

Step 2: Download the Java proxies

Retrieving the Global Address List (GAL) from an Exchange Server

Retrieving the Global Address List (GAL) from an Exchange Server

Java 6 sun.* Compilation Warnings

Java 6 sun.* Compilation Warnings

Windows Vista - User Account Control (UAC)

Windows Vista - User Account Control (UAC)

Precompiled Java Proxy JAR Files

Precompiled Java Proxy JAR Files

Warning Messages When Accessing Microsoft Outlook

Using J-Integra with Eclipse

Using J-Integra with Eclipse

Windows Error 3 occurred while using J-Integra installer

Windows Error 3 occurred while using J-Integra installer

Running the COM Accessing Java Early Binding Example (with Events) Using a VC++ Client

Running the COM Accessing Java Early Binding Example (with Events) Using a Visual C++ Client

Changes to Daylight Saving Time in 2007

Deploying Your J-Integra Application

Deploying Your J-Integra Application

Contents

1. Introduction

2. Java Accessing COM

How to Access .NET Event from Java

How to Access .NET Event from Java

1. Registering the event listener

A. Write the .NET Server with event handler:

How to Check Free/Busy Information From an Exchange Server

How to Check Free/Busy Information From an Exchange Server

MIDL2021 duplicate id when use MIDL compile java2com generated IDL

MIDL2021 Duplicate ID when use MIDL compile java2com generated IDL

CDO Filter on AppoinmentItems

CDO Filter on AppoinmentItems

VB

Java

Search Messages and Appointments by Entry ID