Field | Description |
Create a New Virtual Alias | Name of the Virtual OData Service asset (also, termed as Virtual Alias). The name of a Virtual OData 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 Virtual OData Service name contains any non-conformant character, upon publishing the Virtual OData Service to any gateway, the non-conformant character is simply replaced with the underscore character (_) in Mediator. However, in CentraSite the Virtual OData Service name defined by you is displayed. For more information about the NCName type, see
http://www.w3.org/TR/xmlschema-2/#NCName Note: The name of a Virtual OData Service asset must be unique within an organization. If, for example, a Virtual OData Service with the same name already exists within the CentraSite registry, a warning message will be issued. By default, CentraSite populates the Create a New Virtual Alias field with the display name that was specified for the Native OData Service. |
Endpoint prefix for invocation alias | (Optional). Prefix for the Virtual OData Service. This field accepts URL paths. Example: /testmethod/myprefix/ test@1234 |
Endpoints of <Service_name> to be virtualized | The Native OData Service endpoint you want to use for invoking the Virtual OData Service. The Endpoints list displays a list of the Endpoint URLs available for the Native OData Service. |