Configuration

The various components are configured with XML files named <AssemblyName>.config using the standard .NET configuration layout. For instance the DataSplice.Integration.dll library is configured in the file DataSplice.Integration.dll.config. For the most part, these files will be configured automatically during installation and should not need to be edited by hand unless certain aspects of the default configuration are changed.

Resource Files

All of the text messages displayed by the plug-in components are controlled by resource files located in the <DataSpliceRoot>\Resources folder. These files enable the messages presented to users to be localized into different languages without needing to customize any application files.

Each module configuration file contains a ResourcePath setting that controls the folder used to lookup resource strings. The installer will set this path correctly, so it should not need to change.

Java Bridge Configuration

The connection to the MAXIMO® API is managed by the following files:

• ... \DotNetModules\DataSplice.Integration.Maximo.dll.config

This file has a MaximoServer setting that specifies the location of the MAXIMO® server from the Java side of the proxy. If the Java server is on the same machine this can be localhost, otherwise it will need to be the IP address of hostname of the MAXIMO® server.

For instance:

• ... \DotNetModules\JNBridge.config

This file specifies the location of the Java side of the bridge for the DataSplice server. This will be either the name of the MAXIMO® server, or localhost if the Java server is running on the same machine as DataSplice. The port will also need to be changed if you modify the port the Java server listens on.

For instance:

• DotNetProxy/jnbcore.properties

This file controls the settings of the Java proxy server when it starts up. The only setting that might need to be changed here is the javaSide.port option which controls the port the Java server listens on. This should only be changed if another service is already listening on the default port 8085.

Running the Java Proxy Server on the Same Machine as the DataSplice Server

If you cannot run the Java proxy on the MAXIMO® server, these steps will guide you through setting up the proxy server to run on a different machine:

• First, the correct Java runtime environment must be installed on the target server. At the time of this writing MAXIMO® used Java 1.3.1_06, but check the MAXIMO® installation for the version actually being used. Download an installer from http://java.sun.com and run it. Next, the Java RMI stubs must be copied to the target machine. It is easiest to simply grab the psdi folder in the MAXIMO® installation folder. Copy this to a local folder on the target machine (ie: C:\MaximoProxy). Copy the DotNetProxy folder from the DataSplice installation to this same local folder. If the RMI stubs have not been recompiled, follow the instructions as described above. Edit the StartProxy.bat script to reference the correct version of Java. The paths to the MAXIMO® class files should be correct. Start the Java proxy server. Finally edit the DataSplice.Integration.Maximo.dll.config and JNBridge.config files to reference the correct server names. The first file should contain the MAXIMO® server address and the second should set the server address to localhost.

MAXIMO® Configuration

The MAXIMO® assemblies have associated configuration files that control how various aspects of the system work. This section describes when they might need to be changed.

Changing the Default Username and Password Used to Connect to MAXIMO®

By default, DataSplice will pass the user credentials supplied from the remote client to connect to MAXIMO®. This typically works fine, except nothing will work when testing through the Administration Client because Admin is typically not a valid MAXIMO® user.

The DataSplice.Integration.Maximo.dll.config file contains settings for DefaultUser and DefaultPassword which can be given valid values and then will be used by the Administration Client to connect.

Mapping DataSplice Field Display Names

The MAXIMO® plug-in modules can automatically discover the settings of many values without needing explicit bindings in the Administration Client. This makes setting up the view events much simpler because there are fewer parameters to bind. However, the modules make several assumptions about the display names used in DataSplice and if these are changed the values might not get set correctly.

The configuration files for each module (InventoryModule, EquipmentModule, etc.) contain fieldNameMapping sections which control this automatic lookup. For instance, the section in InventoryModule.dll.config looks like:

The function SetPhysicalCount will automatically lookup the item number, location, bin, and lot as long as the display names match the values in the field mapping. If any of the display names are changed in the view, they will also need to be modified in the configuration files.