Deploying Images and JAR files as Part of a Shared Library JAR file

D Deploying Images and JAR files as Part of a Shared Library JAR file

Learn how to deploy images and JAR files as part of a shared library JAR file. If you have customized an application, a skin, or a resource bundle, you must deploy it as a JAR file within a shared library JAR file.

How to Deploy Images and JAR Files as Part of a Shared Library JAR File

In this section, we use an example in which you include in a shared library JAR file the files you previously created:

customSkin.jar as described in How to Choose a Skin in Process Workspace
customer-impl.jar as described in Customizing Applications in Process Workspace and the Worklist Application
ResourceBundle.jar as described in Customizing a Resource Bundle.

To deploy images and JAR files as part of a shared library JAR file:

Create a temp directory, mkdir temp.
Unzip all the jar files into the temp folder.
```
unzip customSkin.jar -d temp/
unzip customer-impl.jar -d temp/
unzip ResourceBundle.jar -d temp/
```
After you do this, you can see a META-INF folder included in the temp folder.

Note:

You can create an images directory inside the temp directory and copy your customized logo file into it. Then from the application preferences, you can refer to it as /images/customizedLogo.jpg.

Create a MANIFEST.MF file under META-INF directory.

This file should contain the following:

Manifest-Version: 1.0
Ant-Version: Apache Ant 1.7.1
Created-By: 19.1-b02 (Sun Microsystems Inc.)
Implementation-Vendor: Oracle
Implementation-Title: Custom Client Applib
Implementation-Version: 1.0
Product-Name: Custom Client Applib
Specification-Version: 1.0
Extension-Name: custom.client.applib

To ensure that all required class files and other skin files are available in the shared library, package everything into the file custom.client.applib.jar.
To do this, navigate to the temp directory and run the following command:
```
jar -cvfm custom.client.applib.jar META-INF/MANIFEST.MF *
```
You have now created the shared library under the temp directory. It looks like this: temp/custom.client.applib.jar.
Deploy custom.client.applib.jar on the Oracle WebLogic Server as a shared library.

To do this: From the Oracle WebLogic Server Console, click Deployments and Install, navigate to the JAR file location, and deploy.
Restart the Worklist Application or Process Workspace from the Oracle WebLogic Server.

Figure D-1 shows the interface for restarting the Worklist Application.

Figure D-1 Stopping Worklist Application

Description of "Figure D-1 Stopping Worklist Application"

Figure D-2 shows the Oracle WebLogic Server interface for restarting the Worklist Application.

Figure D-2 Restarting Worklist Application

Description of "Figure D-2 Restarting Worklist Application"
Log in to either Worklist Application or Process Workspace, navigate to the Application Preferences page, and specify your customized items.

Figure D-3 highlights the fields to specify.

Figure D-3 Setting Application Preferences

Description of "Figure D-3 Setting Application Preferences"

Note:

To be sure that your branding logo is retrieved, in the Branding Logo field, be sure to precede the file name of your logo with the path name /faces/.