Deploying an Orbix application in a WebSphere instance that enables IBM Global Security fails.

Dominique Sacre · 2013-05-17T17:43:00+00:00

Summary Deploying an Orbix application in a WebSphere instance that enables IBM Global Security fails. Article Number 13107 Environment All Supported Operating Systems Orbix 6.x Question/Problem Description Deploying an Orbix application in a WebSphere instance that enables IBM Global Security fails.WebSphere security classes clash with Orbix TLS classes. Is there a workaround when deploying an Orbix application within a WebSphere container? Clarifying Information Error Message Defect/Enhancement Number Cause Resolution Orbix 6 distribution includes SSL and TLS security classes, need to support secure IIOP. When deployed inside a secure WebSphere instance, common classes between WebSphere jars and Orbix jars can cause unexpected errors. This is the case if Orbix classes are loaded by the main WebSphere instance classloader.There is two possible workaround to this problem:1. Define a WebSphere shared library reference, and refer to it in your Orbix application. This is a two step process: Step1: Create a shared library reference: Go to "WebSphere Integrated Console" (new name for WebSphere Administration Console)Go to Environment->Shared LibrarySelect scope (node server), and click on newFill the name of the shared library reference. in "classpath" enter the path to <Orbix>asp\\<version>\\lib\\asp-corba.jar Step2: refer to the created shared library in your application Go to "WebSphere Integrated Console" (new name for WebSphere Administration Console)Go to "Enterprise applications", and select your applicationIn "references", select "Shared Library References", then select your application.Add the reference created in step 1.Restart your application 2. If secure IIOP is not used by the Orbix application, 'tls.jar" can be removed from the manifest file inside <Orbix>asp\\<version>\\lib\\asp-corba.jar Edit Manifest file inside <Orbix>asp\\<version>\\lib\\asp-corba.jarRemove tls.jar entry from the manifest path Note the first solution is preferred, since it keep secure IIOP support available, and does not require jar changes. Workaround Notes Attachment Created date: 06 September 2011 Last Modified: 13 February 2013 Last Published: 23 June 2012 First Published date: 09 September 2011 #KnowledgeDocs#Orbix

Summary	Deploying an Orbix application in a WebSphere instance that enables IBM Global Security fails.
Article Number	13107
Environment	All Supported Operating Systems Orbix 6.x
Question/Problem Description	Deploying an Orbix application in a WebSphere instance that enables IBM Global Security fails. WebSphere security classes clash with Orbix TLS classes. Is there a workaround when deploying an Orbix application within a WebSphere container?
Clarifying Information
Error Message
Defect/Enhancement Number
Cause
Resolution	Orbix 6 distribution includes SSL and TLS security classes, need to support secure IIOP. When deployed inside a secure WebSphere instance, common classes between WebSphere jars and Orbix jars can cause unexpected errors. This is the case if Orbix classes are loaded by the main WebSphere instance classloader. There is two possible workaround to this problem: 1. Define a WebSphere shared library reference, and refer to it in your Orbix application. This is a two step process: Step1: Create a shared library reference: Go to "WebSphere Integrated Console" (new name for WebSphere Administration Console) Go to Environment->Shared Library Select scope (node server), and click on new Fill the name of the shared library reference. in "classpath" enter the path to <Orbix>asp\\<version>\\lib\\asp-corba.jar Step2: refer to the created shared library in your application Go to "WebSphere Integrated Console" (new name for WebSphere Administration Console) Go to "Enterprise applications", and select your application In "references", select "Shared Library References", then select your application. Add the reference created in step 1. Restart your application 2. If secure IIOP is not used by the Orbix application, 'tls.jar" can be removed from the manifest file inside <Orbix>asp\\<version>\\lib\\asp-corba.jar Edit Manifest file inside <Orbix>asp\\<version>\\lib\\asp-corba.jar Remove tls.jar entry from the manifest path Note the first solution is preferred, since it keep secure IIOP support available, and does not require jar changes.
Workaround
Notes
Attachment

Created date:	06 September 2011
Last Modified:	13 February 2013
Last Published:	23 June 2012
First Published date:	09 September 2011

#KnowledgeDocs
#Orbix

Sign up

Please log in or register:

Welcome to the Rocket Forum!

Please log in or register:

Scanning file for viruses.

This file cannot be downloaded