WebSphere Application Server Network Deployment, Version 6.1
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

             Personalize the table of contents and search results

Creating shared libraries

Shared libraries are files used by multiple applications. Create a shared library to reduce the number of duplicate library files on your system.

About this task

The first step for making a library file available to multiple applications deployed on a server is to create a shared library for each library file that your applications need. When you create the shared libraries, set variables for the library files.

Use the Shared Libraries page to create and configure shared libraries.

Procedure

  1. Go to the Shared Libraries page.

    Click Environment > Shared Libraries in the console navigation tree.

  2. Select a shared library scope.

    Change the scope of the collection table to see what shared libraries are in a particular cell, node or server.

    1. Select a cell, node, or server.

      For example, to make the shared library available to applications and servers on a cell, select a cell.

      On a Version 6.1.0.11 and later multiple-server product, you also can select a cluster. To see the cluster scope, you first must create a cluster on the Server clusters page (Servers > Clusters ). The cluster scope limits the scope of a shared library to cluster members of a particular cluster. After you create a cluster-scoped shared library and map an application to the cluster, you can associate the shared library with the application or its modules.

      To associate a cluster member server-scoped shared library with an application or its modules, you must create a shared library that has the same name for each cluster member. For example, suppose that you have cluster C with two cluster members, CM1 and CM2, and that you map the application to cluster C. If you create the my_library shared library with a cluster member server scope for CM1, you also must create the my_library shared library with a cluster member server scope for CM2. All cluster members must have a shared library with the same name to later associate the CM1 my_library shared library with your application or its modules.

      Best practice: If your multiple-server product is at Version 6.1.0.11 or later, select a cluster scope rather than create a similar shared library for each cluster member.bprac
    2. Click Apply.
    After creating a shared library, you can see whether a shared library can be used on a specific node. Select a scope to see what shared libraries are available to applications installed on or mapped to that scope.
  3. Click New.
  4. Configure the shared library.
    1. On the settings page for a shared library, specify the name, class path, and any other variables for the library file that are needed.

      If the shared library specifies a native library path, refer to Configuring native libraries in shared libraries.

    2. Click Apply.
  5. Repeat steps 1 through 4 until you define a shared library instance for each library file that your applications need.

What to do next

Using the administrative console, associate your shared libraries with specific applications or modules or with the class loader of an application server. Associating a shared library file with a server class loader associates the file with all applications on the server.

Alternatively, you can use an installed optional package to associate your shared libraries with an application.




In this information ...


Related concepts
Related reference

IBM Redbooks, demos, education, and more


Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

IBM Suggests
Task topic    

Terms of Use | Feedback

Last updated: Feb 25, 2009 9:32:38 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/tcws_sharedlib_create.html