SOA Governance and API Management : Working with CentraSite Business UI : Administering the Business UI : Managing Assets : Attaching a Document to an Asset : Attaching an Input File to an Asset
Attaching an Input File to an Asset
An input file is type-specific and depends on the type of asset to which it will be attached. The following table lists the asset types installed with CentraSite and identifies the types of files they require as input.
For this asset...
You must supply this type of file...
Web Service (including Abstract Service)
Web Service Definition Language (WSDL) file.
XML Schema
XML Schema Definition (XSD) file.
Process
XML Process Definition Language (XPDL) file.
You can also choose the option Resolution, which will allow you to specify how already existing imported/included files (further WSDL or schema) are handled. For each of the imported/included files you have one of these options:
*Overwrite the file with new content.
*Create a new version of the file with the new content (if, for example, you want to modify a schema but want to retain its previous version).
*Reuse any version of the file (if, for example, an intermediate version of a schema is currently referred to by a WSDL, you can redirect it to the newest version).
You can attach an input file to an asset instance in the following ways:
*You can attach a document from your file system.
*You can attach any document on the network that is accessible via a URL.
Use the following procedure to attach an input file, for example, WSDL, XML schema, or a BPEL file to the asset.
To attach an input file to the asset
Before you begin, you must have the input file that you want to attach. This file can reside on the file system of the computer where your browser is running, or it can reside anywhere on the network, as long as its location is addressable through a URL.
1. In CentraSite Business UI, display the details page for the asset to which you want to attach an input file. If you need procedures for this step, see Displaying Details of an Asset.
2. In the actions bar for the asset, click Attach.
3. In the Attach Document dialog, specify whether the input file will be read from a URL-addressable location on the network (the URL option) or from your local file system (the File option). Do one of the following as appropriate:
*If the file you are attaching resides on the network, enable the URL option. Specify its URL.
*If the file resides in your local file system, enable the File option. Specify the file name. You can use the Choose File button to navigate to the required folder.
Note:  
To ensure that CentraSite sets the file type correctly in the repository, the name of the file should include an extension that indicates the type of data it contains.
4. Expand Advanced Settings and complete the following steps as necessary.
a. If you have specified a URL and the site you want to access via the URL requires user authentication, enter a username and password for authentication at the URL site.
b. You can also use the Resolution option, which will allow you to specify how an already existing imported/included file (further WSDL or schema) is handled. For each of the imported/included files you have one of these options:
Options
Usage
Always ask
Reuse the existing WSDL/schema files referred to in the main WSDL/schema file, or replace the existing WSDL/schema files by uploading new files.
Always overwrite
Overwrite the existing WSDL/schema files in the registry with the new ones specified by the input file.
Always create new versions
Create a new version of the file with the new content.
If you choose the Always ask option and there is more than one input file with the same name and namespace, you can choose between these. To allow you to select the required file, the dialog Reuse Existing Asset lists the available assets that match the given file name, and also their available versions. You can view the description of any asset in the list; this is useful if you want to check that you have selected the correct asset's file from the list.
5. Choose Attach.
Copyright © 2015- 2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback