queue in connector (generic)

Description - Generic to configure a RabbitMQ receiving queue


Parameter Groups

 ParameterTypeDescription
*URI:stringThe broker URI, in the format scheme://host:port/virtualhost, where the scheme is amqp or amqps, the port is optional defaulting to 5672 for amqp and 5671 for amqps, and the /virtualhost is also optional
*User:stringUser ID for the Broker.
*Password:passwordPassword that is associated with the user ID for the Broker.
* - denotes required
 ParameterTypeDescription
TLS/SSL Configuration:A provider for configuring TLS/SSL for securing SSL Context. If using AMQPS protocol and SSL Context Provider is left blank, the default provider will be used.

Select from one of the following options:
  • Default {default}
Click below for a definition:
    null
* - denotes required
Description - Generic to configure a receive JMS


Parameter Groups

 ParameterTypeDescription
*Name:stringJMS connection factory name in JNDI
UserstringUser logon id at broker
PasswordpasswordUser's password at the broker machine
* - denotes required
 ParameterTypeDescription
*Name:stringThe name of the queue or topic to be read
Type:stringSelect queue for point-to-point or topic for publish-and-subscribe

Select from one of the following options:
  • Queue {queue}
  • Topic {topic}
* - denotes required
 ParameterTypeDescription
Local ContextbooleanWhen true, connect to the default JNDI store ignoring the JNDI Factory and JNDI URL properties
URL:stringURL to reach the JNDI server
FactorystringJNDI initial context factory class. Leave blank for default.
* - denotes required
 ParameterTypeDescription
Name:stringIdentifies the subscription on a topic
Durable:booleanA durable subscription is used by an application which needs to receive all the messages published on a topic, including the ones published when there is no active consumer associated with it.
Shared:booleanA shared subscription is used by a client which needs to be able to share the work of receiving messages from a topic subscription amongst multiple consumers. JMS2 only.
Client ID:stringUniquely identifies a subscription.
* - denotes required
Description - Generic to configure a MQSeries via JMS receiving queue


Parameter Groups

 ParameterTypeDescription
Host:stringHost name or IP address, only needed for MQ client connection
Port:integerport number, only needed for MQ client connection
Channel:stringserver connection channel name, only needed for MQ client connection
Queue Manager:stringIBM MQ queue manager name
* - denotes required
 ParameterTypeDescription
User:stringUser logon id at broker
Password:passwordUser's password at the broker machine
* - denotes required
 ParameterTypeDescription
*Name:stringThe name of the queue or topic to be read
Type:stringSelect queue for point-to-point or topic for publish-and-subscribe

Select from one of the following options:
  • Queue {queue}
  • Topic {topic}
* - denotes required
 ParameterTypeDescription
Name:stringIdentifies the subscription on a topic
Durable:booleanA durable subscription is used by an application which needs to receive all the messages published on a topic, including the ones published when there is no active consumer associated with it.
Shared:booleanA shared subscription is used by a client which needs to be able to share the work of receiving messages from a topic subscription amongst multiple consumers. JMS2 only.
Client ID:stringUniquely identifies a subscription.
* - denotes required
 ParameterTypeDescription
TLS/SSL Configuration:A provider for configuring TLS/SSL for securing SSL Context. If using AMQPS protocol and SSL Context Provider is left blank, the default provider will be used.

Select from one of the following options:
  • Default {default}
Click below for a definition:
    null
SSL CipherSpec:stringThe MQ CipherSpec defines that SSL is to be used. This is configured for the channel by the IBM Websphere MQ Administrator.

Select from one of the following options:
  • DES_SHA_EXPORT
  • DES_SHA_EXPORT1024
  • ECDHE_ECDSA_3DES_EDE_CBC_SHA256
  • ECDHE_ECDSA_AES_128_CBC_SHA256
  • ECDHE_ECDSA_AES_128_GCM_SHA256
  • ECDHE_ECDSA_AES_256_CBC_SHA384
  • ECDHE_ECDSA_AES_256_GCM_SHA384
  • ECDHE_ECDSA_NULL_SHA256
  • ECDHE_ECDSA_RC4_128_SHA256
  • ECDHE_RSA_3DES_EDE_CBC_SHA256
  • ECDHE_RSA_AES_128_CBC_SHA256
  • ECDHE_RSA_AES_128_GCM_SHA256
  • ECDHE_RSA_AES_256_CBC_SHA384
  • ECDHE_RSA_AES_256_GCM_SHA384
  • ECDHE_RSA_NULL_SHA256
  • ECDHE_RSA_RC4_128_SHA256
  • FIPS_WITH_3DES_EDE_CBC_SHA
  • FIPS_WITH_DES_CBC_SHA
  • NULL_MD5
  • NULL_SHA
  • None (Not SSL) {None}
  • RC2_MD5_EXPORT
  • RC4_56_SHA_EXPORT1024
  • RC4_MD5_EXPORT
  • RC4_MD5_US
  • RC4_SHA_US
  • TLS_RSA_WITH_3DES_EDE_CBC_SHA
  • TLS_RSA_WITH_AES_128_CBC_SHA
  • TLS_RSA_WITH_AES_128_CBC_SHA256
  • TLS_RSA_WITH_AES_128_GCM_SHA256
  • TLS_RSA_WITH_AES_256_CBC_SHA
  • TLS_RSA_WITH_AES_256_CBC_SHA256
  • TLS_RSA_WITH_AES_256_GCM_SHA384
  • TLS_RSA_WITH_DES_CBC_SHA
  • TLS_RSA_WITH_NULL_SHA256
  • TLS_RSA_WITH_RC4_128_SHA256
  • TRIPLE_DES_SHA_US
* - denotes required
Description - Generic to configure a MQSeries receiving queue


Parameter Groups

 ParameterTypeDescription
Host:stringHost name or IP address, only needed for MQ client connection
Port:integerport number, only needed for MQ client connection
Channel:stringserver connection channel name, only needed for MQ client connection
Queue Manager:stringIBM MQ queue manager name
* - denotes required
 ParameterTypeDescription
Authentication:booleanIf checked, User ID must be valid on Queue Manager
User ID:stringIf Authentication is checked, User ID must be entered and be valid on Queue Manager
User Password:passwordIf Authentication is checked, Password must be entered and be valid on Queue Manager
* - denotes required
 ParameterTypeDescription
*Name:stringLocal queue from which documents are received or model queue used as template to create a dynamic queue
* - denotes required
 ParameterTypeDescription
TLS/SSL Configuration:A provider for configuring TLS/SSL for securing SSL Context. If using AMQPS protocol and SSL Context Provider is left blank, the default provider will be used.

Select from one of the following options:
  • Default {default}
Click below for a definition:
    null
SSL CipherSpec:stringThe MQ CipherSpec defines that SSL is to be used. This is configured for the channel by the IBM Websphere MQ Administrator.

Select from one of the following options:
  • DES_SHA_EXPORT
  • DES_SHA_EXPORT1024
  • ECDHE_ECDSA_3DES_EDE_CBC_SHA256
  • ECDHE_ECDSA_AES_128_CBC_SHA256
  • ECDHE_ECDSA_AES_128_GCM_SHA256
  • ECDHE_ECDSA_AES_256_CBC_SHA384
  • ECDHE_ECDSA_AES_256_GCM_SHA384
  • ECDHE_ECDSA_NULL_SHA256
  • ECDHE_ECDSA_RC4_128_SHA256
  • ECDHE_RSA_3DES_EDE_CBC_SHA256
  • ECDHE_RSA_AES_128_CBC_SHA256
  • ECDHE_RSA_AES_128_GCM_SHA256
  • ECDHE_RSA_AES_256_CBC_SHA384
  • ECDHE_RSA_AES_256_GCM_SHA384
  • ECDHE_RSA_NULL_SHA256
  • ECDHE_RSA_RC4_128_SHA256
  • FIPS_WITH_3DES_EDE_CBC_SHA
  • FIPS_WITH_DES_CBC_SHA
  • NULL_MD5
  • NULL_SHA
  • None (Not SSL) {None}
  • RC2_MD5_EXPORT
  • RC4_56_SHA_EXPORT1024
  • RC4_MD5_EXPORT
  • RC4_MD5_US
  • RC4_SHA_US
  • TLS_RSA_WITH_3DES_EDE_CBC_SHA
  • TLS_RSA_WITH_AES_128_CBC_SHA
  • TLS_RSA_WITH_AES_128_CBC_SHA256
  • TLS_RSA_WITH_AES_128_GCM_SHA256
  • TLS_RSA_WITH_AES_256_CBC_SHA
  • TLS_RSA_WITH_AES_256_CBC_SHA256
  • TLS_RSA_WITH_AES_256_GCM_SHA384
  • TLS_RSA_WITH_DES_CBC_SHA
  • TLS_RSA_WITH_NULL_SHA256
  • TLS_RSA_WITH_RC4_128_SHA256
  • TRIPLE_DES_SHA_US
* - denotes required
Description - Generic to configure a Active MQ receive queue

 

Parameter Groups

  Parameter Type Description
* URL: string URL for connection to the ActiveMQ broker; for example, tcp://host1:61616, ssl://host1:61617, or failover://(tcp://host1:123,tcp://host2:123). The URL can include options as a query string, as specified in the ActiveMQ documentation. For example, with the failover transport, you must specify a timeout, like failover://(url1,url2)?timeout=100.
  User ID: string User logon id at broker
  Password: password User's password at the broker machine
* - denotes required
  Parameter Type Description
* Name: string The name of the queue or topic to be read
  Type: string Select queue for point-to-point or topic for publish-and-subscribe

Select from one of the following options:
  • Queue {queue}
  • Topic {topic}
* - denotes required
  Parameter Type Description
  Name: string Identifies the subscription on a topic
  Durable: boolean A durable subscription is used by an application which needs to receive all the messages published on a topic, including the ones published when there is no active consumer associated with it.
  Shared: boolean A shared subscription is used by a client which needs to be able to share the work of receiving messages from a topic subscription amongst multiple consumers. JMS2 only.
  Client ID: string Uniquely identifies a subscription.
* - denotes required
  Parameter Type Description
  Configuration:   A provider for configuring TLS/SSL for securing SSL Context. If using AMQPS protocol and SSL Context Provider is left blank, the default provider will be used.

Select from one of the following options:
  • Default {default}
Click below for a definition:
  • null
* - denotes required
Description - Generic to configure a Sonic MQ sending queue


Parameter Groups

 ParameterTypeDescription
*URL:stringBroker reached on this [protocol://]host:port (can be comma separated list used for failover). Protocols are TCP, HTTP
User ID:stringUser logon id at broker
Password:passwordUser's password at the broker machine
* - denotes required
 ParameterTypeDescription
*Name:stringThe name of the queue or topic to be read
Style:stringSelect queue for point-to-point or topic for publish-and-subscribe

Select from one of the following options:
  • Queue {queue}
  • Topic {topic}
* - denotes required
 ParameterTypeDescription
Name:stringIdentifies the subscription on a topic
Durable:booleanA durable subscription is used by an application which needs to receive all the messages published on a topic, including the ones published when there is no active consumer associated with it.
Shared:booleanA shared subscription is used by a client which needs to be able to share the work of receiving messages from a topic subscription amongst multiple consumers. JMS2 only.
Client ID:stringUniquely identifies the subscription.
* - denotes required