Field | Description | |
Name | (Optional). Name of the REST Service. Note: This is the name that users will see when they view this REST Service asset in the CentraSite User Interfaces. Therefore, specify a meaningful name for each REST Service. The name of a REST Service asset must be NCName-conformant, meaning that: The name must begin with a letter or the underscore character (_). The remainder of the name can contain any combination of letters, digits, or the following characters: . - _ (that is, period, dash, or underscore). It can also contain combining characters and extender characters (for example, diacriticals). The name cannot contain any spaces. Furthermore, if the REST Service name contains any non-conformant character, upon publishing the REST Service to any gateway, the non-conformant character is simply replaced with the underscore character (_) in Mediator. However, in CentraSite the REST Service name defined by you is displayed. For more information about the NCName type, see
http://www.w3.org/TR/xmlschema-2/#NCName If you have not specified a Name for the REST Service, CentraSite automatically maps this field with the Service Title property, that is defined in the Swagger specification. | |
Type | The asset type, REST Service. | |
Organization | The organization to which you want to add the REST Service. (The Organization list only displays organizations for which you have the Manage Assets permission or at least the Create Assets permission.) | |
Version | (Optional). The version identifier for the REST Service. You can enter any string in this field, that is, the version identifier does not need to be numeric. You can also leave the field blank. You can later create new versions of the REST Service. The default is 1.0. Examples: 0.0a 1.0.0 (beta) Pre-release 001 V1-2007.04.30 If you have not specified a Version for the REST Service, CentraSite automatically maps this field with the Service Version property, which is defined in the Swagger specification. | |
Description | (Optional). The description for the REST Service. Note: This is the description information that users will see when they view this REST Service asset in the CentraSite User Interfaces. Therefore, specify a meaningful description for each REST Service. If you have not specified a Description for the REST Service, CentraSite automatically maps this field with the Description property, that is defined in the Swagger specification. | |
Import from a Specification File | The input file for the REST Service. | |
Option | Description | |
URL | If the input file you are importing resides on the network, you can specify its URL. | |
File | If the specification resides in your local file system, specify the file name. You can use the Choose button to navigate to the required folder. |
Field | Description |
Credentials | If you have specified a URL and the site you want to access through the URL requires user authentication, type a username and password for authentication at the URL site. |
Resolution | Select a resolution strategy, which will allow you to specify how an already existing imported and included file is handled. For each of the imported and included files you have one of these options: Create new version: Creates a new version of the file with the new content (if, for example, you want to modify a WSDL file but want to retain its previous version). Always overwrite: Overwrites the importing file with new content. |