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.
Property
|
Description
|
---|---|
Last Modified By
|
The user who imported this JAR into the configuration.
|
Last Modified On
|
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.
|
References
|
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.
|
Referenced by
|
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.
|
Description
|
A description of this JAR, if one exists.
|
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. |