Automation Reference - JMP

Application Object Reference for Automating JMP
Automating JMP through Visual C++
Automating JMP through Visual C++
Using C or C++ to create an automation client can be a long, tedious task. However, if you use the support provided
by MFC in Microsoft Visual C++, the task is considerably easier. There are several steps that must be performed in
order to get to a state where you can launch the automation server application (JMP in this case). The AutoClient
application that is included in the Visual C++ Sample directory contains some code that provides ideas on how to get
started. The Microsoft sample application CALCDRIV also shows a MFC-based automation client. CALCDRIV is
typically included with Visual C++, and on MSDN CDs.
AutoClient shows how to start up JMP and drive a Bivariate analysis and the data table. The sample is much smaller
than any of the Visual Basic samples, but the mechanics behind all the automation calls that you might want to use
are the same as the examples with Bivariate and the data table. The following steps are based on the Visual C++
Version 5.0 UI.
Steps for automating JMP
1. Create your application, either manually or through App Wizard. Specify support for OLE automation. Even if
you are not automating your own application, you need to include the OLE headers and initialization code. If
you are retrofitting an existing application, you need to make sure that you include OLE support. This usually
means including afxole.h in your application, and calling AfxOleInit() in your application InitInstance
routine. Consult the MFC OLE documentation for details about this.
2. Bring up the Class Wizard and select the Automation tab. Select the Add Class drop down list and then the
From a Type Library option. Navigate to the JMP install directory until you find JMP.TLB. Select this type
library.
3. You are prompted to confirm the classes that you want to use in your project. If you are unsure what objects (and
interfaces) that you want, select them all by Shift-clicking. Select the names for the files where the class wizard
generates interface stubs and header information. Class Wizard is generating wrapper classes based on the MFC
ColeDispatchDriver class. This gives you easy access to the OLE Invoke automation function without having to
know a lot of the technical details. Select OK. Class Wizard generates the two files (.h and .cpp). You should
include the .h file in whatever .cpp files use the JMP automation objects. For example, your View class
implementation file.
4. The Class View of your Workspace now shows the Interface classes that you have imported. You can examine the
methods and properties for each class through this class view.
5. To start JMP, define a variable of type IJMPAutoApp that persist for the length of the automation session. Call
CreateDispatch on this variable, passing in the JMP ProgID (“JMP.Application”) as the lone parameter. At this
point, when the code executes JMP starts.
6. Call SetVisible(TRUE) on the JMP object created in step 5. If you do not want to see JMP execute, do not do
this step. However, for debugging it is necessary.
7. Now you can use the JMP application object to spawn further objects, which themselves can spawn more objects.
The first thing you probably want to do is load a Data table. To load an existing JMP data table, call the
OpenDocument method on the JMP object created in step 5. If successful, this method returns a dispatch pointer
that can be attached to an object of type IJMPDoc using the AttachDispatch method.
Page 9