Content

Problem
When you create a repository that represents a Microsoft SharePoint site, and click Connect, IBM Content Navigator makes a request to connect to the isolated shared library on the WebSphere Application Server. If the class file path was entered incorrectly when the isolated shared library was set up, the JAR files required for the connection cannot be found, the connection fails, and an error occurs.

Symptom

Your request cannot be processed.

Diagnosing the problem
WebSphere SystemOut.log contains an invocation target exception error, for example:

SystemOut O CIWEB Error: [news\Administrator @ 9.##.##.##] com.ibm.ecm.struts.actions.PluginRepositoryAction.execute() java.lang.reflect.InvocationTargetException

To configure an isolated shared library, follow these steps:

1. Open the WebSphere Application Server administrative console and click Environment > Shared Libraries.
2. Specify the cell, node, and server that represent the scope of the shared library. For example, if the scope is myRepositoryNode01 on myServer02, the cell is myRepositoryNode01Cell, the node is myRepositoryNode01, and the server is myServer02.
3. Click New and enter a name for the shared library. For example, enter SharePointSharedLib.
4. To include the JAR files in the shared library, specify the class file path where the JAR files are located. The default class file path on Windows is
   C:\Program Files\IBM\ECMClient\configure\sharePointLib.
5. Select Use an isolated class loader for this shared library and save your changes.
6. Associate the shared library with the navigator module:
1. Click Application > WebSphere Enterprise Applications > navigator > Shared Library References
2. In the Module section, select the navigator box and click Reference shared libraries.
3. Select the shared library that you created and save your changes.
7. Restart the web application server. After you restart the web application server, your isolated shared library is established.
8. Restart IBM Content Navigator on your WebSphere Application Server.

1. Open the WebSphere Application Server administrative console and click Environment > Shared Libraries.
2. Specify the cell, node, and server that represent the scope of the shared library. For example, if the scope is myRepositoryNode01 on myServer02, the cell is myRepositoryNode01Cell, the node is myRepositoryNode01, and the server is myServer02.
3. Select the shared library that you created and click Edit.
4. To include the JAR files in the shared library, specify the correct class file path where the JAR files are located.
5. Select Use an isolated class loader for this shared library and save your changes.
6. Associate the shared library with the navigator module:
1. Click Application > WebSphere Enterprise Applications > navigator > Shared Library References
2. In the Module section, select the navigator box and click Reference shared libraries.
3. Select the shared library that you created and save your changes.
7. Restart the web application server.
   Restart IBM Content Navigator on your WebSphere Application Server.

However, if that does not resolve the problem, you can try the following tasks:

• Remove and redefine the isolated shared library file, and reload the Microsoft SharePoint plug-in.
1. On your WebSphere Application Server, remove the shared library reference from the navigator module.
2. Remove the isolated shared library definition from the environment shared libraries.
3. Restart IBM Content Navigator.
4. Redefine the isolated shared library.
5. Add the shared library reference to the navigator module
6. Restart IBM Content Navigator, and reload the sharePointPlugin.jar by using the IBM Content Navigator administration tool.

• Remove the isolated shared library, remove the files from the profiles subdirectory, redefine the isolated shared library, and reload the Microsoft SharePoint plug-in.
1. On your WebSphere Application Server, remove the shared library reference from the navigator module.
2. Remove the isolated shared library definition from the environment shared libraries.
3. Restart IBM Content Navigator.
4. Shut down WebSphere.
5. Remove all folders and files in the following directories:
• home_dir\WebSphere\AppServer\profiles\app_server_dir\wstemp
• home_dir\WebSphere\AppServer\profiles\app_server_dir\temp\node_dir\server_dir
6. Start WebSphere.
7. Redefine the isolated shared library.
8. Add the shared library reference to the navigator module.
9. Restart IBM Content Navigator, and reload the sharePointPlugin.jar by using the IBM Content Navigator administration tool.
• Rename the isolated shared library.
1. On your WebSphere Application Server, redefine the isolated shared library and give it a different name.
2. Add the shared library reference to the navigator module, and reference the new name instead of the old name.
3. Restart IBM Content Navigator.