Alias Reader

Specify the message acknowledge mode.
We recommend using acknowledge mode transacted.

Each single message sent to a JMS provider will be acknowledged by the JMS provider (not the recipient) after recipience.
Messages received from a JMS provider within an activity are acknowledged irrespective of subsequent activities. Consequently, if an error occurs during the execution of the activity diagram after message receipt, no rollback occurs.

Using Auto acknowledge mode in a model, a client must be prepared for possible loss of messages.

Duplicate acknowledge mode corresponds to Auto acknowledge mode. Additionally, the JMS provider may send the message more than once to the same destination.

The receiving application must be tolerant of receiving duplicate messages.

Messages sent to or received from a JMS provider within an activity are acknowledged explicitly after processing. Thus, the activity plays the role of a transactional lock.

Specify the expiration time of a sent message (refer also to the description of JMSExpiration in the JMS headers/properties).

Specify a selector to filter the received messages.

Refer to the official Java Message Service Specification for the selector statement syntax.

Specify the name of the queue or topic.

Specify a list of comma separated options in form of <name>=<value>. These options will be interpreted as native options.

The available options depend on the JMS provider.

Specify the JMS credentials in form of <user>/<password>.

Specify the port the JMS provider is listening to.

Protocol used to communicate with the JMS provider. The protocol normally is set automatically.

Specify a path to the JNDI file (.bindings), if a JNDI provider is used and protocol is file.

Specify the host name of the JMS provider.

Specify whether the JMS provider is also a JNDI provider. Default is false if not specified.

The JMS provider is a JNDI provider.

The JMS provider is not a JNDI provider (default).

Additional class that provides an easy way to get all tagged values that can be set dynamically.

Specify here whether you want the REST adapter to throw an exception upon receiving an HTTP error code >= 400.
For older models, if this flag is not present, it will be considered false.

Builder 7.12.0 Runtime 2020.12 In the context of HTTP based adapters (URL, REST, SOAP), enable automatic header generation for the listed headers. These definitions overwrite the default behavior, and X-Transaction-Id, X-Request-Id, X-Sender-Host and/or X-Sender-Service will be substituted by this definition.

requestHttpHeaderRoles can hold a list of definitions in format <http header name>:<role>, that will automatically be generated for each adapter call on this alias. <role> can be one of the listed allowed values (one list entry per line).
Refer to HTTP Header Support > Overwriting the Standard HTTP Headers for more details on header roles.

Additional class that provides an easy way to get all tagged values that can be set dynamically.

You can use this class to get the tagged values from the alias, change the values you need, and provide this class to a dynamic adapter call.

Runtime 2015.10 Supply the maximum number of parallel connections to the SAP system.

• The pool size can be defined per connection string. If you have multiple aliases with the same connection string, the highest value will be used.
  The same applies, if you set the values in the SAP adapter settings on the Bridge.

• If this tag is not set, the connection pool size specified on the <<E2EComposite>> will be applied.

• Compatibility note: This tag will not be created for existing aliases in older models. You have to add the tag manually if you want to set it.
  Older xUML Runtimes (before version 2015.10) will not start with the setting being present. As a workaround, you can delete the tag value.

If all connections from the SAP connection pool are in use, warnings will be logged to the transaction log each second a service is waiting for connection.

2015-12-08 16:47:24 +0100 0000000182469dcd0001612899fea700e3d869aa 3 SAPConnectionPool 0    OK SAPRFC IO_ENTER PoolExhausted
2015-12-08 16:47:25 +0100 0000000182469dcd0001612899fea700e3d869aa 3 SAPConnectionPool 1000 OK SAPRFC IO_EXIT  PoolExhausted

In this case, increase the pool size to solve the problem.

Specify the SOAP version used with this SOAP call.

Time zone string as specified in the time zone appendix. timezone is used to print DateTime expressions.

Examples: "Australia/Melbourne", "CET", "Etc/GMT+10".

If "local" is used, the date/time is printed relative to the local timezone of the Bridge, for example:
2012-10-01T12:36:47.0+02:00 (the timezone of the Bridge is UTC+02:00)

Date formatting code as listed in Date and Time Formatting. If nothing is defined, the XSD standard is used.

Example: %F

Builder 7.12.0 Runtime 2020.12 In the context of HTTP based adapters (URL, REST, SOAP), enable automatic header generation for the listed headers. These definitions overwrite the default behavior, and X-Transaction-Id, X-Request-Id, X-Sender-Host and/or X-Sender-Service will be substituted by this definition.

requestHttpHeaderRoles can hold a list of definitions in format <http header name>:<role>, that will automatically be generated for each adapter call on this alias. <role> can be one of the listed allowed values (one list entry per line).
Refer to HTTP Header Support > Overwriting the Standard HTTP Headers for more details on header roles.

Builder 7.12.0 Runtime 2021.1 Generates a HTTP digest header using the specified algorithm. When applied, a  digest  header is generated using the specified algorithm, and sent with the request . The generated header conforms with RFC3230 and RFC5843. 

Type of the proxy

Proxy user.

URL of the proxy server.

Type of the private key.

Whether to verify the host information form the SSL connection.

Whether to verify the peer information from the SSL connection.

Name of the file that contains the private key.

Password for the private key.

Name of the file that contains the client certificate.

Name of the file containing additional certificates for the connection verification (e.g. additional root CAs).

Type of the certificate.

Additional class that provides an easy way to get all tagged values that can be set dynamically.

If the tagged value dbType is set to DBTypeValue, the dbTypeVariable tagged value is used to define the type of the database. The dbType then can be defined by a setting variable.
This is to handle the case, that you not want to hard code the dbType, but to configure it at runtime via the E2E Bridge.
See Using Global Setting Variables for more information on how to define a global setting variable in the E2E Bridge.

Bridge 7 Specify here the required transaction isolation level of the SQL connection according to SQL-92 standard. Refer to Wikipedia for a detailed description of the available isolation levels.

Added in Builder 6.0.15.5 Runtime 2015.15 Specify the encoding for database access.

After a given connection age (in minutes) the connection will be closed and removed from the pool.

Connections not used for the time specified (in minutes) will be closed and removed from the pool.
This is useful for connections going through firewalls because such connections might be cut off after some time.

String that prefixes tables and stored procedures. For example, if schema is set to S1, all tables accessing the current DB are prefixed by "S1.".

String that prefixes tables. For example, if tableQualifier is set to TQ1, all tables accessing the current DB are prefixed by "TQ1", e.g. TQ1TEMPLOYEE. If schema and table qualifier are given, all tables will become: <schema>.<tableQualifier><tableName>.

Transport protocol.

Machine port number the service is binding to. This port number can be given at service level only.

HTTP path for the SOAP request.

Host name. Default is "localhost" if no value is specified.

HTTP method of the URL adapter call. Default is "POST" if no value is specified.

The maximum number of redirects to follow.

If true, HTTP error codes > 300 will not cause an exception in the model. This implies, that the response body is accessible even if HTTP errors occur. The default value is false.

Native cURL options as listed on Setting cURL Options on the URL Adapter .

Use one of the following syntax rules:

• values separated by ',' in one line
• values separated by ' ' in one line
• list of tagged values

Builder 7.12.0 Runtime 2020.12 In the context of HTTP based adapters (URL, REST, SOAP), enable automatic header generation for the listed headers. These definitions overwrite the default behavior, and X-Transaction-Id, X-Request-Id, X-Sender-Host and/or X-Sender-Service will be substituted by this definition.

requestHttpHeaderRoles can hold a list of definitions in format <http header name>:<role>, that will automatically be generated for each adapter call on this alias. <role> can be one of the listed allowed values (one list entry per line).
Refer to HTTP Header Support > Overwriting the Standard HTTP Headers for more details on header roles.

Builder 7.12.0 Runtime 2021.1 Generates a HTTP  digest  header using the specified algorithm.  When applied, a  digest  header is generated using the specified algorithm, and sent with the request .  The generated header conforms with RFC3230 and RFC5843.

URL of the proxy server.

Proxy user.

Type of the proxy

Name of the file containing additional certificates for the connection verification (e.g. additional root CAs).

Name of the file that contains the client certificate.

Name of the file that contains the private key.

Password for the private key.

Type of the certificate.

Whether to verify the host information form the SSL connection.

Whether to verify the peer information from the SSL connection.

Type of the private key.

Additional class that provides an easy way to get all tagged values that can be set dynamically.