A JAR (Java ARchive) is a zipped file that contains a set of Java classes. It is used to store compiled Java classes and associated metadata that can constitute a program. A JAR acts like a callable program library for Java code elements (so that a single compilation link provides access to multiple elements, rather than requiring bindings for each element individually). To learn more about JARs, see http://java.sun.com/docs/books/tutorial/deployment/jar/
JAR resources in ALSB are used in:
The path is the project name and the name of the folder in which the JAR resides.
This search supports wildcard characters. For example, you can enter “j*” in the Name field to get a list of JARs that start with “j”.
Click View All to remove the search filters and display all JARs.
The unique name assigned to the JAR. The name is a link to the View a JAR Resource - JAR Configuration page. See Editing JARs.
|
|
The path is the project name and the name of the folder in which the JAR resides. It is a link to the project or folder that contains this resource. See Qualifying Resource Names Using Projects and Folders.
|
|
Click the Delete icon to delete a specific JAR. See Deleting JARs.
|
If the JAR loads without problems, the contents of the JAR will be available for viewing. To learn how to view JAR details, see Editing JARs.
Use the View a JAR Resource - Configuration page to update JAR files. Updating a JAR file essentially involves pointing the resource to a new version of the JAR, as you cannot edit a JAR using ALSB.
The date and time that the user imported this JAR into the configuration. Click the date and time link to view the change history of this resource. See View Change History page.
|
|
The number of JARs that this JAR references. If such references exist, click the numeric link to view a list of the JARs. See Viewing References to Resources.
|
|
The number of objects that reference this JAR. If such references exist, click the numeric link to view a list of the objects. See Viewing References to Resources.
|
|
The JAR configuration is displayed by default, which includes the information shown in Table 7-3.
The only field you can edit is Description. You cannot edit a JAR in ALSB. To update the JAR, you must select a new JAR to use. To learn how, see Adding JARs.
Note: | If you change the JAR used by an EJB Business Service (point the JAR resource to a new version of the JAR), you need to redeploy the EJB. You will then have to edit any EJB service that uses this JAR, and reselect the JAR resource, save, and activate. That will repackage the EJB business service to use the new JAR. |
Note: | Java callout actions and Tuxedo-based services, however, will automatically pick up the new JAR. |
In ALSB, JAR resources can contain classes that depend on other classes in different JARs. Use the Edit JAR Dependencies page to add or remove referenced JAR resources.
On the View a JAR Resource - JAR Configuration page, a numeric indicator on the Dependencies tab displays the number of referenced JARs configured for this JAR resource, or a zero if there are none.
The JAR dependencies page includes the information shown in Table 7-4.
The name of the referenced JAR. The name is a link to the View a JAR Resource - JAR Configuration page. See Editing JARs.
|
|
The Edit JAR dependencies page includes the information shown in Table 7-5.
For example, if you are editing JAR A and adding JARs B and C, JAR A references (depends on) JAR B and JAR A references (depends on) JAR C.
Use the arrows in the Options column to reorder the hierarchy of referenced JARs or the Delete icon to remove them.