Occurrence scenario
1. After deploying the OD application to WebSphere, start the application.
2. The following exception was outputed to the FFDC log of WebSphere.
Exception:java.io.FileNotFoundException SourceId:com.ibm.ws.classloader.ClassLoaderUtils.addDependents ProbeId:246 Reporter:java.lang.Class@c0bc96c0
java.io.FileNotFoundException: /AP/IHS/htdocs/CCSWebServer11/runtimeSupport/xml-apis.jar

So, please advise below my inquiry.

1. In OD 07.00.18.01 environment, xml-apis.jar exists in runtimeSupport for WebSphere.
Is it a estimated results as design that does not exist in the environment of OD 08.12.11.01?
Does the occurrence of this exception affect the operation of the application?
2. If 1 has no effect, is there a way to make this exception go away?
3. Will this exception affect https communication, etc.?

We are using this system with below products.
[[ EPM ]]
<swversion>
Avaya Connector Server
Version: RH8.4.64-AV04EP8
Offer Type: bundled
Operating System Version
Linux 4.18.0-372.26.1.el8_6.x86_64
<iaversion.php>
installagent 8.1.2.0.0202 full
docs 8.1.2.0.0202 full
vpms 8.1.2.0.0202 full
vpms 8.1.2.0.0341 patch
docs 8.1.2.0.0341 patch

<OVA for deploy>
ExperiencePortal-Primary-EPM-8.1.2.0.0202.ova
<Patches>
epavl-8.x.x.0.2210.tar.gz
EPM_8.1.2.0.0328.tar.gz
EPM_8.1.2.0.0341.tar.gz

[[ Web Application Server ]]
Orchestration Designer?08.12.11.01
JAVA?IBM Java V1.8.0
WAS?WebSphere Application Server V9.0.2.x
OS?RHEL8.1

Best regards, K.Yamahara

Hi.

The file 'xml-apis.jar' is present in the runtimeconfig.war\WEB-INF\lib, it needs to be copied into the library of your app server ( Ex. tomcat/lib). Please, check the library of WS.

Hi massimo-san,

Thank you for your quick reply.
I understood your answer. However I still need more help.
We are using Websphere. Then I found below similer thread. Then I understood we also need to follow below procedure for 'xml-apis.jar' as well.
Is this my understanding correct?

Subject: Axis2 Problems
https://www.devconnectprogram.com/forums/posts/list/21782.page#p152614

for webShepre follows next steps and recomendation, you can fin this in the OD dev_guide :

Performing additional WebSphere configuration
About this task
For WebSphere 7.0 and later, the Axis2 library files provided by Orchestration Designer conflicts
with the Axis2 library files from WebSphere installation. Therefore, you must configure a separate
class loader for Orchestration Designer applications to use Axis2 library effectively.
Perform the following steps for the additional WebSphere configuration:
Procedure
1. Open the WebSphere Administrative Console.
2. On the Environment menu, click Shared libraries and create a shared library.
3. Copy the following entries into the Classpath field:
${WAS_INSTALL_ROOT}/lib/ext/axiom-api-1.2.13.jar
${WAS_INSTALL_ROOT}/lib/ext/axiom-dom-1.2.13.jar
${WAS_INSTALL_ROOT}/lib/ext/axiom-impl-1.2.13.jar
${WAS_INSTALL_ROOT}/lib/ext/axis2-adb-1.6.2.jar
${WAS_INSTALL_ROOT}/lib/ext/axis2-adb-codegen-1.6.2.jar
${WAS_INSTALL_ROOT}/lib/ext/axis2-json-1.6.2.jar
${WAS_INSTALL_ROOT}/lib/ext/axis2-kernel-1.6.2.jar
${WAS_INSTALL_ROOT}/lib/ext/axis2-saaj-1.6.2.jar
${WAS_INSTALL_ROOT}/lib/ext/axis2-transport-http-1.6.2.jar
${WAS_INSTALL_ROOT}/lib/ext/axis2-transport-local-1.6.2.jar
${WAS_INSTALL_ROOT}/lib/ext/neethi-3.0.2.jar
${WAS_INSTALL_ROOT}/lib/ext/woden-api-1.0M9.jar
${WAS_INSTALL_ROOT}/lib/ext/woden-impl-dom-1.0M9.jar
${WAS_INSTALL_ROOT}/lib/ext/woden-tool-1.0M9.jar
${WAS_INSTALL_ROOT}/lib/ext/XmlSchema-1.4.7.jar
${WAS_INSTALL_ROOT}/lib/ext/VPWebServiceClient-<version>.jar
${WAS_INSTALL_ROOT}/lib/ext/VPAppLogClientWS_<version>.jar
You must modify the version for VPWebServiceClient -<version>.jar according to
the file deployed in the lib or ext directory.
4. Click Servers > Server Types > WebSphere application servers to navigate to the server
configuration page.
5. From the server list, select the server that you want to associate with the shared library.
6. Click Java and Process Management in Server Infrastructure section, and click the Class
Loader link.
7. Create a new class loader, and set the class loader order to Classes loaded with local
class loader first (parent last). Click OK.
8. Select the newly create class loader.
9. On the Configuration page, click the Shared library references link.
10. On the Configuration page, ensure that the shared library you created is selected.
11. Click OK to save the configuration.
12. Make sure you verify all the configuration has been saved, and restart the application server.

Best regards, k.Yamahara

HI Kenji, sure, you are working with the WS 9.x and the procedure states 'For WebSphere 7.0 and later'

Here the doc (the procedure on page 429.):

https://download.avaya.com/css/public/documents/101083618

Please follow and report here.

Hi massimo-san,

Thank you for your quick reply.

I will try to do that tomorrow. Then I will feed results back to you.

Best regards, Kenji

Hi massimo-san,

Thank you for your support.

We can NOT found the "xml-apis.jar" file in OD(8.1.2.1101) install package.
If we need to check other package, please advise.

Export>Export Runtime Support Files>IBM WebSphere
As a result of outputting with
- runtimeSupportWebSphere.zip does not include xml-apis.jar.

We tried to expanded all the contents of runtimeconfig.ear, but WEB-INF/lib only contains "runtimeconfig.jar" and does not include "xml-apis.jar".
Best regards, Kenji

Hi.

Ok, so the WEB-INF/lib directory in the 'runtimeconfig.war' contains just "runtimeconfig.jar".
This happens in the OD release 8.1.2.1101, right ?

It sounds strange, take a look at my environment , that is the first picture below (I don't remember when I collected that file):



Might you send me your exact OD release (second picture below) ?

Hi massimo-san,

Thank you for your support.

Please find attached file.
(attached file : OD_ver.png)

Hi Massimo-san,

Thank you for your support.

If you can provide all of required .jar or any files to use OD with Websphere, please provide them to us once.
Then we will try to confirm whether OD can be work with them or not.

After that please release them formally as MR.

Best regards, K.Yamahara

Hi.
The 'xml-apis.jar' is no longer required. Most likely you have the classloader configured on Websphere to point to the file along with other dependencies as instructed by the OD documentation for previous versions. Following the OD Developer's Guide for 8.1.2 ( https://download.avaya.com/css/public/documents/101083618 ), try to remove the entry that reference this file.

Hi Massimo-san,

Thank you for your reply.
We will remove the entry that reference below file.
The logs say: /AP/IHS/htdocs/CCSWebServer11/runtimeSupport/xml-apis.jar

Anyway, please remove the entry from original file in OD which will release in the future version.

So, let's close this forum.
Best regards, Kenji

Hi Massimo-san,

We confirmed "xml-apis.jar" was described in MANIFEST.M of below jar files.
- serializer-2.7.2.jar
- xalan-2.7.2.jar

Let me confirm do we still require both files for OD?
If we need it, we should install "xml-apis.jar" on customer's system.
If we don't need it, we will removed both file from class loader for shared library

- serializer-2.7.2.jar / META-INF / MANIFEST.MF
Manifest-Version: 1.0
Created-By: 1.7.0_51 (Oracle Corporation)
Main-Class: org.apache.xml.serializer.Version
Class-Path: xml-apis.jar

- xalan-2.7.2.jar / META-INF / MANIFEST.MF
Manifest-Version: 1.0
Created-By: 1.7.0_51 (Oracle Corporation)
Main-Class: org.apache.xalan.xslt.Process
Class-Path: xercesImpl.jar xml-apis.jar serializer.jar

Best regards, K.Yamahara