Using Shared Memory
Using the shared memory feature, rather than a proxy, allows for both the .NET and Java sides of the bridge to run in the same process. The shared memory feature automatically starts and stops both sides of the bridge. All of these features help to boost performance, and typically result in simplified configuration and management tasks.
To use the shared memory feature, follow these steps:
- Select the
Shared Memoryoption from the Communication Method section.
- Two additional path fields will be enabled.
- In the Jvm.dll Location field, identify the correct
jvm.dllfile path. This refers to the location of the Java virtual machine. Click Browse and locate the fully qualified path to thejvm.dllfile. This can either be a local copy (such asC:\oracle\ora92\jdk\jre\bin\hotspot\jvm.dll) or a mapped network location (such asN:\jre\bin\hotspot\jvm.dll, where theNdrive maps directly to theMAXIMOdirectory on the Maximo server).
Note: If using a local copy, the version of Java specified here must match that of the instance running on the Maximo server computer. - In the next field, identify the correct path for either the
psdifolder or thepsdi.jarfile. Thepsdi.jarfile is used if you have decided to use java’s jar utility. Otherwise, thepsdifolder will be used. Click Browse and correctly identify the path of thepsdifolder (if thePsdi Folderoption is selected) or thepsdi.jarfile (if thePsdi.jaroption is selected). This can be either a local copy (such asC:\MAXIMO\psdi) or a mapped network location (such asN:\psdi, where theNdrive maps directly to theMAXIMOdirectory on the Maximo server).
- Click OK.
- The configurator will check again to verify that the DataSplice Server is not running. If it is, it will display a dialog box to this effect. Click OK to close the dialog box. Then shut down the DataSplice Server to proceed.
- If older configuration settings are detected, as would be the case if the configurator has been previously run, a dialog box will be displayed. The dialog gives you the option to back up the older configuration file. Clicking Yes backs up the older settings by placing a copy of the configuration file in a time-stamp-generated subfolder within a
jnbproxybackupfolder inside the DataSplice root directory. For example, if the configuration file is backed up at 8:38:14 A.M. on August 23, 2005, the default backup path would beC:\Program Files\DataSplice\jnbproxybackup\8_23_2005_8_38_14_AM.
- If existing views are detected, a corresponding dialog box will be displayed. The dialog provides the ability to use the current views or install new ones. Click Use Current to simply use the current views. Click Install New to back up the current views and create new ones. The backed up views will be placed in a time-stamp-generated subfolder within a
backupfolder inside theViewsfolder of the DataSplice root directory. For example, if the views are backed up at 8:38:14 A.M. on August 23, 2005, the default backup path would beC:\Program Files\DataSplice\Views\backup\8_23_2005_8_38_14_AM.
- The configurator will check again to verify that the DataSplice Server is not running. If it is, it will display a dialog box to this effect. Click OK to close the dialog box. Then shut down the DataSplice Server to proceed.
- If the configuration settings are saved correctly, a successful installation dialog box will be displyed.
- Click OK to close the dialog box.
- Click Close to exit the configurator.
The next step for this configuration is to recompile the RMI stub files.
Last modified 2005-08-23 09:53 AM