Routing tab  Notes tab

Chapter 4: Configuring Applications

Advanced tab

  1. Select the Advanced tab.

  2. External Libraries – use this option when the ODL code within the SFM makes calls to custom C or C++ code through a bridged library created using BIDL.

    Click Add to add the library to the list. Click Delete to remove a selected library from the list. Click Modify to change the name of a selected library.

  3. Configure Custom Keys. Custom keys are available for most applications, including SFM. Custom keys entered here persist in the application configuration file. Custom keys are often used to statically define routing, debugging, or other resource configuration properties. Applications cannot alter custom key values. A custom key is read by an ODL application using clGetConfig. For example:

    string sAppDebug;
    
    sAppDebug="";
    
    clGetConfig("APP.Debug",&sAppDebug);
    

    In this example, the custom key APP.Debug belongs to the APP group (custom keys are defined in groups). The value is read from the application’s configuration file every time the application is enabled. A custom key is read by a Java application using getConfigValue. For example:

    String sAppDebug="";
    
    sAppDebug = getConfigValue("APP.Debug");
    

    Click New below the Custom Keys Info box. These commands are available:

    Click the Add button within the Custom Keys Add box, then click the window’s Add button.

  4. Go to the ‘sfmayt’, ‘sfmproc’ DFC Flavors box. Use this option to declare the entry points using the sfmayt and sfmproc functions when this SFM is the target to receive data from another SFM (also referred to as “SFM-to-SFM communication”).

    Click Add to add your entry to the list.





Copyright © 2005. Sybase Inc. All rights reserved. Notes tab

View this book as PDF