...
| Code Block |
|---|
$ mkdir work2 $ cd work2 $ cvs co package/aida cvs checkout: Updating package/aida U package/aida/.classpath.... |
Source the Aida development setup files. Note the 2nd argument to aidaSetEnvDev.csh is the directory of your development instance of aida (what you created in the previous step):
| Code Block |
|---|
$ source /afs/slac/g/cd/soft/dev/script/ENVS.csh
$ source /afs/slac/g/cd/soft/dev/script/aidaSetEnvDev.csh dev ${HOME}/work2/package/aida
|
cd to the dp directory
| Code Block |
|---|
$ cd package/aida/edu/stanford/slac/aida/dp/ |
Create a new Data Provider (dp) directory. Then copy an existing Makefile.sun4 from one of the existing dps, on which we'll base a new one.
| Code Block |
|---|
$ mkdir dpSlcMagnet $ cd dpSlcMagnet/ $ cp ../dpSlcModel/Makefile.sun4 . |
Modify the Makefile, replacing the PACKAGE, MODULE and INTERFACENAME values with values appropriate for your new data provider.
| Code Block |
|---|
$ emacs Makefile.sun4 <edit PACKAGE, MODULE and INTERFACENAME> |
Run the Makefile.sun4; this will create all client and server sides, except the _impl.java file. You will create an _impl.java file by hand later.Ignore the jidl complaint about not finding an idl file, it's not supposed to.
| Code Block |
|---|
$ gmake -f Makefile.sun4 jidl: couldn't open /u/cd/rdh/work2/package/aida/idl/dpSlcMagnet.idl sed -e 's/THIS/dpSlcMagnet/g' .... ... |
Go to VMS, and " create the usual 43 layers of Aida directory structure", to the .DP directory. Then create you new subdirectory underneath it.
| Code Block |
|---|
> set def [.work.package.aida.edu.stanford.slac.aida.dp]
> create/dir [.dpslcmagnet]
> set def [.dpslcmagnet]
|
Create the JNI prototypes for the native methods:
| Code Block |
|---|
MCCDEV> javah -o dpslcbpm_jni.h -classpath [------] "edu.stanford.slac.aida.dp.d pSlcBpm.DpSlcBpmI_impl" |
Create your JNI interface module (the C code that the java calls). By convention we call this module dp<servername>_jni.c. It must have the *ATTRIBUTES*=JNI at the top so cmp knows how to compile it, and it should include the output file from the step above. Eg:
| Code Block |
|---|
/*
**MEMBER**=SLCLIBS:AIDASHRLIB
**ATTRIBUTES**=JNI
*/
#include "dpslcbpm_jni.h"
|
Create the dp<servername>_jni_helper.c file. This is the module that defines the functions that access the control system. The names of the functions it *defines* must all be in upper-case (due to the compiling and linking configurations specified in slccom:compile.com and the build com files). But the functions that those function call (in the control system shareables), need not be in upper-case.
...
| Code Block |
|---|
MCCDEV> lib/create aidashr_devlib.olb MCCDEV> cinc *.c |
Create an aidashr_xfr_alpha.opt. Due to namemanging of JNI and VMS linking
namespace restrictions, it's important to do this with java$jni_example:scan_globals_for_option.com.
| Code Block |
|---|
MCCDEV> libr/extract=dpslcbpm_jni/output=dpslcbpm_jni aidashr_devlib MCCDEV> @java$jni_example:scan_globals_for_option *.obj aidashr_xfr_alpha.opt |
Link your aidashr, using the opt file created above. You may also need to use a locally modified version of AIDASHR_XFR_ALPHA.OPT if you are using shareables AIDA hasn't used before.
| Code Block |
|---|
MCCDEV> buildtest aidashr /default |
Run the server. The java command to run an AIDA server takes several arguments, to pass the values of
environment variables to the server at startup, so we have little .com files for each server. To override the default classpath (JAVA$CLASSPATH) which points to the aida.jar in slcimage, and the default AIDASHR (in SLCSHR), redefine the logicals before running the START<server>.COM file:
| Code Block |
|---|
MCCDEV> define myjava$classpath [------] MCCDEV> testshrx/define/default aidashr MCCDEV> @startdpslcbpm |