Open topic with navigation

# Channel Details Panel

The Channel details panel presents the details of an individual channel definition. In edit mode, you can modify the definition.

## Push Settings

See Configuring Push Notifications.

Parameter | Description
--- | ---
APNS Certificate | Enter the PEM-encoded private certificate data.
APNS Certificate Password | Enter the password for the private certificate.
Use APNS Sandbox | When enabled, use Apple's development sandbox network. When disabled, use Apple's production network.
Firebase Cloud API Key | Enter the Firebase Cloud Messaging (FCM) API key.

## Authorization

If security is enabled for the cluster, it authenticates and authorizes eFTL clients. Clients can use channel functionality based on their authorization groups. See also Client Authentication and Authorization.

These parameters are available if you enable Authentication in the cluster settings; see eFTL Clusters Grid. Only use these parameters when using the legacy method for configuring authorization. For details on the legacy method, see Client Authentication and Authorization.

Parameter | Description
--- | ---
Publish Group | Only eFTL clients in this authorization group can publish messages on this channel.
Subscribe Group | Only eFTL clients in this authorization group can subscribe on this channel.

## Parameters Specific to FTL Messaging Infrastructure

Parameter | Description
--- | ---
Default Durable Template | Optional. When eFTL clients create dynamic durable subscriptions on the channel without specifying a durable type, they use this template. It is a good practice to avoid confusion by configuring a standard durable template as the default. You can associate at most one default dynamic durable template with each channel. The menu offers the templates defined in the persistence store associated with the channel.
Shared Durable Template | Optional. When eFTL clients create shared durable subscriptions on the channel, they use this template. You can associate at most one shared durable template with each channel. The menu offers the templates defined in the persistence store associated with the channel.
Last-Value Durable Template | Optional. When eFTL clients create last-value durable subscriptions on the channel, they use this template. You can associate at most one last-value durable template with each channel. The menu offers the templates defined in the persistence store associated with the channel.
Map Template | Optional. When eFTL clients create map durable subscriptions on the channel, they use this template. You can associate at most one map template with each channel. The menu offers the templates defined in the persistence store associated with the channel.
Subscriber Name Mapping for Static Durables | Optional. Note: Subscriber name mapping is an advanced topic. If you configure a persistence store for a channel, then you can configure a mapping from durable names (in subscribe calls) to static durable names (defined in the store). For the semantics of durable subscriptions, see "Persistence" inDevelopment.

## Parameters Specific to EMS Messaging Infrastructure

Parameter | Description
--- | ---
User Name Password | Required for EMS infrastructure. The eFTL service authenticates itself to the EMS server using this username and password.

## Heartbeats and Timeouts

These parameters have factory default values, which you can override.

Parameter | Description
--- | ---
Heartbeat : eFTL Service to FTL Server | The TIBCO eFTL service sends heartbeats at this interval (in seconds) to clients on the channel. Clients respond to heartbeats, indicating that they are still connected. Zero is a special value, which prevents the service from sending heartbeats. If you set this parameter to zero, you must also set Client Timeout to zero.
Client Timeout | The TIBCO eFTL service disconnects a client after this interval (in seconds) since the last communication from the client, including heartbeat responses and message publishing calls. Zero is a special value, instructing the service to not disconnect clients.
Client Reconnect Timeout | When a client disconnects from the eFTL service, the service buffers outbound messages so that the client can receive them when it reconnects. The service buffers message for this interval. After this interval elapses, the service deletes outbound messages it was buffering for the client.

## Limits

These parameters have factory default values, which you can override.

Parameter | Description
--- | ---
Maximum Pending Acknowledgments | When the backlog of unacknowledged messages outbound to an eFTL client on the channel exceeds this limit, the service stops transferring messages to the client. When the service receives acknowledgments, it resumes sending messages to the client. For eFTL 6.8.0 and later, if an eFTL client specifies a value for `max_pending_acks` that is greater than the value configured for the channel, the client's value is rounded down to the channel's value.
Maximum Message Size | You can limit the size (in bytes) of inbound messages. Publish calls in eFTL clients fail when a message exceeds this limit.
Maximum Queue Size | You can limit the growth of eFTL client message queues to conserve memory in the eFTL service. For background information and complete details, see the following section on Maximum Queue Size.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO FTL® - Enterprise Edition

Copyright © 2009-2024. Cloud Software Group, Inc. All Rights Reserved.