AMQPClassic Module

Properties   Methods   Events   Config Settings   Errors  

An easy-to-use AMQP 0.9.1 client implementation, with support for RabbitMQ extensions.

Syntax

IPWorksIoT.Amqpclassic

Remarks

The AMQPClassic class provides an easy-to-use AMQP 0.9.1 client implementation, and it also supports certain RabbitMQ extensions to the AMQP 0.9.1 specification. The class supports both plaintext and TLS-enabled connections over TCP.

Connecting

The AMQP 0.9.1 transport protocol has two layers: an overall connection between the client and server, and one or more channels running over that connection.

The class implements both layers, so the first step is to initiate the overall connection. Set the AuthScheme, User, Password, SSLEnabled, and VirtualHost properties if necessary, then call the ConnectTo method, passing it the server's hostname and port number. (If the server in question is not running RabbitMQ, disabling the RabbitMQCompatible configuration setting before connecting is also recommended.)

The next step is to create at least one channel, which can be accomplished by using the CreateChannel method. The class allows creating any number of channels, up to the limit specified by the MaxChannelCount configuration setting.

Connecting and Creating a Channel // The examples in this documentation use a RabbitMQ server, which requires SASL Plain auth. amqpc1.AuthScheme = AmqpclassicAuthSchemes.smSASLPlain; amqpc1.User = "guest"; amqpc1.Password = "guest"; amqpc1.SSLEnabled = true; amqpc1.ConnectTo("amqpclassic.test-server.com", 5671); amqpc1.CreateChannel("channel");

Once the class has connected to the server, and one or more channels have been opened, the class can begin manipulating exchanges and queues, publishing messages, and creating consumers.

Note that most AMQP 0.9.1 operations can themselves vary in their complexity. The examples below are intentionally simple for the sake of clarity and brevity, but links are provided for many other parts of the class's API where more detail can be found.

Declaring Exchanges

The DeclareExchange method is used to declare (i.e., create, or verify the existence of) exchanges on the server. While all AMQP servers provide a default, direct-type exchange that all queues are bound to automatically (using their name as the routing key), more complex use-cases will often require creating additional exchanges of varying types.

Declaring an Exchange // Declare a direct-type exchange. amqpc1.DeclareExchange("channel", "MyExchange", "direct", false, false, false, false);

Exchanges can also be deleted using the DeleteExchange method.

Declaring Queues

The DeclareQueue method is used to declare (i.e., create, or verify the existence of) queues on the server. Unlike with exchanges, the server does not provide any queues by default, so declaring a queue is always necessary (unless one has already been created by another client, or configured ahead-of-time on the server itself).

Declaring a Queue // Declare a queue. amqpc1.DeclareQueue("channel", "MyQueue", false, false, false, false, false);

Queues may also be deleted or purged using the DeleteQueue and PurgeQueue methods.

Binding Queues to Exchanges

The BindQueue method is used to bind a queue to an exchange. Exchanges use the information held by their queue bindings to determine which messages to forward to which queues.

Note that all AMQP 0.9.1 servers automatically bind all queues to their default exchange (which is always a direct exchange with no name) using each queue's name as the binding's routing key. This makes it easy to send a message to a specific queue without having to declare bindings; just call PublishMessage, pass empty string for ExchangeName, and the name of the desired queue for RoutingKey.

Binding a Queue to an Exchange // Bind a queue to an exchange. Messages will only be delivered to the queue if their routing key is "MyRoutingKey". amqpc1.BindQueue("channel", "MyQueue", "MyExchange", "MyRoutingKey", false);

Queues can also be unbound from exchanges using the UnbindQueue method.

Publishing Messages

To publish a message, populate the Message* properties, and then call the PublishMessage method.

Publishing a Message amqpc1.Message.Body = "Hello, world!"; // Publish a message to the server's default (no-name) exchange, using the name of a specific queue as the routing key. amqpc1.PublishMessage("channel", "", "MyQueue", false, false); // Publish a message to the "MyExchange" exchange, using the routing key "MyRoutingKey". amqpc1.PublishMessage("channel", "MyExchange", "MyRoutingKey", false, false);

Note that outgoing messages may be handled differently by the server if the channel they are sent over is in transaction or (for RabbitMQ only) "publish confirmations" mode. Refer to the EnableTransactionMode and EnablePublishConfirms methods for more information.

Receiving Messages

There are two possible ways for the class to receive a message:

• Messages can be asynchronously pushed to the class from the server. At any point in time, the server may push a message to the class from a queue that the Consume method has been used to attach a consumer to.
• Messages can be synchronously pulled from the server by the class. The FetchMessage method is used to attempt to pull (or "fetch") messages from a specific queue.

Regardless of how they are received, all incoming messages cause the ReceivedMessage* properties to be populated and the MessageIn event to fire.

Receiving a Message // MessageIn event handler. amqpc1.OnMessageIn += (s, e) => { if (e.MessageCount == -1) { // The server pushed a message to us asynchronously due to a consumer we created. Console.WriteLine("The server pushed this message to us via consumer '" + e.ConsumerTag + "':"); Console.WriteLine(amqpc1.ReceivedMessage.Body); } else if (e.DeliveryTag > 0) { // We pulled a message from a queue with the FetchMessage() method. Console.WriteLine("Message successfully pulled:"); Console.WriteLine(amqpc1.ReceivedMessage.Body); Console.WriteLine(e.MessageCount + " messages are still available to pull."); } else { // We tried to pull a message, but there were none available to pull. Console.WriteLine("No messages available to pull."); } }; // Attach a consumer to "MyQueue". amqpc1.Consume("channel", "MyQueue", "consumerTag", false, true, false, false); // Or, try to fetch a message from "MyQueue". amqpc1.FetchMessage("channel", "MyQueue", true);

Note that the MessageIn event always fires if FetchMessage is called successfully, even if there were no messages available to fetch; refer to MessageIn for more information.

Property List

The following is the full list of the properties of the module with short descriptions. Click on the links for further details.

Method List

The following is the full list of the methods of the module with short descriptions. Click on the links for further details.

Event List

The following is the full list of the events fired by the module with short descriptions. Click on the links for further details.

Config Settings

The following is a list of config settings for the module with short descriptions. Click on the links for further details.

Arguments Property (AMQPClassic Module)

A collection of table fields that specify arguments to send to the server when calling certain methods.

Syntax

• Swift
• Objective-C

public var arguments: Array<AMQPCTableField> {
  get {...}
}

@property (nonatomic,readwrite,assign,getter=argumentCount,setter=setArgumentCount:) int argumentCount;

- (int)argumentCount;
- (void)setArgumentCount :(int)newArgumentCount;

- (NSString*)argumentName:(int)argumentIndex;
- (void)setArgumentName:(int)argumentIndex :(NSString*)newArgumentName;

- (NSString*)argumentValue:(int)argumentIndex;
- (void)setArgumentValue:(int)argumentIndex :(NSString*)newArgumentValue;

- (int)argumentValueType:(int)argumentIndex;
- (void)setArgumentValueType:(int)argumentIndex :(int)newArgumentValueType;

Default Value

"/"

Remarks

This property holds a collection of AMQPCTableField objects representing additional arguments sent when one of the following methods is called:

• Consume
• DeclareExchange
• DeclareQueue
• BindQueue
• UnbindQueue

Arguments are typically server-dependent; refer to your server's documentation to determine what, if any, arguments are supported for each of the above methods.

AuthScheme Property (AMQPClassic Module)

The authentication scheme to use when connecting.

Syntax

• Swift
• Objective-C

public var authScheme: AmqpclassicAuthSchemes {
  get {...}
  set {...}
}

public enum AmqpclassicAuthSchemes: Int32 {
  case smNone = 0
  case smSASLAnonymous = 1
  case smSASLPlain = 2
  case smSASLExternal = 3
}

@property (nonatomic,readwrite,assign,getter=authScheme,setter=setAuthScheme:) int authScheme;

- (int)authScheme;
- (void)setAuthScheme :(int)newAuthScheme;

Default Value

2

Remarks

This property controls what authentication scheme the class should use when connecting to the remote host.

Valid values are:

• smNone (0)
• smSASLAnonymous (1)
• smSASLPlain (2) - Default
• smSASLExternal (3)

Channels Property (AMQPClassic Module)

Collection of active channels.

Syntax

• Swift
• Objective-C

public var channels: Array<AMQPCChannel> {
  get {...}
}

@property (nonatomic,readonly,assign,getter=channelCount) int channelCount;

- (int)channelCount;

- (BOOL)channelAccept:(int)channelIndex;

- (int)channelMode:(int)channelIndex;

- (NSString*)channelName:(int)channelIndex;

- (BOOL)channelReadyToSend:(int)channelIndex;

Default Value

"/"

Remarks

This collection property holds a list of AMQPCChannel items, one for each currently active channel.

Refer to CreateChannel and CloseChannel for more information.

ClientProperties Property (AMQPClassic Module)

A collection of table fields that describe properties of the client.

Syntax

• Swift
• Objective-C

public var clientProperties: Array<AMQPCTableField> {
  get {...}
}

@property (nonatomic,readwrite,assign,getter=clientPropertyCount,setter=setClientPropertyCount:) int clientPropertyCount;

- (int)clientPropertyCount;
- (void)setClientPropertyCount :(int)newClientPropertyCount;

- (NSString*)clientPropertyName:(int)clientPropertyIndex;
- (void)setClientPropertyName:(int)clientPropertyIndex :(NSString*)newClientPropertyName;

- (NSString*)clientPropertyValue:(int)clientPropertyIndex;
- (void)setClientPropertyValue:(int)clientPropertyIndex :(NSString*)newClientPropertyValue;

- (int)clientPropertyValueType:(int)clientPropertyIndex;
- (void)setClientPropertyValueType:(int)clientPropertyIndex :(int)newClientPropertyValueType;

Default Value

"/"

Remarks

This property holds a collection of AMQPCTableField objects representing client properties. During the connection process, these properties will be sent to the server.

While the class does not send any client properties by default, it is common for AMQP clients to send "product", "version", and "platform" properties to help identify themselves.

Connected Property (AMQPClassic Module)

This property triggers a connection or disconnection.

Syntax

• Swift
• Objective-C

public var connected: Bool {
  get {...}
  set {...}
}

@property (nonatomic,readwrite,assign,getter=connected,setter=setConnected:) BOOL connected;

- (BOOL)connected;
- (void)setConnected :(BOOL)newConnected;

Default Value

False

Remarks

This property triggers a connection or disconnection. Setting this property to True makes the class attempt to connect to the host identified by the RemoteHost property. If successful, after the connection is achieved, the value of the property changes to True and the Connected event is fired.

Setting this property to False closes the connection. How and when the connection is closed is controlled by the Linger property.

Note: It is recommended to use the Connect or Disconnect method instead of setting this property.

Firewall Property (AMQPClassic Module)

A set of properties related to firewall access.

Syntax

• Swift
• Objective-C

public var firewall: Firewall {
  get {...}
  set {...}
}

@property (nonatomic,readwrite,assign,getter=firewallAutoDetect,setter=setFirewallAutoDetect:) BOOL firewallAutoDetect;

- (BOOL)firewallAutoDetect;
- (void)setFirewallAutoDetect :(BOOL)newFirewallAutoDetect;

@property (nonatomic,readwrite,assign,getter=firewallType,setter=setFirewallType:) int firewallType;

- (int)firewallType;
- (void)setFirewallType :(int)newFirewallType;

@property (nonatomic,readwrite,assign,getter=firewallHost,setter=setFirewallHost:) NSString* firewallHost;

- (NSString*)firewallHost;
- (void)setFirewallHost :(NSString*)newFirewallHost;

@property (nonatomic,readwrite,assign,getter=firewallPassword,setter=setFirewallPassword:) NSString* firewallPassword;

- (NSString*)firewallPassword;
- (void)setFirewallPassword :(NSString*)newFirewallPassword;

@property (nonatomic,readwrite,assign,getter=firewallPort,setter=setFirewallPort:) int firewallPort;

- (int)firewallPort;
- (void)setFirewallPort :(int)newFirewallPort;

@property (nonatomic,readwrite,assign,getter=firewallUser,setter=setFirewallUser:) NSString* firewallUser;

- (NSString*)firewallUser;
- (void)setFirewallUser :(NSString*)newFirewallUser;

 

Default Value

"/"

Remarks

This is a Firewall-type property, which contains fields describing the firewall through which the class will attempt to connect.

Heartbeat Property (AMQPClassic Module)

The heartbeat timeout value.

Syntax

• Swift
• Objective-C

public var heartbeat: Int32 {
  get {...}
  set {...}
}

@property (nonatomic,readwrite,assign,getter=heartbeat,setter=setHeartbeat:) int heartbeat;

- (int)heartbeat;
- (void)setHeartbeat :(int)newHeartbeat;

Default Value

0

Remarks

This property specifies the heartbeat timeout value, in seconds. Heartbeats are disabled if set to 0 (default).

Before connecting, this property can be set to indicate the desired heartbeat timeout value. During the connection process, the class and the server will compare their desired heartbeat values and choose the lower one.

Once connected, this property will reflect the agreed-upon heartbeat value. While the connection is idle, heartbeats are sent by both the class and the server approximately once every (Heartbeat / 2) seconds. If either side has not received a heartbeat (or other transmission) for ~Heartbeat seconds, it will consider the other side unreachable and close the connection.

This setting cannot be changed while connected.

IncomingMessages Property (AMQPClassic Module)

Collection of incoming messages which are waiting for acknowledgement.

Syntax

• Swift
• Objective-C

public var incomingMessages: Array<AMQPCMessage> {
  get {...}
}

@property (nonatomic,readonly,assign,getter=incomingMessageCount) int incomingMessageCount;

- (int)incomingMessageCount;

- (NSString*)incomingMessageAppId:(int)incomingMessageIndex;

- (NSString*)incomingMessageBody:(int)incomingMessageIndex;

- (NSData*)incomingMessageBodyB:(int)incomingMessageIndex;
- (NSString*)incomingMessageChannelName:(int)incomingMessageIndex;

- (NSString*)incomingMessageContentEncoding:(int)incomingMessageIndex;

- (NSString*)incomingMessageContentType:(int)incomingMessageIndex;

- (NSString*)incomingMessageCorrelationId:(int)incomingMessageIndex;

- (int)incomingMessageDeliveryMode:(int)incomingMessageIndex;

- (NSString*)incomingMessageExpiration:(int)incomingMessageIndex;

- (NSString*)incomingMessageHeaders:(int)incomingMessageIndex;

- (NSString*)incomingMessageId:(int)incomingMessageIndex;

- (int)incomingMessagePriority:(int)incomingMessageIndex;

- (NSString*)incomingMessageReplyTo:(int)incomingMessageIndex;

- (long long)incomingMessageTimestamp:(int)incomingMessageIndex;

- (NSString*)incomingMessageType:(int)incomingMessageIndex;

- (NSString*)incomingMessageUserId:(int)incomingMessageIndex;

Default Value

"/"

Remarks

This property holds a collection of AMQPCMessage objects that represent incoming messages the class has yet to send acknowledgements to the server for.

Refer to the MessageIn event for more information about message acknowledgements.

LocalHost Property (AMQPClassic Module)

The name of the local host or user-assigned IP interface through which connections are initiated or accepted.

Syntax

• Swift
• Objective-C

public var localHost: String {
  get {...}
  set {...}
}

@property (nonatomic,readwrite,assign,getter=localHost,setter=setLocalHost:) NSString* localHost;

- (NSString*)localHost;
- (void)setLocalHost :(NSString*)newLocalHost;

Default Value

""

Remarks

The LocalHost property contains the name of the local host as obtained by the gethostname() system call, or if the user has assigned an IP address, the value of that address.

In multi-homed hosts (machines with more than one IP interface) setting LocalHost to the value of an interface will make the class initiate connections (or accept in the case of server classs) only through that interface.

If the class is connected, the LocalHost property shows the IP address of the interface through which the connection is made in internet dotted format (aaa.bbb.ccc.ddd). In most cases, this is the address of the local host, except for multi-homed hosts (machines with more than one IP interface).

NOTE: LocalHost is not persistent. You must always set it in code, and never in the property window.

LocalPort Property (AMQPClassic Module)

The TCP port in the local host where the module binds.

Syntax

• Swift
• Objective-C

public var localPort: Int32 {
  get {...}
  set {...}
}

@property (nonatomic,readwrite,assign,getter=localPort,setter=setLocalPort:) int localPort;

- (int)localPort;
- (void)setLocalPort :(int)newLocalPort;

Default Value

0

Remarks

This property must be set before a connection is attempted. It instructs the class to bind to a specific port (or communication endpoint) in the local machine.

Setting this property to 0 (default) enables the system to choose an open port at random. The chosen port will be returned by the LocalPort property after the connection is established.

LocalPort cannot be changed once a connection is made. Any attempt to set this property when a connection is active will generate an error.

This property is useful when trying to connect to services that require a trusted port in the client side.

Message Property (AMQPClassic Module)

The message to send.

Syntax

• Swift
• Objective-C

public var message: AMQPCMessage {
  get {...}
  set {...}
}

@property (nonatomic,readwrite,assign,getter=messageAppId,setter=setMessageAppId:) NSString* messageAppId;

- (NSString*)messageAppId;
- (void)setMessageAppId :(NSString*)newMessageAppId;

@property (nonatomic,readwrite,assign,getter=messageBody,setter=setMessageBody:) NSString* messageBody;

- (NSString*)messageBody;
- (void)setMessageBody :(NSString*)newMessageBody;

@property (nonatomic,readwrite,assign,getter=messageBodyB,setter=setMessageBodyB:) NSData* messageBodyB;

- (NSData*)messageBodyB;
- (void)setMessageBodyB :(NSData*)newMessageBody;
@property (nonatomic,readonly,assign,getter=messageChannelName) NSString* messageChannelName;

- (NSString*)messageChannelName;

@property (nonatomic,readwrite,assign,getter=messageContentEncoding,setter=setMessageContentEncoding:) NSString* messageContentEncoding;

- (NSString*)messageContentEncoding;
- (void)setMessageContentEncoding :(NSString*)newMessageContentEncoding;

@property (nonatomic,readwrite,assign,getter=messageContentType,setter=setMessageContentType:) NSString* messageContentType;

- (NSString*)messageContentType;
- (void)setMessageContentType :(NSString*)newMessageContentType;

@property (nonatomic,readwrite,assign,getter=messageCorrelationId,setter=setMessageCorrelationId:) NSString* messageCorrelationId;

- (NSString*)messageCorrelationId;
- (void)setMessageCorrelationId :(NSString*)newMessageCorrelationId;

@property (nonatomic,readwrite,assign,getter=messageDeliveryMode,setter=setMessageDeliveryMode:) int messageDeliveryMode;

- (int)messageDeliveryMode;
- (void)setMessageDeliveryMode :(int)newMessageDeliveryMode;

@property (nonatomic,readwrite,assign,getter=messageExpiration,setter=setMessageExpiration:) NSString* messageExpiration;

- (NSString*)messageExpiration;
- (void)setMessageExpiration :(NSString*)newMessageExpiration;

@property (nonatomic,readwrite,assign,getter=messageHeaders,setter=setMessageHeaders:) NSString* messageHeaders;

- (NSString*)messageHeaders;
- (void)setMessageHeaders :(NSString*)newMessageHeaders;

@property (nonatomic,readwrite,assign,getter=messageId,setter=setMessageId:) NSString* messageId;

- (NSString*)messageId;
- (void)setMessageId :(NSString*)newMessageId;

@property (nonatomic,readwrite,assign,getter=messagePriority,setter=setMessagePriority:) int messagePriority;

- (int)messagePriority;
- (void)setMessagePriority :(int)newMessagePriority;

@property (nonatomic,readwrite,assign,getter=messageReplyTo,setter=setMessageReplyTo:) NSString* messageReplyTo;

- (NSString*)messageReplyTo;
- (void)setMessageReplyTo :(NSString*)newMessageReplyTo;

@property (nonatomic,readwrite,assign,getter=messageTimestamp,setter=setMessageTimestamp:) long long messageTimestamp;

- (long long)messageTimestamp;
- (void)setMessageTimestamp :(long long)newMessageTimestamp;

@property (nonatomic,readwrite,assign,getter=messageType,setter=setMessageType:) NSString* messageType;

- (NSString*)messageType;
- (void)setMessageType :(NSString*)newMessageType;

@property (nonatomic,readwrite,assign,getter=messageUserId,setter=setMessageUserId:) NSString* messageUserId;

- (NSString*)messageUserId;
- (void)setMessageUserId :(NSString*)newMessageUserId;

 

Default Value

"/"

Remarks

This property holds an AMQPCMessage object whose fields are used to construct a message to send when PublishMessage is called.

Refer to PublishMessage for more information.

Publishing a Message amqpc1.Message.Body = "Hello, world!"; // Publish a message to the server's default (no-name) exchange, using the name of a specific queue as the routing key. amqpc1.PublishMessage("channel", "", "MyQueue", false, false); // Publish a message to the "MyExchange" exchange, using the routing key "MyRoutingKey". amqpc1.PublishMessage("channel", "MyExchange", "MyRoutingKey", false, false);

OutgoingMessages Property (AMQPClassic Module)

Collection of outgoing messages which are waiting for acknowledgement.

Syntax

• Swift
• Objective-C

public var outgoingMessages: Array<AMQPCMessage> {
  get {...}
}

@property (nonatomic,readonly,assign,getter=outgoingMessageCount) int outgoingMessageCount;

- (int)outgoingMessageCount;

- (NSString*)outgoingMessageAppId:(int)outgoingMessageIndex;

- (NSString*)outgoingMessageBody:(int)outgoingMessageIndex;

- (NSData*)outgoingMessageBodyB:(int)outgoingMessageIndex;
- (NSString*)outgoingMessageChannelName:(int)outgoingMessageIndex;

- (NSString*)outgoingMessageContentEncoding:(int)outgoingMessageIndex;

- (NSString*)outgoingMessageContentType:(int)outgoingMessageIndex;

- (NSString*)outgoingMessageCorrelationId:(int)outgoingMessageIndex;

- (int)outgoingMessageDeliveryMode:(int)outgoingMessageIndex;

- (NSString*)outgoingMessageExpiration:(int)outgoingMessageIndex;

- (NSString*)outgoingMessageHeaders:(int)outgoingMessageIndex;

- (NSString*)outgoingMessageId:(int)outgoingMessageIndex;

- (int)outgoingMessagePriority:(int)outgoingMessageIndex;

- (NSString*)outgoingMessageReplyTo:(int)outgoingMessageIndex;

- (long long)outgoingMessageTimestamp:(int)outgoingMessageIndex;

- (NSString*)outgoingMessageType:(int)outgoingMessageIndex;

- (NSString*)outgoingMessageUserId:(int)outgoingMessageIndex;

Default Value

"/"

Remarks

This property holds a collection of AMQPCMessage objects that represent outgoing messages the class has yet to receive acknowledgements from the server for.

Refer to the PublishMessage method for more information.

Password Property (AMQPClassic Module)

A password to use for SASL authentication.

Syntax

• Swift
• Objective-C

public var password: String {
  get {...}
  set {...}
}

@property (nonatomic,readwrite,assign,getter=password,setter=setPassword:) NSString* password;

- (NSString*)password;
- (void)setPassword :(NSString*)newPassword;

Default Value

""

Remarks

This property contains a password to use for SASL authentication.

QueueMessageCount Property (AMQPClassic Module)

The message count returned by various queue operations.

Syntax

• Swift
• Objective-C

public var queueMessageCount: Int32 {
  get {...}
}

@property (nonatomic,readonly,assign,getter=queueMessageCount) int queueMessageCount;

- (int)queueMessageCount;

Default Value

0

Remarks

This property is populated with a message count after calling certain queue-related methods.

This property is read-only.

ReceivedMessage Property (AMQPClassic Module)

The last message received.

Syntax

• Swift
• Objective-C

public var receivedMessage: AMQPCMessage {
  get {...}
}

@property (nonatomic,readonly,assign,getter=receivedMessageAppId) NSString* receivedMessageAppId;

- (NSString*)receivedMessageAppId;

@property (nonatomic,readonly,assign,getter=receivedMessageBody) NSString* receivedMessageBody;

- (NSString*)receivedMessageBody;

@property (nonatomic,readonly,assign,getter=receivedMessageBodyB) NSData* receivedMessageBodyB;

- (NSData*)receivedMessageBodyB;
@property (nonatomic,readonly,assign,getter=receivedMessageChannelName) NSString* receivedMessageChannelName;

- (NSString*)receivedMessageChannelName;

@property (nonatomic,readonly,assign,getter=receivedMessageContentEncoding) NSString* receivedMessageContentEncoding;

- (NSString*)receivedMessageContentEncoding;

@property (nonatomic,readonly,assign,getter=receivedMessageContentType) NSString* receivedMessageContentType;

- (NSString*)receivedMessageContentType;

@property (nonatomic,readonly,assign,getter=receivedMessageCorrelationId) NSString* receivedMessageCorrelationId;

- (NSString*)receivedMessageCorrelationId;

@property (nonatomic,readonly,assign,getter=receivedMessageDeliveryMode) int receivedMessageDeliveryMode;

- (int)receivedMessageDeliveryMode;

@property (nonatomic,readonly,assign,getter=receivedMessageExpiration) NSString* receivedMessageExpiration;

- (NSString*)receivedMessageExpiration;

@property (nonatomic,readonly,assign,getter=receivedMessageHeaders) NSString* receivedMessageHeaders;

- (NSString*)receivedMessageHeaders;

@property (nonatomic,readonly,assign,getter=receivedMessageId) NSString* receivedMessageId;

- (NSString*)receivedMessageId;

@property (nonatomic,readonly,assign,getter=receivedMessagePriority) int receivedMessagePriority;

- (int)receivedMessagePriority;

@property (nonatomic,readonly,assign,getter=receivedMessageReplyTo) NSString* receivedMessageReplyTo;

- (NSString*)receivedMessageReplyTo;

@property (nonatomic,readonly,assign,getter=receivedMessageTimestamp) long long receivedMessageTimestamp;

- (long long)receivedMessageTimestamp;

@property (nonatomic,readonly,assign,getter=receivedMessageType) NSString* receivedMessageType;

- (NSString*)receivedMessageType;

@property (nonatomic,readonly,assign,getter=receivedMessageUserId) NSString* receivedMessageUserId;

- (NSString*)receivedMessageUserId;

 

Default Value

"/"

Remarks

This property is an AMQPCMessage object which represents the last message received by the class. It is populated by the class automatically each time a message is received.

Refer to Consume, FetchMessage, and MessageIn for more information.

RemoteHost Property (AMQPClassic Module)

This property includes the address of the remote host. Domain names are resolved to IP addresses.

Syntax

• Swift
• Objective-C

public var remoteHost: String {
  get {...}
  set {...}
}

@property (nonatomic,readwrite,assign,getter=remoteHost,setter=setRemoteHost:) NSString* remoteHost;

- (NSString*)remoteHost;
- (void)setRemoteHost :(NSString*)newRemoteHost;

Default Value

""

Remarks

This property specifies the IP address (IP number in dotted internet format) or the domain name of the remote host. It is set before a connection is attempted and cannot be changed once a connection is established.

If this property is set to a domain name, a DNS request is initiated, and upon successful termination of the request, this property is set to the corresponding address. If the search is not successful, an error is returned.

If the class is configured to use a SOCKS firewall, the value assigned to this property may be preceded with an "*". If this is the case, the host name is passed to the firewall unresolved and the firewall performs the DNS resolution.

Example. Connecting:

TCPClientControl.RemoteHost = "MyHostNameOrIP" TCPClientControl.RemotePort = 777 TCPClientControl.Connected = true

RemotePort Property (AMQPClassic Module)

The port of the AQMP server (default is 5672). The default port for SSL is 5671.

Syntax

• Swift
• Objective-C

public var remotePort: Int32 {
  get {...}
  set {...}
}

@property (nonatomic,readwrite,assign,getter=remotePort,setter=setRemotePort:) int remotePort;

- (int)remotePort;
- (void)setRemotePort :(int)newRemotePort;

Default Value

5672

Remarks

This property specifies a service port on the remote host to connect to.

A valid port number (a value between 1 and 65535) is required for the connection to take place. The property must be set before a connection is attempted and cannot be changed once a connection is established. Any attempt to change this property while connected will fail with an error.

ServerProperties Property (AMQPClassic Module)

A collection of table fields that describe properties of the server.

Syntax

• Swift
• Objective-C

public var serverProperties: Array<AMQPCTableField> {
  get {...}
}

@property (nonatomic,readonly,assign,getter=serverPropertyCount) int serverPropertyCount;

- (int)serverPropertyCount;

- (NSString*)serverPropertyName:(int)serverPropertyIndex;

- (NSString*)serverPropertyValue:(int)serverPropertyIndex;

- (int)serverPropertyValueType:(int)serverPropertyIndex;

Default Value

"/"

Remarks

After connecting, this property will hold a collection of AMQPCTableField objects representing server properties.

SSLAcceptServerCertEncoded Property (AMQPClassic Module)

This is the certificate (PEM/base64 encoded).

Syntax

• Swift
• Objective-C

public var sslAcceptServerCertEncoded: String {
  get {...}
  set {...}
}

public var sslAcceptServerCertEncodedB: Data {
  get {...}
  set {...}
}

@property (nonatomic,readwrite,assign,getter=SSLAcceptServerCertEncoded,setter=setSSLAcceptServerCertEncoded:) NSString* SSLAcceptServerCertEncoded;

- (NSString*)SSLAcceptServerCertEncoded;
- (void)setSSLAcceptServerCertEncoded :(NSString*)newSSLAcceptServerCertEncoded;

@property (nonatomic,readwrite,assign,getter=SSLAcceptServerCertEncodedB,setter=setSSLAcceptServerCertEncodedB:) NSData* SSLAcceptServerCertEncodedB;

- (NSData*)SSLAcceptServerCertEncodedB;
- (void)setSSLAcceptServerCertEncodedB :(NSData*)newSSLAcceptServerCertEncoded;

Default Value

""

Remarks

This is the certificate (PEM/Base64 encoded). This property is used to assign a specific certificate. The SSLAcceptServerCertStore and SSLAcceptServerCertSubject properties also may be used to specify a certificate.

When SSLAcceptServerCertEncoded is set, a search is initiated in the current SSLAcceptServerCertStore for the private key of the certificate. If the key is found, SSLAcceptServerCertSubject is updated to reflect the full subject of the selected certificate; otherwise, SSLAcceptServerCertSubject is set to an empty string.

If an error occurs when setting this property an error will not be thrown. This property has a related method which will throw an error:

public func setSSLAcceptServerCertEncodedB(sslAcceptServerCertEncoded: Data) throws
public func setSSLAcceptServerCertEncoded(sslAcceptServerCertEncoded: String) throws

SSLCertEncoded Property (AMQPClassic Module)

This is the certificate (PEM/base64 encoded).

Syntax

• Swift
• Objective-C

public var sslCertEncoded: String {
  get {...}
  set {...}
}

public var sslCertEncodedB: Data {
  get {...}
  set {...}
}

@property (nonatomic,readwrite,assign,getter=SSLCertEncoded,setter=setSSLCertEncoded:) NSString* SSLCertEncoded;

- (NSString*)SSLCertEncoded;
- (void)setSSLCertEncoded :(NSString*)newSSLCertEncoded;

@property (nonatomic,readwrite,assign,getter=SSLCertEncodedB,setter=setSSLCertEncodedB:) NSData* SSLCertEncodedB;

- (NSData*)SSLCertEncodedB;
- (void)setSSLCertEncodedB :(NSData*)newSSLCertEncoded;

Default Value

""

Remarks

This is the certificate (PEM/Base64 encoded). This property is used to assign a specific certificate. The SSLCertStore and SSLCertSubject properties also may be used to specify a certificate.

When SSLCertEncoded is set, a search is initiated in the current SSLCertStore for the private key of the certificate. If the key is found, SSLCertSubject is updated to reflect the full subject of the selected certificate; otherwise, SSLCertSubject is set to an empty string.

If an error occurs when setting this property an error will not be thrown. This property has a related method which will throw an error:

public func setSSLCertEncodedB(sslCertEncoded: Data) throws
public func setSSLCertEncoded(sslCertEncoded: String) throws

SSLCertStore Property (AMQPClassic Module)

This is the name of the certificate store for the client certificate.

Syntax

• Swift
• Objective-C

public var sslCertStore: String {
  get {...}
  set {...}
}

public var sslCertStoreB: Data {
  get {...}
  set {...}
}

@property (nonatomic,readwrite,assign,getter=SSLCertStore,setter=setSSLCertStore:) NSString* SSLCertStore;

- (NSString*)SSLCertStore;
- (void)setSSLCertStore :(NSString*)newSSLCertStore;

@property (nonatomic,readwrite,assign,getter=SSLCertStoreB,setter=setSSLCertStoreB:) NSData* SSLCertStoreB;

- (NSData*)SSLCertStoreB;
- (void)setSSLCertStoreB :(NSData*)newSSLCertStore;

Default Value

"MY"

Remarks

This is the name of the certificate store for the client certificate.

The SSLCertStoreType property denotes the type of the certificate store specified by SSLCertStore. If the store is password protected, specify the password in SSLCertStorePassword.

SSLCertStore is used in conjunction with the SSLCertSubject property to specify client certificates. If SSLCertStore has a value, and SSLCertSubject or SSLCertEncoded is set, a search for a certificate is initiated. Please see the SSLCertSubject property for details.

Designations of certificate stores are platform dependent.

The following designations are the most common User and Machine certificate stores in Windows:

When the certificate store type is PFXFile, this property must be set to the name of the file. When the type is PFXBlob, the property must be set to the binary contents of a PFX file (i.e., PKCS#12 certificate store).

SSLCertStorePassword Property (AMQPClassic Module)

If the type of certificate store requires a password, this property is used to specify the password needed to open the certificate store.

Syntax

• Swift
• Objective-C

public var sslCertStorePassword: String {
  get {...}
  set {...}
}

@property (nonatomic,readwrite,assign,getter=SSLCertStorePassword,setter=setSSLCertStorePassword:) NSString* SSLCertStorePassword;

- (NSString*)SSLCertStorePassword;
- (void)setSSLCertStorePassword :(NSString*)newSSLCertStorePassword;

Default Value

""

Remarks

If the type of certificate store requires a password, this property is used to specify the password needed to open the certificate store.

SSLCertStoreType Property (AMQPClassic Module)

This is the type of certificate store for this certificate.

Syntax

• Swift
• Objective-C

public var sslCertStoreType: AmqpclassicSSLCertStoreTypes {
  get {...}
  set {...}
}

public enum AmqpclassicSSLCertStoreTypes: Int32 {
  case cstUser = 0
  case cstMachine = 1
  case cstPFXFile = 2
  case cstPFXBlob = 3
  case cstJKSFile = 4
  case cstJKSBlob = 5
  case cstPEMKeyFile = 6
  case cstPEMKeyBlob = 7
  case cstPublicKeyFile = 8
  case cstPublicKeyBlob = 9
  case cstSSHPublicKeyBlob = 10
  case cstP7BFile = 11
  case cstP7BBlob = 12
  case cstSSHPublicKeyFile = 13
  case cstPPKFile = 14
  case cstPPKBlob = 15
  case cstXMLFile = 16
  case cstXMLBlob = 17
  case cstJWKFile = 18
  case cstJWKBlob = 19
  case cstSecurityKey = 20
  case cstBCFKSFile = 21
  case cstBCFKSBlob = 22
  case cstPKCS11 = 23
  case cstAuto = 99
}

@property (nonatomic,readwrite,assign,getter=SSLCertStoreType,setter=setSSLCertStoreType:) int SSLCertStoreType;

- (int)SSLCertStoreType;
- (void)setSSLCertStoreType :(int)newSSLCertStoreType;

Default Value

0

Remarks

This is the type of certificate store for this certificate.

The class supports both public and private keys in a variety of formats. When the cstAuto value is used, the class will automatically determine the type. This property can take one of the following values:

SSLCertSubject Property (AMQPClassic Module)

This is the subject of the certificate used for client authentication.

Syntax

• Swift
• Objective-C

public var sslCertSubject: String {
  get {...}
  set {...}
}

@property (nonatomic,readwrite,assign,getter=SSLCertSubject,setter=setSSLCertSubject:) NSString* SSLCertSubject;

- (NSString*)SSLCertSubject;
- (void)setSSLCertSubject :(NSString*)newSSLCertSubject;

Default Value

""

Remarks

This is the subject of the certificate used for client authentication.

This property must be set after all other certificate properties are set. When this property is set, a search is performed in the current certificate store to locate a certificate with a matching subject.

If a matching certificate is found, the property is set to the full subject of the matching certificate.

If an exact match is not found, the store is searched for subjects containing the value of the property.

If a match is still not found, the property is set to an empty string, and no certificate is selected.

The special value "*" picks a random certificate in the certificate store.

The certificate subject is a comma-separated list of distinguished name fields and values. For instance, "CN=www.server.com, OU=test, C=US, E=support@nsoftware.com". Common fields and their meanings are as follows:

If a field value contains a comma, it must be quoted.

If an error occurs when setting this property an error will not be thrown. This property has a related method which will throw an error:

public func setSSLCertSubject(sslCertSubject: String) throws

SSLEnabled Property (AMQPClassic Module)

Whether TLS/SSL is enabled.

Syntax

• Swift
• Objective-C

public var sslEnabled: Bool {
  get {...}
  set {...}
}

@property (nonatomic,readwrite,assign,getter=SSLEnabled,setter=setSSLEnabled:) BOOL SSLEnabled;

- (BOOL)SSLEnabled;
- (void)setSSLEnabled :(BOOL)newSSLEnabled;

Default Value

False

Remarks

This setting specifies whether TLS/SSL is enabled in the class. When False (default) the class operates in plaintext mode. When True TLS/SSL is enabled.

TLS/SSL may also be enabled by setting SSLStartMode. Setting SSLStartMode will automatically update this property value.

If the default port (5672) is selected when SSLEnabled is set to true, the port will automatically be changed to the default port for AMQP with SSL (5671). Likewise, if port 5671 is selected when SSLEnabled is set to false, the port will automatically be changed to the default port. If the port has been set to any value other than the default values, it will remain the same when the value of SSLEnabled changes.

SSLProvider Property (AMQPClassic Module)

This specifies the SSL/TLS implementation to use.

Syntax

• Swift
• Objective-C

public var sslProvider: AmqpclassicSSLProviders {
  get {...}
  set {...}
}

public enum AmqpclassicSSLProviders: Int32 {
  case sslpAutomatic = 0
  case sslpPlatform = 1
  case sslpInternal = 2
}

@property (nonatomic,readwrite,assign,getter=SSLProvider,setter=setSSLProvider:) int SSLProvider;

- (int)SSLProvider;
- (void)setSSLProvider :(int)newSSLProvider;

Default Value

0

Remarks

This property specifies the SSL/TLS implementation to use. In most cases the default value of 0 (Automatic) is recommended and should not be changed. When set to 0 (Automatic) the class will select whether to use the platform implementation or the internal implementation depending on the operating system as well as the TLS version being used.

Possible values are:

In most cases using the default value (Automatic) is recommended. The class will select a provider depending on the current platform.

When Automatic is selected the platform implementation will be used by default in all cases in the macOS edition.

SSLServerCertEncoded Property (AMQPClassic Module)

This is the certificate (PEM/base64 encoded).

Syntax

• Swift
• Objective-C

public var sslServerCertEncoded: String {
  get {...}
}

public var sslServerCertEncodedB: Data {
  get {...}
}

@property (nonatomic,readonly,assign,getter=SSLServerCertEncoded) NSString* SSLServerCertEncoded;

- (NSString*)SSLServerCertEncoded;

@property (nonatomic,readonly,assign,getter=SSLServerCertEncodedB) NSData* SSLServerCertEncodedB;

- (NSData*)SSLServerCertEncodedB;

Default Value

""

Remarks

This is the certificate (PEM/Base64 encoded). This property is used to assign a specific certificate. The SSLServerCertStore and SSLServerCertSubject properties also may be used to specify a certificate.

When SSLServerCertEncoded is set, a search is initiated in the current SSLServerCertStore for the private key of the certificate. If the key is found, SSLServerCertSubject is updated to reflect the full subject of the selected certificate; otherwise, SSLServerCertSubject is set to an empty string.

This property is read-only.

If an error occurs when setting this property an error will not be thrown. This property has a related method which will throw an error:

public func setSSLServerCertEncodedB(sslServerCertEncoded: Data) throws
public func setSSLServerCertEncoded(sslServerCertEncoded: String) throws

Timeout Property (AMQPClassic Module)

A timeout for the module.

Syntax

• Swift
• Objective-C

public var timeout: Int32 {
  get {...}
  set {...}
}

@property (nonatomic,readwrite,assign,getter=timeout,setter=setTimeout:) int timeout;

- (int)timeout;
- (void)setTimeout :(int)newTimeout;

Default Value

60

Remarks

If the Timeout property is set to 0, all operations return immediately, potentially failing with a WOULDBLOCK error if data cannot be sent immediately.

If Timeout is set to a positive value, data is sent in a blocking manner and the class will wait for the operation to complete before returning control. The class will handle any potential WOULDBLOCK errors internally and automatically retry the operation for a maximum of Timeout seconds.

The class will use DoEvents to enter an efficient wait loop during any potential waiting period, making sure that all system events are processed immediately as they arrive. This ensures that the host application does not "freeze" and remains responsive.

If Timeout expires, and the operation is not yet complete, the class .

Please note that by default, all timeouts are inactivity timeouts, i.e. the timeout period is extended by Timeout seconds when any amount of data is successfully sent or received.

The default value for the Timeout property is 60 seconds.

User Property (AMQPClassic Module)

A username to use for SASL authentication.

Syntax

• Swift
• Objective-C

public var user: String {
  get {...}
  set {...}
}

@property (nonatomic,readwrite,assign,getter=user,setter=setUser:) NSString* user;

- (NSString*)user;
- (void)setUser :(NSString*)newUser;

Default Value

""

Remarks

This property contains a username to use for SASL authentication.

VirtualHost Property (AMQPClassic Module)

The virtual host to connect to.

Syntax

• Swift
• Objective-C

public var virtualHost: String {
  get {...}
  set {...}
}

@property (nonatomic,readwrite,assign,getter=virtualHost,setter=setVirtualHost:) NSString* virtualHost;

- (NSString*)virtualHost;
- (void)setVirtualHost :(NSString*)newVirtualHost;

Default Value

"/"

Remarks

This property specifies the virtual host to connect to on the server, and is set to / by default.

Note that the configuration of the server defines what virtual hosts are available.

This setting cannot be changed while connected.

BindQueue Method (AMQPClassic Module)

Binds a queue to an exchange.

Syntax

• Swift
• Objective-C

public func bindQueue(channelName: String, queueName: String, exchangeName: String, routingKey: String, noWait: Bool) throws -> Void

- (void)bindQueue:(NSString*)channelName :(NSString*)queueName :(NSString*)exchangeName :(NSString*)routingKey :(BOOL)noWait;

Remarks

This method is used to bind the queue named QueueName to the exchange named ExchangeName. Exchanges use bindings to determine which queues to route messages to.

Multiple bindings between the same queue and exchange with different RoutingKeys and/or arguments are allowed; requests that would create a duplicate binding are ignored. No queue will ever receive duplicate copies of any message, regardless of what bindings are present on the server.

Note that all AMQP 0.9.1 servers automatically bind all queues to their default exchange (which is always a direct exchange with no name) using each queue's name as the binding's routing key. This makes it easy to send a message to a specific queue without having to declare bindings; just call PublishMessage, pass empty string for ExchangeName, and the name of the desired queue for RoutingKey.

ChannelName controls what channel the class will send the request over. While any channel can technically be used, keep in mind that the server will close it if a channel error occurs. For this reason, it is good practice to make requests such as this one using a channel that is not involved in message publishing or consumption.

QueueName must be a non-empty string consisting only of letters, digits, hyphens, underscores, periods, and colons. It must be no longer than 255 characters.

The server's default exchange may be specified by passing empty string for ExchangeName. Otherwise, ExchangeName must be a non-empty string consisting only of letters, digits, hyphens, underscores, periods, and colons. It must be no longer than 255 characters.

The RoutingKey parameter specifies the binding's routing key. Exchanges that use routing-key-based logic make some sort of comparison between the routing keys of incoming messages and this value to decide which messages should be forwarded to the specified queue. Examples of exchange types which use routing keys include:

• direct exchanges, which compare (for equality) the routing keys of incoming messages to the routing keys of each queue bound to them.
• topic exchanges, which match the routing keys of incoming messages against the routing pattern of each queue bound to them.

Not all exchange types make use of routing keys, in which case empty string can be passed for the RoutingKey parameter. Examples of exchange types which don't use routing keys include:

• fanout exchanges simply forward incoming messages to all queues bound to them, unconditionally.
• header exchanges only forward messages that include certain headers. When binding a queue to a header exchange, add items to the Argument* properties to describe the headers that eligible messages must have, and whether they must have any or all of those headers.

Note that the format of the RoutingKey parameter and/or the content of the Argument* properties may differ slightly between server implementations. Refer to your server's documentation to determine what it expects to receive for each exchange type that it supports.

The NoWait parameter, if True, will cause the server to execute the request asynchronously. For asynchronous request handling, the server only sends back a response in case of an error.

An exception is thrown if no channel with the given ChannelName exists, or if the server returns an error because:

• No queue with the given QueueName exists.
• No exchange with the given ExchangeName exists.

Note that in AMQP, server errors are grouped into "connection errors" and "channel errors", and both are fatal. That is, if the server returns a channel error, it will then close the channel which caused the error; and if it returns a connection error, it will then close the connection. The AMQPClassic class's Error Codes page includes AMQP's various connection and channel errors.

Binding a Queue to an Exchange // Bind a queue to an exchange. Messages will only be delivered to the queue if their routing key is "MyRoutingKey". amqpc1.BindQueue("channel", "MyQueue", "MyExchange", "MyRoutingKey", false);

CancelConsume Method (AMQPClassic Module)

Cancels an existing consumer.

Syntax

• Swift
• Objective-C

public func cancelConsume(channelName: String, consumerTag: String, noWait: Bool) throws -> Void

- (void)cancelConsume:(NSString*)channelName :(NSString*)consumerTag :(BOOL)noWait;

Remarks

This method requests that the server cancel the consumer identified by the given ConsumerTag on the channel specified by ChannelName.

The NoWait parameter, if True, will cause the server to execute the request asynchronously. For asynchronous request handling, the server only sends back a response in case of an error.

An exception is thrown if no channel with the given ChannelName exists, or if the server returns an error because no consumer with the given ConsumerTag exists.

Note that in AMQP, server errors are grouped into "connection errors" and "channel errors", and both are fatal. That is, if the server returns a channel error, it will then close the channel which caused the error; and if it returns a connection error, it will then close the connection. The AMQPClassic class's Error Codes page includes AMQP's various connection and channel errors.

CloseChannel Method (AMQPClassic Module)

Closes a channel.

Syntax

• Swift
• Objective-C

public func closeChannel(channelName: String) throws -> Void

- (void)closeChannel:(NSString*)channelName;

Remarks

This method closes the channel named ChannelName and removes it from the Channel* properties.

If no channel with the given ChannelName exists, an exception will be thrown.

CommitTransaction Method (AMQPClassic Module)

Commits the current transaction for a channel.

Syntax

• Swift
• Objective-C

public func commitTransaction(channelName: String) throws -> Void

- (void)commitTransaction:(NSString*)channelName;

Remarks

This method commits the current transaction for the channel with the given ChannelName. A new transaction is started immediately after the current one is committed.

Refer to EnableTransactionMode for more information about transactions.

An exception is thrown if a channel with the given ChannelName doesn't exist, or if the server returns an error because the channel does not have transaction mode enabled.

Note that in AMQP, server errors are grouped into "connection errors" and "channel errors", and both are fatal. That is, if the server returns a channel error, it will then close the channel which caused the error; and if it returns a connection error, it will then close the connection. The AMQPClassic class's Error Codes page includes AMQP's various connection and channel errors.

Config Method (AMQPClassic Module)

Sets or retrieves a configuration setting.

Syntax

• Swift
• Objective-C

public func config(configurationString: String) throws -> String

- (NSString*)config:(NSString*)configurationString;

Remarks

Config is a generic method available in every class. It is used to set and retrieve configuration settings for the class.

These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the class, access to these internal properties is provided through the Config method.

To set a configuration setting named PROPERTY, you must call Config("PROPERTY=VALUE"), where VALUE is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter).

To read (query) the value of a configuration setting, you must call Config("PROPERTY"). The value will be returned as a string.

Connect Method (AMQPClassic Module)

This method connects to a remote host.

Syntax

• Swift
• Objective-C

public func connect() throws -> Void

- (void)connect;

Remarks

This method connects to the remote host specified by RemoteHost and RemotePort. For instance: component.RemoteHost = "MyHostNameOrIP"; component.RemotePort = 7777; component.Connect();

ConnectTo Method (AMQPClassic Module)

This method connects to a remote host.

Syntax

• Swift
• Objective-C

public func connectTo(host: String, port: Int32) throws -> Void

- (void)connectTo:(NSString*)host :(int)port;

Remarks

This method connects to the remote host specified by the Host and Port parameters. For instance: component.ConnectTo("MyHostNameOrIP", 777)

Consume Method (AMQPClassic Module)

Starts a new consumer for a given queue.

Syntax

• Swift
• Objective-C

public func consume(channelName: String, queueName: String, consumerTag: String, noLocal: Bool, noAck: Bool, exclusive: Bool, noWait: Bool) throws -> Void

- (void)consume:(NSString*)channelName :(NSString*)queueName :(NSString*)consumerTag :(BOOL)noLocal :(BOOL)noAck :(BOOL)exclusive :(BOOL)noWait;

Remarks

This method instructs the server to start a new consumer on the queue named QueueName; once the consumer is created, it will cause messages enqueued to the specified queue to be delivered to the class over the channel specified by ChannelName.

Consumers last as long as the channel they were created on, or until they are cancelled using the CancelConsume method. Each time a message is delivered to the class, it is immediately added to the IncomingMessage* properties, the ReceivedMessage* properties are populated, and the MessageIn event fires.

ConsumerTag is a string which uniquely identifies the new consumer on the specified channel. If empty string is passed for ConsumerTag, the server will generate a consumer tag automatically when it creates the . this auto-generated consumer tag can then be retrieved by querying the ConsumerTag configuration setting after this method returns.

The NoLocal parameter, if True, ensures that the consumer never consumes messages published on the same channel. (Note that this functionality is not available on RabbitMQ servers, which ignore the NoLocal parameter).

The NoAck parameter controls whether the server will expect the class to acknowledge the each message delivered. Refer to MessageIn for more information about acknowledging messages.

The Exclusive parameter, if True, will cause the class to request that the server create an exclusive consumer. Attaching an exclusive consumer to a queue prevents any other consumers from consuming messages from that queue.

The NoWait parameter, if True, will cause the server to execute the request asynchronously. For asynchronous request handling, the server only sends back a response in case of an error.

Additional arguments may be sent with this request by adding them to the Argument* properties. Arguments are server-dependent; refer to your server's documentation to determine if any additional arguments apply for this request.

An exception is thrown if no channel with the given ChannelName exists, or if the server returns an error because:

• No queue with the given QueueName exists.
• The given ConsumerTag is already in use on the specified channel.
• An exclusive consumer was requested for a queue which already has consumers attached to it.

Note that in AMQP, server errors are grouped into "connection errors" and "channel errors", and both are fatal. That is, if the server returns a channel error, it will then close the channel which caused the error; and if it returns a connection error, it will then close the connection. The AMQPClassic class's Error Codes page includes AMQP's various connection and channel errors.

Receiving a Message // MessageIn event handler. amqpc1.OnMessageIn += (s, e) => { if (e.MessageCount == -1) { // The server pushed a message to us asynchronously due to a consumer we created. Console.WriteLine("The server pushed this message to us via consumer '" + e.ConsumerTag + "':"); Console.WriteLine(amqpc1.ReceivedMessage.Body); } else if (e.DeliveryTag > 0) { // We pulled a message from a queue with the FetchMessage() method. Console.WriteLine("Message successfully pulled:"); Console.WriteLine(amqpc1.ReceivedMessage.Body); Console.WriteLine(e.MessageCount + " messages are still available to pull."); } else { // We tried to pull a message, but there were none available to pull. Console.WriteLine("No messages available to pull."); } }; // Attach a consumer to "MyQueue". amqpc1.Consume("channel", "MyQueue", "consumerTag", false, true, false, false); // Or, try to fetch a message from "MyQueue". amqpc1.FetchMessage("channel", "MyQueue", true);

CreateChannel Method (AMQPClassic Module)

Creates a new channel.

Syntax

• Swift
• Objective-C

public func createChannel(channelName: String) throws -> Void

- (void)createChannel:(NSString*)channelName;

Remarks

This method creates a new channel with the name ChannelName and adds it to the Channel* properties. If a channel with the given ChannelName already exists, an error will be thrown.

Connecting and Creating a Channel // The examples in this documentation use a RabbitMQ server, which requires SASL Plain auth. amqpc1.AuthScheme = AmqpclassicAuthSchemes.smSASLPlain; amqpc1.User = "guest"; amqpc1.Password = "guest"; amqpc1.SSLEnabled = true; amqpc1.ConnectTo("amqpclassic.test-server.com", 5671); amqpc1.CreateChannel("channel");

DeclareExchange Method (AMQPClassic Module)

Verifies that an exchange exists, potentially creating it if necessary.

Syntax

• Swift
• Objective-C

public func declareExchange(channelName: String, exchangeName: String, exchangeType: String, passive: Bool, durable: Bool, autoDelete: Bool, noWait: Bool) throws -> Void

- (void)declareExchange:(NSString*)channelName :(NSString*)exchangeName :(NSString*)exchangeType :(BOOL)passive :(BOOL)durable :(BOOL)autoDelete :(BOOL)noWait;

Remarks

This method is used to verify that an exchange named ExchangeName exists; and potentially creates it if no such exchange exists.

ChannelName controls what channel the class will send the request over. While any channel can technically be used, keep in mind that the server will close it if a channel error occurs. For this reason, it is good practice to make requests such as this one using a channel that is not involved in message publishing or consumption.

ExchangeName must be a non-empty string consisting only of letters, digits, hyphens, underscores, periods, and colons. It must be no longer than 255 characters, and must not begin with amq. unless the Passive parameter is True.

ExchangeType specifies the exchange type. All servers support the direct and fanout exchange types, and most should also support the topic and header exchange types. Some servers may support additional, custom exchange types as well. Refer to your server's documentation for more information about each exchange type, and to determine what exchange types it supports other than direct and fanout.

If Passive is True, the server will only verify that an exchange with the given ExchangeName actually exists (regardless of how it is configured).

If Passive is False, and no exchange named ExchangeName currently exists, the server will create one.

If Passive is False, and there is a preexisting exchange named ExchangeName, the server will verify that its current configuration matches the given parameters and arguments.

Durable specifies what happens to the exchange in the event of a server restart. Durable exchanges will be recreated, while non-durable (transient) exchanges will not.

AutoDelete specifies whether the server should automatically delete the exchange when all queues have been unbound from it. Note that this parameter is only sent if the RabbitMQCompatible configuration setting is enabled; it is ignored otherwise.

The NoWait parameter, if True, will cause the server to execute the request asynchronously. For asynchronous request handling, the server only sends back a response in case of an error.

Additional arguments may be sent with this request by adding them to the Argument* properties. Arguments are server-dependent; refer to your server's documentation to determine if any additional arguments apply for this request.

An exception is thrown if no channel with the given ChannelName exists, or if the server returns an error because:

• One of the parameter constraints described above was violated.
• One of the verification cases described above fails.
• The value passed for ExchangeType did not correspond to an exchange type supported by the server.

Note that in AMQP, server errors are grouped into "connection errors" and "channel errors", and both are fatal. That is, if the server returns a channel error, it will then close the channel which caused the error; and if it returns a connection error, it will then close the connection. The AMQPClassic class's Error Codes page includes AMQP's various connection and channel errors.

Declaring an Exchange // Declare a direct-type exchange. amqpc1.DeclareExchange("channel", "MyExchange", "direct", false, false, false, false);

DeclareQueue Method (AMQPClassic Module)

Verifies that a queue exists, potentially creating it if necessary.

Syntax

• Swift
• Objective-C

public func declareQueue(channelName: String, queueName: String, passive: Bool, durable: Bool, exclusive: Bool, autoDelete: Bool, noWait: Bool) throws -> Void

- (void)declareQueue:(NSString*)channelName :(NSString*)queueName :(BOOL)passive :(BOOL)durable :(BOOL)exclusive :(BOOL)autoDelete :(BOOL)noWait;

Remarks

This method is used to verify that a queue named QueueName exists; and potentially creates it if no such queue exists.

After each successful call to this method, the class populates the QueueMessageCount property, as well as the QueueConsumerCount and QueueName configuration settings. Refer to each one for more information.

ChannelName controls what channel the class will send the request over. While any channel can technically be used, keep in mind that the server will close it if a channel error occurs. For this reason, it is good practice to make requests such as this one using a channel that is not involved in message publishing or consumption.

If creating a new queue, empty string can be passed for QueueName to have the server automatically generate a name for the new queue (which can then be retrieved using the QueueName configuration setting). In all other cases, QueueName must be a non-empty string consisting only of letters, digits, hyphens, underscores, periods, and colons. It must be no longer than 255 characters, and must not begin with amq. unless the Passive parameter is True.

If Passive is True, the server will only verify that a queue with the given QueueName actually exists (regardless of how it is configured).

If Passive is False, and no queue named QueueName currently exists, the server will create one.

If Passive is False, and there is a preexisting queue named QueueName, the server will verify that its current configuration matches the given parameters and arguments.

Durable specifies what happens to the queue in the event of a server restart. Durable queue will be recreated, while non-durable (transient) queue will not. (Note that the messages in durable queues will still be lost unless they are marked as persistent.)

Exclusive, if True, indicates that the queue may only be accessed by the current connection. Exclusive queues are deleted when the current connection closes.

AutoDelete specifies whether the server should automatically delete the queue when all consumers have finished using it. (Note that auto-delete queues aren't eligible for deletion until after a consumer attaches to them for the first time.)

The NoWait parameter, if True, will cause the server to execute the request asynchronously. For asynchronous request handling, the server only sends back a response in case of an error.

Additional arguments may be sent with this request by adding them to the Argument* properties. Arguments are server-dependent; refer to your server's documentation to determine if any additional arguments apply for this request.

An exception is thrown if no channel with the given ChannelName exists, if QueueName empty string and NoWait is True, or if the server returns an error because:

• One of the parameter constraints described above was violated.
• One of the verification cases described above fails.
• An attempt was made to verify (i.e., the Passive parameter was True) another connection's exclusive queue.

Note that in AMQP, server errors are grouped into "connection errors" and "channel errors", and both are fatal. That is, if the server returns a channel error, it will then close the channel which caused the error; and if it returns a connection error, it will then close the connection. The AMQPClassic class's Error Codes page includes AMQP's various connection and channel errors.

Declaring a Queue // Declare a queue. amqpc1.DeclareQueue("channel", "MyQueue", false, false, false, false, false);

DeleteExchange Method (AMQPClassic Module)

Deletes an exchange.

Syntax

• Swift
• Objective-C

public func deleteExchange(channelName: String, exchangeName: String, ifUnused: Bool, noWait: Bool) throws -> Void

- (void)deleteExchange:(NSString*)channelName :(NSString*)exchangeName :(BOOL)ifUnused :(BOOL)noWait;

Remarks

This method is used to delete an exchange.

ChannelName controls what channel the class will send the request over. While any channel can technically be used, keep in mind that the server will close it if a channel error occurs. For this reason, it is good practice to make requests such as this one using a channel that is not involved in message publishing or consumption.

ExchangeName must be a non-empty string consisting only of letters, digits, hyphens, underscores, periods, and colons. It must be no longer than 255 characters, and must not begin with amq..

When IfUnused is True, the server will only delete the exchange if no queues are bound to it.

The NoWait parameter, if True, will cause the server to execute the request asynchronously. For asynchronous request handling, the server only sends back a response in case of an error.

An exception is thrown if no channel with the given ChannelName exists, or if the server returns an error because:

• The value passed for ExchangeName fails one or more of the constraints described above.
• No exchange named ExchangeName exists. (This does not apply for RabbitMQ; attempting to delete a non-existent exchange will always succeed.)
• The IfUnused parameter was True, but the exchange still had one or more queues bound to it.

Note that in AMQP, server errors are grouped into "connection errors" and "channel errors", and both are fatal. That is, if the server returns a channel error, it will then close the channel which caused the error; and if it returns a connection error, it will then close the connection. The AMQPClassic class's Error Codes page includes AMQP's various connection and channel errors.

DeleteQueue Method (AMQPClassic Module)

Deletes a queue.

Syntax

• Swift
• Objective-C

public func deleteQueue(channelName: String, queueName: String, ifUnused: Bool, ifEmpty: Bool, noWait: Bool) throws -> Void

- (void)deleteQueue:(NSString*)channelName :(NSString*)queueName :(BOOL)ifUnused :(BOOL)ifEmpty :(BOOL)noWait;

Remarks

This method is used to delete the queue named QueueName.

After each successful call to this method, the class populates the QueueMessageCount property with the number of messages deleted along with the queue. (Note that this does not occur if the NoWait parameter is set to True.)

ChannelName controls what channel the class will send the request over. While any channel can technically be used, keep in mind that the server will close it if a channel error occurs. For this reason, it is good practice to make requests such as this one using a channel that is not involved in message publishing or consumption.

QueueName must be a non-empty string consisting only of letters, digits, hyphens, underscores, periods, and colons. It must be no longer than 255 characters, and must not begin with amq..

When IfUnused is True, the server will only delete the queue if no consumers are attached to it.

When IfEmpty is True, the server will only delete the queue if it has no messages in it. (When IfEmpty is False, servers will typically move any remaining messages to a dead-letter queue, if one is available.)

The NoWait parameter, if True, will cause the server to execute the request asynchronously. For asynchronous request handling, the server only sends back a response in case of an error.

An exception is thrown if no channel with the given ChannelName exists, or if the server returns an error because:

• The value passed for QueueName fails one or more of the constraints described above.
• No queue named QueueName exists. (This does not apply for RabbitMQ; attempting to delete a non-existent queue will always succeed.)
• The IfUnused parameter was True, but the queue still had one or more consumers attached to it.
• The IfEmpty parameter was True, but the queue still had one or more messages in it.

Note that in AMQP, server errors are grouped into "connection errors" and "channel errors", and both are fatal. That is, if the server returns a channel error, it will then close the channel which caused the error; and if it returns a connection error, it will then close the connection. The AMQPClassic class's Error Codes page includes AMQP's various connection and channel errors.

Disconnect Method (AMQPClassic Module)

This method disconnects from the remote host.

Syntax

• Swift
• Objective-C

public func disconnect() throws -> Void

- (void)disconnect;

Remarks

This method disconnects from the remote host. Calling this method is equivalent to setting the Connected property to False.

DoEvents Method (AMQPClassic Module)

Processes events from the internal message queue.

Syntax

• Swift
• Objective-C

public func doEvents() throws -> Void

- (void)doEvents;

Remarks

When DoEvents is called, the class processes any available events. If no events are available, it waits for a preset period of time, and then returns.

EnablePublishConfirms Method (AMQPClassic Module)

Enables publish confirmations mode for a channel.

Syntax

• Swift
• Objective-C

public func enablePublishConfirms(channelName: String, noWait: Bool) throws -> Void

- (void)enablePublishConfirms:(NSString*)channelName :(BOOL)noWait;

Remarks

This method enables publish confirmations mode for the channel with the given ChannelName.

While a channel is in publish confirmations mode, the server will acknowledge each message published by the class. The class will wait to fire the MessageOut event until it receives this acknowledgement. (Note that this mode is only available when the RabbitMQCompatible configuration setting is enabled.)

Note that a channel will stay in publish confirmations mode, once enabled, until it is deleted.

The NoWait parameter, if True, will cause the server to execute the request asynchronously. For asynchronous request handling, the server only sends back a response in case of an error.

An exception is thrown if the RabbitMQCompatible configuration setting is currently False, if no channel with the given ChannelName exists, or if EnableTransactionMode has been called for the specified channel previously.

EnableTransactionMode Method (AMQPClassic Module)

Enables transaction mode for a channel.

Syntax

• Swift
• Objective-C

public func enableTransactionMode(channelName: String) throws -> Void

- (void)enableTransactionMode:(NSString*)channelName;

Remarks

This method enables transaction mode for the channel with the given ChannelName.

While a channel is in transaction mode, all messages published and acknowledgements sent over it will be part of a transaction, and the server will wait to process them until the transaction is either committed or rolled back.

To commit the current transaction on a channel, call CommitTransaction; and to roll it back (and discard the messages and acknowledgements that were part of it), call RollbackTransaction.

Keep in mind that, according to the AMQP 0.9.1 specification:

• A new transaction is always started immediately after committing or rolling back the current one, which means that...
• ...a channel will stay in transaction mode, once enabled, until it is deleted.
• Transactions are only guaranteed to be atomic if all messages published and acknowledgements sent affect a single queue.
• Any messages published on a channel in transaction mode that have the Mandatory or Immediate flags set are not guaranteed to be included in the transaction.

An exception is thrown if no channel with the given ChannelName exists, or if EnablePublishConfirms has been called for the specified channel previously.

FetchMessage Method (AMQPClassic Module)

Attempts to fetch a message from a given queue.

Syntax

• Swift
• Objective-C

public func fetchMessage(channelName: String, queueName: String, noAck: Bool) throws -> Void

- (void)fetchMessage:(NSString*)channelName :(NSString*)queueName :(BOOL)noAck;

Remarks

This method attempts to fetch a message from the queue named QueueName over the channel named ChannelName.

If a message is fetched as a result of this method being called, it is immediately added to the IncomingMessage* properties, the ReceivedMessage* properties are populated, and the MessageIn event fires.

Even if no message gets fetched, the MessageIn event will still fire as long as the request was successful. The server returns the number of available messages in the specified queue in response to all successful fetch requests, and that count is exposed by MessageIn event's MessageCount parameter. Refer to the MessageIn event for more information.

QueueName must be a non-empty string consisting only of letters, digits, hyphens, underscores, periods, and colons. It must be no longer than 255 characters.

The NoAck parameter controls whether the server will expect the class to acknowledge the fetched message. Refer to MessageIn for more information about acknowledging messages.

An exception is thrown if no channel with the given ChannelName exists, or if the server returns an error because:

• No queue with the given QueueName exists.
• The specified queue exists, but is locked or otherwise unavailable to consume from (e.g., an exclusive consumer might be attached to it).

Note that in AMQP, server errors are grouped into "connection errors" and "channel errors", and both are fatal. That is, if the server returns a channel error, it will then close the channel which caused the error; and if it returns a connection error, it will then close the connection. The AMQPClassic class's Error Codes page includes AMQP's various connection and channel errors.

Receiving a Message // MessageIn event handler. amqpc1.OnMessageIn += (s, e) => { if (e.MessageCount == -1) { // The server pushed a message to us asynchronously due to a consumer we created. Console.WriteLine("The server pushed this message to us via consumer '" + e.ConsumerTag + "':"); Console.WriteLine(amqpc1.ReceivedMessage.Body); } else if (e.DeliveryTag > 0) { // We pulled a message from a queue with the FetchMessage() method. Console.WriteLine("Message successfully pulled:"); Console.WriteLine(amqpc1.ReceivedMessage.Body); Console.WriteLine(e.MessageCount + " messages are still available to pull."); } else { // We tried to pull a message, but there were none available to pull. Console.WriteLine("No messages available to pull."); } }; // Attach a consumer to "MyQueue". amqpc1.Consume("channel", "MyQueue", "consumerTag", false, true, false, false); // Or, try to fetch a message from "MyQueue". amqpc1.FetchMessage("channel", "MyQueue", true);

Interrupt Method (AMQPClassic Module)

Interrupt the current action and disconnects from the remote host.

Syntax

• Swift
• Objective-C

public func interrupt() throws -> Void

- (void)interrupt;

Remarks

This method will interrupt the current method (if applicable) and cause the class to disconnect from the remote host.

PublishMessage Method (AMQPClassic Module)

Publishes a message.

Syntax

• Swift
• Objective-C

public func publishMessage(channelName: String, exchangeName: String, routingKey: String, mandatory: Bool, immediate: Bool) throws -> Void

- (void)publishMessage:(NSString*)channelName :(NSString*)exchangeName :(NSString*)routingKey :(BOOL)mandatory :(BOOL)immediate;

Remarks

This method is used to publish the message specified by the Message* properties to the exchange named ExchangeName over the channel specified by ChannelName.

When this method is called, the message to publish is immediately added to the OutgoingMessage* properties, and the MessageOut event fires once it has been sent (or, if the specified channel is in "publish confirmations" mode, after the server has acknowledged it).

Note that all AMQP 0.9.1 servers automatically bind all queues to their default exchange (which is always a direct exchange with no name) using each queue's name as the binding's routing key. This makes it easy to send a message to a specific queue without having to declare bindings; just call PublishMessage, pass empty string for ExchangeName, and the name of the desired queue for RoutingKey.

Note that messages published over channels which are in either transaction or "publish confirmations" mode may be handled differently than they would be on a channel in normal mode. Refer to the EnableTransactionMode and EnablePublishConfirms methods for more information about what each mode entails.

The server's default exchange may be specified by passing empty string for ExchangeName. Otherwise, ExchangeName must be a non-empty string consisting only of letters, digits, hyphens, underscores, periods, and colons. It must be no longer than 255 characters.

The RoutingKey parameter specifies the message's routing key. Whether this parameter needs to be non-empty, and what format it should have if so, depends on the type of exchange it is being sent to. Some exchange types may use information included with the message, such as its MessageHeaders. Refer to BindQueue for more information about how routing keys are used, and to your server's documentation for information on what it expects.

The Mandatory parameter controls what the server should do if the message can't be routed to any queue (either because it isn't eligible for any of the queues bound to the specified exchange because of how their bindings are configured, or because no queues are bound to the exchange in the first place). If True, the server will return the message, at which point the MessageReturned event will be fired. If False, the server will drop the message.

The Immediate parameter controls what the server should do if the message can't be immediately delivered to any consumer (either because it cannot be routed to a queue, or because the queues it can be routed to have no active consumers attached to them). If True, the server will return the message, at which point the MessageReturned event will be fired. If False, the server will queue the message if possible, or drop it if not.

An exception is thrown if no channel with the given ChannelName exists, or if the server returns an error because:

• The value passed for ExchangeName fails one or more of the constraints described above.
• No exchange named ExchangeName exists.
• The message is rejected for some reason.

Note that in AMQP, server errors are grouped into "connection errors" and "channel errors", and both are fatal. That is, if the server returns a channel error, it will then close the channel which caused the error; and if it returns a connection error, it will then close the connection. The AMQPClassic class's Error Codes page includes AMQP's various connection and channel errors.

Publishing a Message amqpc1.Message.Body = "Hello, world!"; // Publish a message to the server's default (no-name) exchange, using the name of a specific queue as the routing key. amqpc1.PublishMessage("channel", "", "MyQueue", false, false); // Publish a message to the "MyExchange" exchange, using the routing key "MyRoutingKey". amqpc1.PublishMessage("channel", "MyExchange", "MyRoutingKey", false, false);

PurgeQueue Method (AMQPClassic Module)

Purges all messages from a queue.

Syntax

• Swift
• Objective-C

public func purgeQueue(channelName: String, queueName: String, noWait: Bool) throws -> Void

- (void)purgeQueue:(NSString*)channelName :(NSString*)queueName :(BOOL)noWait;

Remarks

This method purges all messages from the queue named QueueName. Messages which have been sent but are awaiting acknowledgement are not affected.

After each successful call to this method, the class populates the QueueMessageCount property with the number of messages purged from the queue. (Note that this does not occur if the NoWait parameter is set to True.)

ChannelName controls what channel the class will send the request over. While any channel can technically be used, keep in mind that the server will close it if a channel error occurs. For this reason, it is good practice to make requests such as this one using a channel that is not involved in message publishing or consumption.

QueueName must be a non-empty string consisting only of letters, digits, hyphens, underscores, periods, and colons. It must be no longer than 255 characters.

The NoWait parameter, if True, will cause the server to execute the request asynchronously. For asynchronous request handling, the server only sends back a response in case of an error.

An exception is thrown if no channel with the given ChannelName exists, or if the server returns an error because no queue named QueueName exists.

Note that in AMQP, server errors are grouped into "connection errors" and "channel errors", and both are fatal. That is, if the server returns a channel error, it will then close the channel which caused the error; and if it returns a connection error, it will then close the connection. The AMQPClassic class's Error Codes page includes AMQP's various connection and channel errors.

Recover Method (AMQPClassic Module)

Request that the server redeliver all messages on a given channel that have not been acknowledged.

Syntax

• Swift
• Objective-C

public func recover(channelName: String, requeue: Bool) throws -> Void

- (void)recover:(NSString*)channelName :(BOOL)requeue;

Remarks

This method is used to request that the server redeliver all messages that it previously sent to the class on the channel specified by ChannelName which are still awaiting acknowledgement.

A call to this method may cause the server to redeliver zero or more messages over the channel specified by ChannelName. Those messages will cause the MessageIn event to fire with its Redelivered event parameter set to True.

The Requeue parameter controls how the server should attempt to redeliver the messages awaiting acknowledgement. If set to True, the server will simple put the messages back on their original queues, and they will be delivered like any other queued messages (potentially to other consumers). If set to False, the server will redeliver the messages to the class directly.

An exception is thrown if no channel with the given ChannelName exists, or (for RabbitMQ only) if the server returns an error because Requeue was False. (RabbitMQ only supports setting Requeue to True.)

Note that in AMQP, server errors are grouped into "connection errors" and "channel errors", and both are fatal. That is, if the server returns a channel error, it will then close the channel which caused the error; and if it returns a connection error, it will then close the connection. The AMQPClassic class's Error Codes page includes AMQP's various connection and channel errors.

Reset Method (AMQPClassic Module)

Reset the component.

Syntax

• Swift
• Objective-C

public func reset() throws -> Void

- (void)reset;

Remarks

This method will reset the class's properties to their default values.

ResetMessage Method (AMQPClassic Module)

Resets the Message properties.

Syntax

• Swift
• Objective-C

public func resetMessage() throws -> Void

- (void)resetMessage;

Remarks

This method resets the Message* properties.

RollbackTransaction Method (AMQPClassic Module)

Rolls back the current transaction for a channel.

Syntax

• Swift
• Objective-C

public func rollbackTransaction(channelName: String) throws -> Void

- (void)rollbackTransaction:(NSString*)channelName;

Remarks

This method rolls back the current transaction for the channel with the given ChannelName. A new transaction is started immediately after the current one is rolled back.

Refer to EnableTransactionMode for more information about transactions.

An exception is thrown if a channel with the given ChannelName doesn't exist, or if the server returns an error because the channel does not have transaction mode enabled.

Note that in AMQP, server errors are grouped into "connection errors" and "channel errors", and both are fatal. That is, if the server returns a channel error, it will then close the channel which caused the error; and if it returns a connection error, it will then close the connection. The AMQPClassic class's Error Codes page includes AMQP's various connection and channel errors.

SetChannelAccept Method (AMQPClassic Module)

Disables or enables message acceptance for a given channel.

Syntax

• Swift
• Objective-C

public func setChannelAccept(channelName: String, accept: Bool) throws -> Void

- (void)setChannelAccept:(NSString*)channelName :(BOOL)accept;

Remarks

This method is used to disable and enable message acceptance for the channel specified by ChannelName.

A channel is always configured to accept messages when first created, allowing the server to freely deliver messages to the class for any consumers that have been created on that channel using the Consume method.

Disabling message acceptance for a channel prevents the server from automatically delivering messages to the class over it; however, it is still possible to use the FetchMessage method to synchronously attempt to retrieve a message on a channel with message acceptance disabled.

An exception is thrown if no channel with the given ChannelName exists, or (for RabbitMQ only) if the server returns an error because Accept was False. (RabbitMQ does not support disabling message acceptance.)

Note that in AMQP, server errors are grouped into "connection errors" and "channel errors", and both are fatal. That is, if the server returns a channel error, it will then close the channel which caused the error; and if it returns a connection error, it will then close the connection. The AMQPClassic class's Error Codes page includes AMQP's various connection and channel errors.

SetQoS Method (AMQPClassic Module)

Requests a specific quality of service (QoS).

Syntax

• Swift
• Objective-C

public func setQoS(channelName: String, prefetchSize: Int32, prefetchCount: Int32, global: Bool) throws -> Void

- (void)setQoS:(NSString*)channelName :(int)prefetchSize :(int)prefetchCount :(BOOL)global;

Remarks

This method is used to request a specific quality of service for a certain scope. When the PrefetchSize and/or PrefetchCount are set for a certain scope, the server will limit how many messages it sends to the class before stopping to wait for or or more of them to be acknowledged.

ChannelName is the name of the channel which is used to send the request. Depending on the server and what Global is set to, it may also be significant to the request itself (refer to the Global parameter's description, below, for more information).

PrefetchSize specifies a window size in bytes; i.e., the server will stop sending messages if the total size of all of the currently unacknowledged messages already sent, plus the size of the next message that could be sent, exceeds PrefetchSize bytes. A PrefetchSize of 0 indicates no limit. (Note that RabbitMQ does not support prefetch size limits.)

PrefetchCount specifies the number of unacknowledged messages the server will limit itself to sending. A PrefetchCount of 0 indicates no limit.

Global specifies the scope which the QoS request should apply to. It is interpreted differently based on whether the server is RabbitMQ or not. Refer to this table:

Keep the following things in mind when using QoS:

• The limits specified by a QoS request only affect messages that require acknowledgement.
• How the server chooses to handle interactions between QoS settings at different scopes is server-dependent.

An exception is thrown if no channel with the given ChannelName exists, or if the server returns an error for any reason.

Note that in AMQP, server errors are grouped into "connection errors" and "channel errors", and both are fatal. That is, if the server returns a channel error, it will then close the channel which caused the error; and if it returns a connection error, it will then close the connection. The AMQPClassic class's Error Codes page includes AMQP's various connection and channel errors.

UnbindQueue Method (AMQPClassic Module)

Removes a previously-created queue binding.

Syntax

• Swift
• Objective-C

public func unbindQueue(channelName: String, queueName: String, exchangeName: String, routingKey: String) throws -> Void

- (void)unbindQueue:(NSString*)channelName :(NSString*)queueName :(NSString*)exchangeName :(NSString*)routingKey;

Remarks

This method removes a previously-created queue binding.

ChannelName controls what channel the class will send the request over. While any channel can technically be used, keep in mind that the server will close it if a channel error occurs. For this reason, it is good practice to make requests such as this one using a channel that is not involved in message publishing or consumption.

QueueName must be a non-empty string consisting only of letters, digits, hyphens, underscores, periods, and colons. It must be no longer than 255 characters.

The server's default exchange may be specified by passing empty string for ExchangeName. Otherwise, ExchangeName must be a non-empty string consisting only of letters, digits, hyphens, underscores, periods, and colons. It must be no longer than 255 characters.

RoutingKey should be the same routing key used when originally creating the binding that is to be removed. For bindings created using arguments instead of a routing key, the Argument* properties must contain the same items used originally instead.

An exception is thrown if no channel with the given ChannelName exists, or if the server returns an error because:

• No queue with the given QueueName exists. (Does not apply to RabbitMQ.)
• No exchange with the given ExchangeName exists. (Does not apply to RabbitMQ.)

Note that in AMQP, server errors are grouped into "connection errors" and "channel errors", and both are fatal. That is, if the server returns a channel error, it will then close the channel which caused the error; and if it returns a connection error, it will then close the connection. The AMQPClassic class's Error Codes page includes AMQP's various connection and channel errors.

ChannelReadyToSend Event (AMQPClassic Module)

Fires when a channel is ready to send messages.

Syntax

• Swift
• Objective-C

func onChannelReadyToSend(channelName: String)

- (void)onChannelReadyToSend:(NSString*)channelName;

Remarks

This event fires when a channel is ready to send messages.

ChannelName is the name of the channel.

Connected Event (AMQPClassic Module)

This event is fired immediately after a connection completes (or fails).

Syntax

• Swift
• Objective-C

func onConnected(statusCode: Int32, description: String)

- (void)onConnected:(int)statusCode :(NSString*)description;

Remarks

If the connection is made normally, StatusCode is 0 and Description is "OK".

If the connection fails, StatusCode has the error code returned by the Transmission Control Protocol (TCP)/IP stack. Description contains a description of this code. The value of StatusCode is equal to the value of the error.

Please refer to the Error Codes section for more information.

ConnectionStatus Event (AMQPClassic Module)

This event is fired to indicate changes in the connection state.

Syntax

• Swift
• Objective-C

func onConnectionStatus(connectionEvent: String, statusCode: Int32, description: String)

- (void)onConnectionStatus:(NSString*)connectionEvent :(int)statusCode :(NSString*)description;

Remarks

The ConnectionStatus event is fired when the connection state changes: for example, completion of a firewall or proxy connection or completion of a security handshake.

The ConnectionEvent parameter indicates the type of connection event. Values may include the following:

Disconnected Event (AMQPClassic Module)

This event is fired when a connection is closed.

Syntax

• Swift
• Objective-C

func onDisconnected(statusCode: Int32, description: String)

- (void)onDisconnected:(int)statusCode :(NSString*)description;

Remarks

If the connection is broken normally, StatusCode is 0 and Description is "OK".

If the connection is broken for any other reason, StatusCode has the error code returned by the Transmission Control Protocol (TCP/IP) subsystem. Description contains a description of this code. The value of StatusCode is equal to the value of the TCP/IP error.

Please refer to the Error Codes section for more information.

Error Event (AMQPClassic Module)

Information about errors during data delivery.

Syntax

• Swift
• Objective-C

func onError(errorCode: Int32, description: String)

- (void)onError:(int)errorCode :(NSString*)description;

Remarks

The Error event is fired in case of exceptional conditions during message processing. Normally the class .

The ErrorCode parameter contains an error code, and the Description parameter contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the Error Codes section.

Log Event (AMQPClassic Module)

Fires once for each log message.

Syntax

• Swift
• Objective-C

func onLog(logLevel: Int32, message: String, logType: String)

- (void)onLog:(int)logLevel :(NSString*)message :(NSString*)logType;

Remarks

This event fires once for each log message generated by the class. The verbosity is controlled by the LogLevel setting.

LogLevel indicates the level of the Message. Possible values are:

LogType identifies the type of log entry. Possible values are:

• Info: General information about the class.
• Frame: Frame status messages.

MessageIn Event (AMQPClassic Module)

Fires when a message is received; as well as when an attempt is made to fetch a message from a currently empty queue.

Syntax

• Swift
• Objective-C

func onMessageIn(channelName: String, consumerTag: String, deliveryTag: Int64, redelivered: Bool, exchangeName: String, routingKey: String, messageCount: Int32, accept: inout Int32)

- (void)onMessageIn:(NSString*)channelName :(NSString*)consumerTag :(long long)deliveryTag :(BOOL)redelivered :(NSString*)exchangeName :(NSString*)routingKey :(int)messageCount :(int*)accept;

Remarks

This event fires anytime a message is received. There are two possible ways for the class to receive a message:

• Messages can be asynchronously pushed to the class from the server. At any point in time, the server may push a message to the class from a queue that the Consume method has been used to attach a consumer to.
• Messages can be synchronously pulled from the server by the class. The FetchMessage method is used to attempt to pull (or "fetch") messages from a specific queue.

This event also fires anytime FetchMessage is called against a queue that currently has no messages available to pull. This is a special case, and results in only the ChannelName and MessageCount event parameters being populated.

Other than that special case, and any exceptions noted below, this event's parameters are populated the same way regardless of the manner in which messages are received.

ChannelName always reflects the name of the associated channel.

ConsumerTag reflects the consumer tag associated with the consumer that caused the server to push the message to the class. (ConsumerTag is always empty for messages pulled from the server by FetchMessage since no consumers are involved.)

DeliveryTag reflects the server-assigned, channel-specific delivery tag number for the incoming message.

Redelivered reflects whether the server is redelivering a message that is has delivered previously.

ExchangeName reflects the name of the exchange to which the incoming message was originally published. (If the message was originally published to the server's default exchange, whose name is always the empty string, ExchangeName will also be empty.)

RoutingKey reflects the routing key that the message was originally published with.

MessageCount is always -1 when this event fires due to a message being pushed to the class by the server. When this event fires as a result of FetchMessage being called, MessageCount reflects the number of messages still available in the queue the class tried to pull a message from (even if there were no messages available to pull).

The Accept parameter can be set to control how the class responds to the incoming message, if it needs to be acknowledged (if the message doesn't need to be acknowledged, the value set to the Accept parameter is ignored). Valid values are:

• 0 - default: Accept the message; send a positive acknowledgement.
• 1: Silently accept the message; don't send any acknowledgement.
• 2: Accept the message; send a cumulative positive acknowledgement coving this, and all previously unacknowledged, messages.
• 3: Reject the message; send a negative acknowledgement for it, and instruct the server not to return it to the queue.
• 4: Reject the message; send a negative acknowledgement for it, and instruct the server to return it to the queue.

If the value provided for the Accept parameter isn't one of those described above, the default (0) will be used instead.

Receiving a Message // MessageIn event handler. amqpc1.OnMessageIn += (s, e) => { if (e.MessageCount == -1) { // The server pushed a message to us asynchronously due to a consumer we created. Console.WriteLine("The server pushed this message to us via consumer '" + e.ConsumerTag + "':"); Console.WriteLine(amqpc1.ReceivedMessage.Body); } else if (e.DeliveryTag > 0) { // We pulled a message from a queue with the FetchMessage() method. Console.WriteLine("Message successfully pulled:"); Console.WriteLine(amqpc1.ReceivedMessage.Body); Console.WriteLine(e.MessageCount + " messages are still available to pull."); } else { // We tried to pull a message, but there were none available to pull. Console.WriteLine("No messages available to pull."); } }; // Attach a consumer to "MyQueue". amqpc1.Consume("channel", "MyQueue", "consumerTag", false, true, false, false); // Or, try to fetch a message from "MyQueue". amqpc1.FetchMessage("channel", "MyQueue", true);

MessageOut Event (AMQPClassic Module)

Fires when a message is published.

Syntax

• Swift
• Objective-C

func onMessageOut(channelName: String, exchangeName: String, routingKey: String, messageId: String, deliveryTag: Int64, accepted: Bool)

- (void)onMessageOut:(NSString*)channelName :(NSString*)exchangeName :(NSString*)routingKey :(NSString*)messageId :(long long)deliveryTag :(BOOL)accepted;

Remarks

This event fires anytime a message is published; or after an outgoing message has been acknowledged by the server, if the channel it was published on is in "publish confirmations" mode.

ChannelName reflects the name of the channel the message was published on.

ExchangeName reflects the name of the exchange the message was published to. (If the message was published to the server's default exchange, whose name is always the empty string, ExchangeName will also be empty.)

RoutingKey reflects the routing key that the message was published with.

MessageId reflects the message's unique Id, if one was set.

DeliveryTag reflects the channel-specific delivery tag number for the message. (Note that this is only populated for messages published on a channel in "publish confirmations" mode; otherwise it will be set to -1.)

Accepted indicates whether the server published back a positive True or negative False acknowledgement for the outgoing message. Note that this is only valid for messages published on a channel in "publish confirmations" mode; Accepted will always be True messages published on a channel in normal or transaction mode.

Refer to EnablePublishConfirms for more information about channels in "publish confirmations" mode.

MessageReturned Event (AMQPClassic Module)

Fires if a previously published message is returned by the server due to it being undeliverable.

Syntax

• Swift
• Objective-C

func onMessageReturned(channelName: String, replyCode: Int32, replyText: String, exchangeName: String, routingKey: String)

- (void)onMessageReturned:(NSString*)channelName :(int)replyCode :(NSString*)replyText :(NSString*)exchangeName :(NSString*)routingKey;

Remarks

This event fires if the server returns a previously published message because it could not deliver it. Typically, messages are only undeliverable in one of the following situations:

• The message was originally published with the Mandatory option enabled, but there were no queues it could be routed to.
• The message was originally published with the Immediate option enabled, but there were no consumers it could be delivered to immediately on any queue it was routed to (or there were no queues it could be routed to).

The ReceivedMessage* properties will be populated with the returned message.

ChannelName reflects the name of the channel the message was originally published on.

ReplyCode will be an AMQP error code that indicates the reason why the message was returned. (Tip: The AMQPClassic class's Error Codes page includes the various AMQP error codes.)

ReplyText will be a message with further details about why the message was returned.

ExchangeName reflects the name of the exchange to which the message was originally published. (If the message was originally published to the server's default exchange, whose name is always the empty string, ExchangeName will also be empty.)

RoutingKey reflects the routing key that the message was originally published with.

SSLServerAuthentication Event (AMQPClassic Module)

Fired after the server presents its certificate to the client.

Syntax

• Swift
• Objective-C

func onSSLServerAuthentication(certEncoded: Data, certSubject: String, certIssuer: String, status: String, accept: inout Bool)

- (void)onSSLServerAuthentication:(NSData*)certEncoded :(NSString*)certSubject :(NSString*)certIssuer :(NSString*)status :(int*)accept;

Remarks

During this event, the client can decide whether or not to continue with the connection process. The Accept parameter is a recommendation on whether to continue or close the connection. This is just a suggestion: application software must use its own logic to determine whether or not to continue.

When Accept is False, Status shows why the verification failed (otherwise, Status contains the string OK). If it is decided to continue, you can override and accept the certificate by setting the Accept parameter to True.

SSLStatus Event (AMQPClassic Module)

Shows the progress of the secure connection.

Syntax

• Swift
• Objective-C

func onSSLStatus(message: String)

- (void)onSSLStatus:(NSString*)message;

Remarks

The event is fired for informational and logging purposes only. This event tracks the progress of the connection.

AMQPCChannel Type

Represents an AMQP 0.9.1 channel.

Remarks

This type represents an AMQP 0.9.1 channel.

Fields

Constructors

public init()

AMQPCMessage Type

Represents an AMQP 0.9.1 message.

Remarks

This type represents an AMQP 0.9.1 message.

Fields

[
  { "name": "Header1", "type": "long", "value": 12345678901234 },
  { "name": "Header2", "type": "boolean", "value": "false" },
  { "name": "Header3", "type": "string", "value": "This is a test." }
]

[
  { "type": "int", "value": 23 },
  { "type": "int", "value": -52 },
  { "type": "int", "value": 153325 }
]

Constructors

public init()

AMQPCTableField Type

Represents an AMQP 0.9.1 table field.

Remarks

This type represents an AMQP 0.9.1 table field.

Fields

[
  { "type": "int", "value": 23 },
  { "type": "int", "value": -52 },
  { "type": "int", "value": 153325 }
]

{
  { "name": "Test1", "type": "long", "value": 12345678901234 },
  { "name": "Test2", "type": "boolean", "value": "false" },
  { "name": "Test3", "type": "string", "value": "This is a test." }
}

Constructors

public init()

Firewall Type

This is the firewall the component will connect through.

Remarks

When connecting through a firewall, this type is used to specify different properties of the firewall, such as the firewall and the .

Fields

Constructors

public init()

Config Settings (AMQPClassic Module)

AMQPClassic Config Settings

TCPClient Config Settings

SSL Config Settings

-----BEGIN CERTIFICATE-----
MIIEKzCCAxOgAwIBAgIRANTET4LIkxdH6P+CFIiHvTowDQYJKoZIhvcNAQELBQAw
...
eWHV5OW1K53o/atv59sOiW5K3crjFhsBOd5Q+cJJnU+SWinPKtANXMht+EDvYY2w
F0I1XhM+pKj7FjDr+XNj
-----END CERTIFICATE-----
\r \n
-----BEGIN CERTIFICATE-----
MIIEFjCCAv6gAwIBAgIQetu1SMxpnENAnnOz1P+PtTANBgkqhkiG9w0BAQUFADBp
..
d8q23djXZbVYiIfE9ebr4g3152BlVCHZ2GyPdjhIuLeH21VbT/dyEHHA
-----END CERTIFICATE-----

-----BEGIN CERTIFICATE-----
MIIEKzCCAxOgAwIBAgIRANTET4LIkxdH6P+CFIiHvTowDQYJKoZIhvcNAQELBQAw
...
eWHV5OW1K53o/atv59sOiW5K3crjFhsBOd5Q+cJJnU+SWinPKtANXMht+EDvYY2w
F0I1XhM+pKj7FjDr+XNj
-----END CERTIFICATE-----
\r \n
-----BEGIN CERTIFICATE-----
MIIEFjCCAv6gAwIBAgIQetu1SMxpnENAnnOz1P+PtTANBgkqhkiG9w0BAQUFADBp
..
d8q23djXZbVYiIfE9ebr4g3152BlVCHZ2GyPdjhIuLeH21VbT/dyEHHA
-----END CERTIFICATE-----

Socket Config Settings

Base Config Settings

Trappable Errors (AMQPClassic Module)

AMQPClassic Errors

TCPClient Errors

SSL Errors

TCP/IP Errors