Communicating Message Broker and Websphere Application Server - websphere-portal

I have a portal application deployed on WebSphere Portal server and message flows deployed in message broker execution group. The portal application does some kind of database CRUD operation. Based on the changes made through portal, I want to update my cache data of Message Broker. Since there could be several broker execution group, so I thought of creating a pub-sub model. Every time the portal changes some values in the database, it publishes that message to the topic which broker application will listen to and take appropriate action.
My problem is how to make both these servers communicate to each other. Any pointer would be highly appreciated.
Thanks in advance.

JMS would probably be my choice here as it already supports the pub/sub semantics and is supported by both products.

You can Use DatabaseInput Node in You Message Flows, this Node can listens on Database,Table,or Column if you want for more information go to this link and read about the Node:
DatabaseInput Node Documentation

Related

Logic App to Queue - SSL connection could not be established

We have a Logic App trying to access the Storage Account Queue, secured by a private endpoint. Both resources are in the same SNET. We have configured our Managed Identities correctly and given Storage Queue Data Contributor access to the storage account. When trying to put a message in the queue, we are getting the error:
SSL connection could not be established, see inner exception.
We checked this Microsoft documentation but are not aware of what certificate they are talking about. Please check the error screenshot below.
It turns out that we need to whitelist the IP addresses in our company's firewall. However, there is a catch. According to this community post, we required our logic app and storage accounts in different regions. Since the move was not possible, we changed all our connectors to built-in connectors instead of Azure public connectors. Changing to the built-in connectors came with its own challenges, but we were able to achieve our purpose.

Salesforce Inbound Sms integration

I am trying to trigger an apex class on every inbound text message received for messaging session in omni channel tab. But I am not able to find any object that can be used to attach a trigger on it. Have searched online as well, but in most of the guides they use third party services like twilio, Mercury etc. Can someone help me to implement this without any third-party service?
You should try agent work or pending service routing objects I think

Web Service in SQL server (Alternative solution)

HI All Currently we have a web service in the Our Platform, that is called from the database.
When something changes inside the database, it should by itself initiate and inform an External Application.
The application should NOT be polling the database and enquiring of the change.
The current solution which we have is a HTTP call but this has it's own overhead. Also, it does not guarantee 100% message delivery.
So is there an alternate solution.
Can the database write to a Queue?

SignalR - NLB Server Change and Suggested Way to Scale-Out

I have silverlight web app. This web app run in 4 servers with a NLB in front of them. I need to use SignalR in my web app.
Lets think about this scenario.
Client#1 is connected to Server#1 and everything is okay. They are communicating each other through a hub perfectly. Then suddenly NLB assigned Client#1 to Server#2.
Now, what will happen to Connection and Hub? How they will communicate?
How is the connection between Client#1 and Server#1 set?
PS: I don't know much about NLB. Maybe it is stupid question, but I could not find a good explanation.
My second question is, which way among scaling out (Azure, SQL, Redis) is the best for .NET Silverlight app with possibly not many clients (Less than 10K)?
Not: I use MS SQL, SQL Server highly in my app.
After I watch this very informative video, I found answers to my questions.
Basically, the new connection will be established automatically when the client is assigned to other server node. The old connection is lost, however in any case, all the clients can be notified if you are using Back-plane. Thus, this is not a problem.
The hub object is also not a problem since it is transient object, i.e, in every new single operation a new hub object is created. Thus, this is also not a problem. There is no persistent hub object between server and client. Even if there is one server and one client, the hub will be destroyed and created in every operation.
The only problem is that if you are using groups, then the group information is lost for the client when it connects to the other server. The server does not maintain lists of groups or group memberships. So in that case you need to use a database and you can update manually from your db. When the new connection is establishes between client and new server, you can search this client in the db, and if you find a group information of that client, then you can manually re-register to that group again.
For choosing the Backplane, there is no fastest or best way. Nobody can say this way is faster or better among Azure Service Bus, Redis, SQL. It really depends on your application. If you are already using MS Azure Services, then pick Azure implementation for your web app. If you are using Redis in you app, go woth Redis. Otherwise you can select SQL. As I said, all of them are more or less same. Pick one that is most suitable for your web app.
These are all what get from video and the official site of the SignalR page.
This site is one of the best SignalR tutorial and api guide site. It is highly recommended that go through all sections.

Web application authentication design pattern

I'm working on a web application and I'm having problem accessing the database on server side because there is no user for the DB proxy to map. In other word, I have a method which will start as soon as the application comes online and will call itself every 5 seconds to check for new messages. If it receives a specified message, it then goes to the database and finds whatever it needs. However, accessing database on server side wouldn't be possible because there is no user for the DB proxy to map. So what is a good design pattern for this type of application? Should I need an application account for these type of automation process?
Btw, I'm using Weblogic JPA 2.1 for database stuff.
Thanks in advance.
First of all, what exactly do you mean by "no user for the DB proxy to map"?
I assume, you meant that you don't have a user known by a session who connects to the database?
If yes, you usually wouldn't do that anyway and instead nearly always have a database user for your application. Then, no matter a user triggers a database call by an action or the backend triggers it by some scheduling, it will always be the same user who does it. In your Java EE application, you'd have a datasource containing this user in its configuration and all your application parts use the related entity manager when doing persistent actions or queries.

Resources