8.6.1.2 Configure WebSphere Shared Library to Support Jersey 2x and Jackson 2.9x Libraries

Perform the following configuration to set the WebSphere shared library to support jersey 2x and Jackson 2.9x libraries.

1. Click Environment from the menu on the left to expand and view the list. Click Shared Libraries to open the Shared Libraries window.

   Figure 8-1 WebSphere Shared Libraries

   
   

   

   
   
2. Enter the following details:
   • Name : Enter a uniquely identifiable name.
   • Description : Enter a valid description.
   • Classpath : Enter the absolute path where the JARs related to Jersey 2.x and Jackson 2.9x are copied. These jars are available in the <OFSAA_HOME>/ficweb/webroot/externallib/WEBINF/lib/ directory after creation of the EAR file. Another format of representation of the path is <ofsaa_deployed_area_location>/externallib/WEBINF/lib/.
3. Select Use an isolated class loader for this library.
4. Click OK to save to master configuration.
5. Select the application or module and map the shared libraries. Click OK.

   In the following figure, ofsa is selected.

   Figure 8-2 WebSphere Shared Library References

   
   

   

   
   
6. From the Shared Library Mapping window, move the required shared libraries from Available to Selected. In the following figure, JERSEY2x is selected.

   Figure 8-3 WebSphere Shared Libraries Mapping Selection

   
   

   

   
   
7. Click OK .
8. Similarly, select the next application or module and repeat the procedure from steps 5 to 7.

   Figure 8-4 WebSphere Shared Libraries Select Next Application

   
   

   

   
   
9. Disable the built-in JAX-RS via JVM property.
   1. Navigate to the WebSphere admin console in the Servers select WebSphere Application Servers then select yourServerName .
   2. In the Server Infrastructure section, go to Java and Process Management select Process definition , select Java Virtual Machine then select Custom properties .
   3. Add the following property: com.ibm.websphere.jaxrs.server.DisableIBMJAXRSEngine=true

   Note:

   If the application does not come up post the steps mentioned above, then, navigate to Application Servers select server 1, select Web container then select Custom properties and modify the following property to True: com.ibm.ws.webcontainer.emptyServletMappings = true

   Figure 8-5 Set Web Container Custom Properties

   
   

   

   
   
10. Restart the application.