Update assets

We can use the Update asset wizard to update classes, composites, wsdl, xsd, and definitions.xml files in an asset.

Import one or more assets. The file name of each deployable object in the imported assets is shown on the list of assets on the console Assets page.

We can update all or part of the contents of assets that are in the product management domain. Complete the steps in the Procedure to update an asset using the console Update asset wizard. Alternatively, we can update assets using programming or wsadmin.sh.

The following update limitations exist if the asset you are updating is a Service Component Architecture (SCA) asset:

• We cannot delete a composite file that a composition unit is using. If a delete is attempted, a warning message is sent to the Update asset log.

• We cannot update an sca-contribution.xml file.

  • SCA cannot detect deployable composites that are either added or deleted. Therefore, during deployment of a new composition unit, we do not see the new deployable composite in the deployables option list.

  • SCA cannot detect dependencies added/removed during the Update asset process.

    • If a new import package is added and if a class in an existing composition unit is updated to require this new package, then the Update asset wizard fails with a ClassNotFoundException. Deployment of any new composition units from the updated asset are successful as the dependencies are detected during deployment operation.

    • If a new export package/namespace is added, then it has no affect on the existing composition unit and the Update asset wizard completes successfully.

• We cannot update configuration metadata such as composite, XSD, or WSDL files in a dependent SCA asset that is deployed as a shared library. We can only update binary files that do not contain annotations which the SCA programming model uses or depends on.

• Because the Update asset wizard uses the new composite definition file provided in the asset for the existing composition unit, the following post deployment related changes to the composite configuration are not saved.

  • Binding resources: To save this information, export all the data to the composite definition file in the new asset before you do the update.

  • Component reference target URIs: To save this information, export all the data to the composite definition file in the new asset before you do the update.

  • Component properties: To save this information, export all the data to the composite definition file in the new asset before you do the update.

  • HTTP Endpoint URL information: You need to reconfigure this information after the Update asset wizard finishes.

• For web services policy set attachments, during Update asset processing:

  • If there is a policy set specified for an endpoint in the updated composite definition file, SCA checks to see if a policy set has already been attached to that endpoint in the deployed composition unit. If an attachment already exists for that endpoint, the attachment is removed, and the policy set listed in the new composite file for that endpoint is attached. In this situation, if we have made any post deployment policy set configuration changes, these changes are lost.

  • If there is no policy set defined for an endpoint in the update composite definition file, then any existing attachments to that endpoint are removed.

• Policy set bindings follow these same rules.

• For RunAs and RoleToUser mapping definitions, during Update asset processing:

  • For implementation.java, implementation.spring and implementation.osgiapp, any new roles defined in the definition.xml file in the asset are picked up and users can be mapped to these roles using either the editCompositionUnit command or the console. Any existing role mappings for the original roles are preserved.

  • For implementation.jee, the runAs and RoleToUser mappings are defined in the JEE application instead of in the SCA asset or SCA composition unit. Therefore, SCA does not do anything with these mappings during Update asset processing.

• The user defined virtual host that hosts web content for binding.ws, binding.atom, binding.http with wireformat.jsonrpc and implementation.widget is not supported. A virtual host mapping of default_host is used during Update asset processing.

1. Go to the Update asset wizard.

   1. Click Applications > Application Types > Assets to access the Assets page.

   2. Select the check box next to the asset to update.

   3. Click Update.

2. On the Update asset page, specify whether we want replace an entire asset or update its contents and, as needed, the replacement file or module.

   1. Select an update option.

      We can update asset contents by adding, deleting, or updating a single file or module in the asset, or by merging multiple files or modules. Update options include the following:

      • Replace entire asset

      • Replace specific asset contents

      • Add module or file to asset

      • Remove file or module from asset

      • Merge asset contents

      The online help for the Update asset page describes the options.

   2. If we are updating specific asset contents or removing a file or module, specify the path beginning with the asset archive file.

      For Specify the path beginning with the asset archive file, specify a relative path to the file that starts from the root of the asset file. For example, if the file is located at com/company/greeting.class in module hello.jar, specify a relative path of hello.jar/com/company/greeting.class.

   3. If we are updating the entire asset, updating an asset file or module, or merging asset contents, specify the full path name of the new file or module.

   4. Click Next.

3. On the Select options for updating an asset page, specify asset settings and click Next.

   The online help for the Select options for importing an asset page describes the settings.

4. On the Summary page, click Finish.

Results

If we update an asset packaged as a library JAR file that is not a Java EE archive, then the product automatically distributes the updated asset to all of the composition units that use the asset.

However, if you update a Java EE asset, then the product does not automatically distribute the updated Java EE archive to composition units created from that asset, which are Java EE applications. We must select every Java EE application created from that asset and use the Update button to update the Java EE application individually by specifying the update contents.

What to do next

Create a business-level application and add the asset to the business-level application.

Subtopics

• Update asset settings
  Use this page to select whether we want replace an entire asset or update its contents. We can update asset contents by adding, deleting, or updating a single file or module in the asset, or by merging multiple files or modules into an asset. Updating an asset registers the updated files with the product management domain.

Related concepts

Assets

Related tasks

Create business-level applications

Administer business-level applications using programming

Listing assets using programming

Edit an asset using programming

Import an asset using programming

Manage assets

Upload asset settings

Asset collection

Asset settings