By default the INFO logging is printing in the console how to disable it ?
How to browse the message in the solace mq ? do we have any tool for this ?
Thanks
Logging configuration is dependant on the platform of the application. The Solace JMS and JCSMP API logging uses Jakarta Commons Logging to support different logging frameworks, such as log4j or java.util.logging. The other answer by user Farside shows how to change the logging level if you are using log4j with the Solace JMS API.
You can find more information about logging in your specific platform in the Solace Messaging API guides or in the integration guides provided on the Solace Systems Developer Portal.
To see information about the spooled messages on a queue in Solace, you can use the CLI or SolAdmin.
In the CLI, the command is:
show queue <queueName> message-vpn <vpnName> messages detail
This will allow you to see information on each message in the queue, such as the date spooled, message size, sequence number, etc.
In SolAdmin, you can view the equivalent information by navigating to the 'Endpoints' tab and selecting the 'Durable Queues' view. From this view, you can double click on the queue in the list and select the 'Messages' tab. You can double click on a specific message to view more information.
To view the full contents of a spooled message, you can create a Queue Browser. This is a client that can look at messages spooled on a queue in order of oldest to newest without consuming them. A full description of a Queue Browser is provided in Chapter 9, "Working with Guaranteed Messages" of the Solace Messaging Platform Feature Guide. Details about creating a Queue Browser are provided in the Solace Messaging APIs Developer Guide.
These documents are available on the Solace Systems developer portal at this link:
http://dev.solacesystems.com/docs/product-documentation/
Solace JMS API logging is very similar to configuring any other Spring
Framework logging. They say, to define the level of logging use:
log4j.category.com.solacesystems.jms=DEBUG
log4j.category.com.solacesystems.jcsmp=DEBUG
More information can be found here: section "6.1 How to enable Solace JMS API logging". By default info logs will be written to the console.
Related
When my users reply via SMS with opt-in or opt-out messages, Twilio's Opt-Out "engine" works as expected, but then the message is passed on to my Studio flow. I'd prefer to have these opt-* messages stop at the opt engine, and not have to add a bunch of extra logic to my flow to handle/discard them.
Is there an option for this? I don't see one under the messaging service's Opt-Out Management.
According to Twilio's documentation, I can set a custom help message at a Message Service level via their console -- can this be done via their API?
Link to documentation: https://www.twilio.com/docs/sms/services/advanced-opt-out#configuring-advanced-opt-out-keywords
Unfortunately, it cannot be done via an API today, it must be done via the Console.
Getting Started with Advanced Opt-Out for Messaging Services
Customize opt-in and opt-out flows with Advanced Opt-Out
Customizing Users’ Opt-in and Opt-out Experience with Advanced Opt-Out
I am experimenting with Twilio Flex. I have setup project from Flex template to get started and it worked fine.
When I go to Flex Phone Number configuration I can see incoming messages are routed to Flex Proxy Service.
I don't understand quite well how Flex Proxy Service is integrated with Studio Messaging Flow. I can see my SMS messages in Messaging Flow log's but I do not know where exactly Proxy Service is configured to route messages to this flow
When I tried to change Flex Phone Number configuration so that when new message comes in Studio Flow (Messaging Flow) is called directly it stopped working and I could not see my messages popping up in Flex agent dashboard any more.
Obviously proxy service is doing something else in the background (other than routing to respective studio flow). Any suggestions here?
Twilio Proxy is used to orchestrate messages from multiple channels to the Flex agent UI. In the background it bridges messages from a messaging channel like SMS to a chat session. It is not necessary to configure the Proxy service manually, Flex automatically does it for you. You can configure a phone number for Flex on the Flex Management Console. On the same page you can link a messaging channel to a Studio flow. This flow is triggered whenever a new conversation is created.
You cannot configure a phone number directly with a Studio Flow to use it with Flex. The Flow for a channel is always configured (selected from the drop-down) on the Flex Management Console.
How can I add a configuration page for my slack app?
example: asana has an add configuration button which leads to a page which we can use to then connect the slack user account with asana account
Several Slack apps (e.g. Twitter, Google Calendar) provide a configuration page after installation into Slack. However this feature seams to be available only to commercial partners of Slack, but not as a standard feature for every app developers.
Developers need to implement it by themselves with an external app / script that is linked the Slack app and store the configurations in their own database.
See also this answer for a full explanation on how this works.
Looking on the official Slack Plattform Roadmap for Developers this feature might be implemented in the future under "Install apps from within Slack".
Update:
You can now use Dialogs to create something similar to configuration pages. It allows you to open a custom modal window with up to 5 inputs (text or drop-downs). Its still not the same as having a full configuration page like the internal Slack apps have, but its a huge step forward and might be sufficient for many cases.
As Solace does not support deleting and disconnecting client via SEMP over a message bus, as mentioned here, may I know how do I do that programmatically? I need to manage clients, especially client connection from my application. Can I run trigger CLI scripts from my program to achieve that?
Thank you.
Disconnecting a client is an administrative action that can only be executed by management users over the management interface. Client applications are not allowed to execute this action.
To disconnect a client, you can send a SEMP command through the management interface using a management user. (Not via SEMP over Message Bus.)