Submit Data command properties

Durable

Indicates whether the queue is durable. By default, this property is set to True.

If the queue specified in your configuration item is not durable, you will need to change this property to False; otherwise, you may encounter an error due to durability mismatch and your configuration item will not start until this is fixed.

True, False

Username

The user name for the external software.

User account

Password

The password that is associated with the external user account.

Note: The default SubmitData item that appears in a new project doesn't come with authentication details. These empty values produce a validation error unless you supply user authentication details.

Password

URI

The uniform resource identifier (URI) that is the source for receiving Submit Data commands.

You must enter the appropriate URI for the software you are using.

Note: The URI for RabbitMQ cannot contain the slash (/) character or spaces in the name of the queue.

For the URI value, we suggest that you use a naming convention that includes the version information of the Service Bus Submit Data message schema.

The schema version appears in the header of the message text.

<xmlns="http://schemas.ampla.com/ServiceBus/SubmitData/2014/08">

amqp://ampla.commands.submitclientnotification.v201902

MessageFormat

Specifies whether to use XML format or JSON format for the message scheme.

If a message does not match the message type, the message is not processed; an error is logged and the message moves to the Dead Letter Queue. See, Dead Letter Queues.

XML, JSON

MessageSchema

Click the Browse (...) button on the MessageSchema property.

The MessageSchema Editor opens. The format depends on whether the MessageFormat property is XML or JSON format.

For more information, see Submit Data command schema.

RunAsUser

Click Browse (...) to open the picker dialog and select the Production Analyst user to submit this command. Only users of Basic User type are available for selection.

We recommend that you create Production Analyst users that are specific for submitting data. These users should have minimal privileges and limited access to the areas in the project.

You should avoid giving an unnecessary amount of access to users who will be submitting external data into Production Analyst.