When defining an extension, you must select the Type from a drop-down. The following types display in the drop-down, which is defaulted to Logic.

• Logic

  Logic is the only type of extension that is supported at this time. Logic extensions define associated execution points that, when triggered, invoke the custom extension logic Java class defined by the extension name.

• Viewable

  Viewable extensions are not supported at this time.

When defining an extension, you must define the name of the extension. The name of the extension is the name of the Java class that is to be invoked when an associated execution point is triggered. When naming your extension, be sure to follow Java class naming standards such as starting with an upper case letter, using upper and lower case letters to distinguish words, no spaces, etc. Also, do not include the .java file type extension in the name of the extension. For example, if you are defining an extension to call the Java class MySpecificLogic.java, name the extension MySpecificLogic.

When defining an extension, you must select the Execution Mode from a drop-down. The following execution modes display in the drop-down, which is defaulted to Synchronous.

• Synchronous

  A synchronous extension executes and returns specified data. The calling process must wait for the extension to finish before continuing.

• Asynchronous

  An asynchronous extension executes and does not return any data, allowing processing to continue without waiting for the extension to finish.

When defining an extension, you must associate one or more execution points with the extension. Execution points are predefined combinations of a building block, process point, and action type. These execution points have "hooks" in the code that, when triggered, invoke the extension Java class. See "Identifying An Execution Point" for more information.

When defining an extension, the parameter IDs and their corresponding default names are displayed on the Extension Parameters window. The types of extension parameters are predefined for each execution point, such as String, int, etc. The corresponding default parameter names may be edited so that is has meaning to your particular usage of it.

To enable custom extensions, the following changes must be made in the gateway.ini file located in the MSLV_Home/server/appserver/gateway directory, where MSLV_Home is the directory in which the MetaSolv Solution software is installed and server is the name of the WebLogic server.

Specifying the CLASSPATH tells the framework where to find your custom extension Java class, which must reside in the path specified in the gateway.ini.

1. Save a copy of the gateway.ini file.

2. Open the original gateway.ini file for editing.

3. Add the following line at the end of [Custom] section within the file. (If your gateway.ini file does not have the [Custom] section, you need to add it.)

   • For Windows operating systems

     CLASSPATH=MSLV_Home/server/appserver/samples/customExtension;

   • For Unix operating systems

     CLASSPATH=MSLV_Home//server//appserver//samples//customExtension;

     where:

     MSLV_Home is the directory in which the MetaSolv Solution software is installed

     server is the name of the WebLogic server

4. Save and close the file.

See MetaSolv Solution Installation Guide for more information on the configuration requirements for using custom extensions.

If you have performed a full installation, these configurations are already in place. The configurations described in MetaSolv Solution Installation Guide need to be set up only if you have upgraded from a release prior to 6.0.12.