SOALink Engine Messages

During configuration of routing protocol, if any of the routing types are StraightThrough/LoadBalance/ContentBased/ContextBased routing, then the transport of the routing should be HTTP enabled.

Enable the HTTP transport for routing protocol.

During configuration of the routing protocol, if the routing type is JMS routing, then the transport of the routing should be JMS enabled.

Enable the JMS transport for routing protocol.

The input JAR file provided does not contain the relevant TargetType definition XML.

Add the relevant TargetType definition XML to the input JAR file.

The input JAR file provided does not contain the relevant transformation file.

Add the relevant transformation file to the input JAR file.

The input JAR file provided does not contain the target type name in the Target Type Definition file.

Provide the Target Type name.

The input JAR file provided does not contain the relevant Event Type definition.

Add the relevant Event Type definition to the input JAR file.

The Target Type already exists with the provided name in Target Type definition file.

Change the Target Type name.

The imported WSDL does not contain the service element.

Make sure service element is present in the service WSDL.

The WSDL is not present for the created virtual service.

Make sure the created virtual service contains the WSDL.

An activity log which is the latest deployment log for a deployed asset cannot be deleted.

Unselect the particular deployment log from the deployment history before deleting other old entries.

The consumer application used as part of the context based routing condition of the asset to be deployed is not available in the CentraSite Repository.

Change the consumer application selected in the routing condition.

This exception is thrown when a data type mismatch is encountered when mapping SNMP Trap attributes from EventType.xml to RuntimeEventType attributes.

Ensure the data type matches.

The inbound transport information is not defined for the asset to be deployed to the Mediator.

Configure the entry protocol in the processing steps profile of the asset to be deployed.

A WSDL is not available for the native service to be virtualized.

Attach the WSDL for the native service to be virtualized.

Service must contain at least one service binding, otherwise it cannot be virtualized

Getting error while virtualizing the service without service binding

During target type creation, if the SNMP Trap OID is duplicated in EventType.xml, this exception is thrown.

SNMP Trap OIDs should be unique within and across target types.

During target type creation, if the SNMP Trap OID is already present in an existing target type, this exception is thrown.

SNMP Trap OIDs should be unique within and across target types.

Scoped Virtual Service deployment will not be triggered since some of the dependent assertions are missing in the Runtime Policy.

Ensure dependent assertions exist.

Virtual Service will have policies associated with it. These policies may be dependent on other policies. If the dependent policies are not applied for the virtual service, this exception will arise.

Please create the dependent runtime policy and make sure it is applicable for the virtual service to be deployed.

An error occurred while creating an API Key instance.

Check if there are any related messages in the log to determine the cause of the problem.

Mandatory parameters were not provided while creating API Key object

Provide the mandatory parameters.

The version of mediator to which the asset is being deployed does not support the parameter {0}.

Change the parameter to one that is supported in the mediator version installed.

An error was encountered while creating the OAuth2 Client asset.

Check if there are any related messages in the log to determine the cause of the problem.

Mandatory parameters were missing while creating OAuth2 client object.

Check if the mandatory parameters 'Service' and 'Consumer' are missing.

When both API Keys and OAuth2 are enforced for an API in AND condition, this exception is thrown

Change the Enforce condition to OR

This occurs if no connection can be established to the deployment endpoint defined in a target during deployment/undeployment/syncconsumers operations. This could be because the deployment endpoint is down or the credentials used for accessing the deployment endpoint are wrong.

Check if the deployment endpoint is up and running. Also check if the credentials defined in the target for accessing the deployment endpoint are correct.

This is how the name of the API key will be generated where the service name is passed as a parameter.

No action required.

This is how the name of the OAuth2 Client is created when the service name and consumer name are passed as parameters.

No action required.

Virtual Service can be deployed from latest version of CentraSite to Mediator version 8.2.2 and above. If you deploy any service to older version of Mediator from latest version of CentraSite, some policy parameters or actions cannot be executed on older version of Mediator. Such policy parameters or actions will be ignored. This warning message will list those ignored parameter/actions.

If the ignored parameters or actions need to be executed, then Mediator has to be upgraded to version in which CentraSite is running. If the ignored parameter or actions are not needed, then this warning message can be ignored.