Hi, The purpose of this email is the figure out a way to do $subject. Suppose a carbon server wants to send a JMS message to through MB without using a user name( which is recognized by MB). this is obviously not possible since to create a connection one needs have credentials ( i.g username + password , access key).
Now, the scenario I have in mind is where MB and another (probably a carbon) server(s) are just part of a bigger system. various parts of the system needs to communicate with each other using JMS. one approach would be to have a special/magic user to connect to MB and send message. BUT this is not the ideal approach given that its has the meaning of a user generated the massage NOT the System. ( and a magic user need to be created in every tenant). Now let me relate the problem to a example: In Appfactory we use MB to exchange messages. some of these messages are originated from appfactory users. examples: 1. User creates an application. 2. User starts a build. However there are some events that are not particularly associated with an user. Examples: 1) an web application is deployed (or deployment failed) in application server (App server is spawned by Stratos and deployment is done via dep-sync). 2) a build completes in jenkins/build server and appfactory send a notification about the build status. Note that in above scenarios, event is generated by the system ( a.ka. Appfactoy) not the user. which means we don't know a user to associate OR its wrong to associate the user with the event ( the user might get angry if the Appfactory used his/her name to send a massage !!) So in essence what we are looking for a way to create a jms connection to MB without involving a user in userstore. I know with the current capabilities ( or how the JMS is works) this may be not possible. So what do you guys think? -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
