If you are using legacy Component Manager
and have a component that uses multiple .jar files and the .jar files
are not part of the code module for the component (for example, JDBC
drivers or Java Platform, Enterprise Edition .jar files), special
steps are required. Use the Register component classes window
to specify the additional files.
To complete the class registration task, the .jar file must be accessible from your local computer during the configuration process.
For run time, the .jar file must be located on the server where Component Manager runs. You use Process Task Manager to specify the exact location of the .jar file and to start the component.
If you later use Process Configuration Console on a different computer to access the classes in this .jar file, an error is displayed if the .jar file is not present at the previously specified location on that computer. To view the classes in the specified .jar file, you can either copy the .jar file to the directory where Process Configuration Console expects to find it, or you copy the .jar file to any location on your local system and re-register the class.
To specify additional classes for a component queue:
If there is an error when you save the registration, you can ignore the error and continue with the save, or you can return to the registration window to fix the problem.