EIM FAQ

• MethodCompiler location
• Solaris 8 Sun OS: /opt/ltx/bin/, /opt/ltx/releases/<release>/DNT/customer/bin
• CentOS 4.6: /opt/ltx/releases/<release>/i686*/bin
• Default EIM source code location
• enVision (Solaris): /opt/ltx/releases/<version>/customer/test_methods/
• enVision (CentOS 4.6): 
• Custom EIM binary location (where the compiled "evso" file is to be placed)
• enVision (Solaris): 
• /opt/ltx/releases/<version>/customer/custom_methods/DNT
• /opt/ltx/releases/<version>/customer/custom_methods/FX1
• DNT for CX testers while FX1 for FX testers but need to confirm this 
• enVision (CentOS 4.6): 
• /opt/ltx/releases/<version>/i686*/custom_methods/DNT
• /opt/ltx/releases/<version>/i686*/custom_methods/FX1
• DNT for CX testers while FX1 for FX testers 
• Command to compile EIM source code
• >MethodCompiler -t DNT/FX1 -f <file>.tmk
• Note: Some systems required you to set the full path of MethodCompiler command. 
• Specify either DNT for DX systems,  or FX1 for X-series systems
• Do's in Developing EIM 
• Don'ts in Developing EIMl
• How to Properly load an EIM into MethodTool
• enVision only loads EIM's (evso files) that are located in default EIM source code location and custom EIM binary locations.
• If you have an EIM source code and wishes to load it into MethodTool, follow this:
• open OpTool>MethodTool
• in OpTool>MethodTool>Method Directory:, specify the path where your EIM source code is located (cxx, hxx, mid, makefile, etc...)
• set OpTool>MethodTool>Edit>Tool Mode>External Interface. If you are in the right path, a pop-up will appear letting you select which EIM object to load. select which one you prefer
• press OpTool>MethodTool>Reload
• If successful, press OpTool>MethodTool>ExternalInterface and select your EIM. Press OK and your EIM will be loaded successfully