Shared Memory

The shared memory is a part of physical memory intended for common use. Programs communicate with each other through shared memory.

Shared memory results in faster access to the components loaded in shared memory. To enhance the performance of your LN system, you can load program objects and report objects into the shared memory. Before you set up and initialize shared memory, you should verify that the hardware and internal memory is sufficient.

After the installation of LN, various objects are already loaded in the shared memory. This section describes the procedure to load additional objects into the shared memory.

LN uses many DLLs; therefore, it is difficult to decide which objects should be loaded into the shared memory. Before you fill the shared memory, use measurement tools to identify which objects are frequently used and suitable to load into the shared memory.

A shared memory that is configured based on the measurement information improves the processing speed of your LN application.

For more information on shared memory, see Infor Enterprise Server Technical Manual.

  1. Activate logging

    To gather statistics on the usage of objects, start the session.

    Optionally, click Cleanup to remove the currently stored shared memory measurement data.

    Specify the time frame in which shared memory logging must take place. If you do not define a time frame, no logging is done.

    After you specify the logging parameters, click Convert to Runtime . You can only run the Convert to Runtime command on a Master Application Server.

    The measurement starts for all bshells started after the conversion is run, taking the defined time frame into account. The logged information of a bshell is stored when the bshell is closed.

    For details, see the session help.

  2. View object usage statistics

    After the period of shared memory measurement has ended, start the session.

    Use this session to view statistics on the object usage in the bshell. The session displays, among other things, the number of times an object was loaded during the measurement period. This information helps identify which objects are frequently used and should be loaded into the shared memory.

    Optionally, click Print to print a Shared Memory Object Measurement report.

    Optionally, on the appropriate menu, click Cleanup to remove the shared memory measurement data.

    For details, see the session help.

  3. Optional: Allocate shared memory for package combinations.

    Start the session and click Allocate . The session starts. Specify, per package combination, the amount of memory, in MBs, that must be allocated for object usage in shared memory.

    Note: The amount of shared memory for the package combination is unlimited if you do not allocate memory for a package combination. Or if you allocate 0 MB for a package combination.
  4. Specify shared memory data

    Start the session. In this session, you can specify shared memory data in these ways.

    Import objects from measurement

    (Recommended)

    On the appropriate menu, click Import Objects from Measurement . The session starts.

    Use this session to:

    • Import a range of program objects or report objects from the object measurements into the shared memory data.

    • Import the most frequently used objects until the allocated memory, defined in the session, is reached. To do this, you must select the Fill remaining allocated memory with most counted objects check box. The current shared memory data is deleted first, except the objects marked as Fixed.

      This option is recommended. A shared memory that is filled with the most frequently used objects improves the processing speed of your LN application.
    Import objects from DD On the appropriate menu, click Import Objects from DD . The session starts. Use this session to import a range of program objects or report objects from the Data Dictionary (DD) into the shared memory data.
    Manually add objects To manually enter objects in the grid, click New.
    Note: 
    • You can define one or more objects for a package combination. The domains and table definitions of that package combination are also loaded into the shared memory. You cannot add individual domains and table definitions.
    • Tools objects, objects of packages tt and tl, do not belong to a package combination, and are therefore stored in the dummy <empty> package combination. To create a list of Tools objects to be loaded into shared memory, leave the Package Combination field empty.
    • You can mark objects as Fixed. Fixed objects are not removed from the shared memory data when running the session with the Fill remaining allocated memory with most counted objects check box selected.

    For details, see the session help.

  5. Convert the shared memory data to Runtime

    On the appropriate menu in the session, click Convert to Runtime . You can only run this command on a host that is defined as Master Application Server (MAS).

    When the conversion is complete, click OK and close the session.

  6. Restart the shared memory

    The procedure to restart the shared memory depends on the operating system of the LN server.

    Operating System Procedure
    Windows

    To restart the shared memory:

    1. Start the Enterprise Server Service Manager.
    2. Right-click the Shared Memory Service, and on the shortcut menu, click Stop.
    3. Right-click the Shared Memory Service again, and on the shortcut menu, click Start.
    UNIX

    To restart the shared memory:

    1. Log off from LN.
    2. Log onto the LN server as user root.

    3. Specify these commands:

      # cd $BSE/bin

      # shmmnanager6.2 -k

      # shmmnanager6.2 -i

      # ./srdd_init6.2 -i