Attached the howto.
Any comments and changes appreciated.

For orionsupport team (you can publish it)

Luciano




-----Messaggio originale-----
Da: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED]]
Inviato: venerdì 19 gennaio 2001 1.42
A: Orion-Interest
Oggetto: RE: JMS


There is an article on Orion Support about integrating OpenJMS with Orion,
this may help you - http://www.orionsupport.com/articles/openjms.html

If you do succeed, but need changes, we'd love to hear what you needed to do
to get SwiftMQ working with Orion - I'll alter the article on the site.

Cheers,
Mike

> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Montebove
> Luciano
> Sent: Friday, January 19, 2001 3:31 AM
> To: Orion-Interest
> Cc: [EMAIL PROTECTED]
> Subject: R: JMS
>
>
> I have just started a study for integrating swiftMQ and sonicMQ
> with Orion.
> Up to now I tried only to send messages from servlet/JSP but both the
> products provide some form of bridging with other JMS servers, so this way
> could be possible to use Message Driven EJB.
> More information in a few weeks.
>
> Luciano
>
>
> -----Messaggio originale-----
> Da: Mike Courtney [mailto:[EMAIL PROTECTED]]
> Inviato: mercoledì 17 gennaio 2001 18.27
> A: Orion-Interest
> Oggetto: RE: JMS
>
>
> Speaking of which, has anyone out there used any of these
> messaging systems
> with Orion?
>
> I am interested in using a solid JMS implementation with a
> backing database
> for distributed replication/high availability. Apparently Orion only
> provides file based persistence for JMS queues.
>
> Any suggestions/thoughts?
>
> thanks,
> Mike Courtney
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Joseph B.
> Ottinger
> Sent: Wednesday, January 17, 2001 5:52 AM
> To: Orion-Interest
> Subject: Re: JMS
>
>
> On Wed, 17 Jan 2001 [EMAIL PROTECTED] wrote:
> > Is that true that the only message queue servers in existence
> > which support JMS are IBM's MQ Series and Forte's
> > Java Message Queue? Any other vendors?
>
> Um, no. Far from it.
>
> Some JMS systems, including the ones you mentioned:
>
> MQSeries (http://www-4.ibm.com/software/ts/mqseries/)
> SonicMQ (http://www.progress.com/sonicmq/)
> FioranoMQ (http://www.fiorano.com/)
> BEA's message queue (http://www.bea.com/)
> OpenJMS (http://www.openjms.org/)
> SwiftMQ (http://www.swiftmq.com/)
> Sun's JMS (http://http://www.sun.com/forte/jmq/index.html)
> Softwired iBus (http://www.softwired-inc.com/)
>
> I'm sure there are more.
>
> -----------------------------------------------------------
> Joseph B. Ottinger                           [EMAIL PROTECTED]
> http://epesh.com/                             IT Consultant
>
>
>
>
>


Title: 1)Download and Install SwiftMQ 1

1)Download and Install SwiftMQ 1.2 and the JMS Bridge Extension Swiftlet 1.0

2) modify the launch script for SwiftMQ to include orion.jar in the classpath

3)include these lines in smqr?.properties:

swiftlet.xt$bridge.servers.names=orion1

swiftlet.xt$bridge.servers.orion1.configfile=../../conf/bridge_orion.properties

swiftlet.xt$bridge.servers.orion1.objectfactory=com.swiftmq.extension.bridge.JNDIObjectFactory

swiftlet.xt$bridge.servers.orion1.retryinterval=60000

##to create a bridge from an orion topic to a swift topic (see swift docs for queues)#######

swiftlet.xt$bridge.servers.orion1.bridgings.names=provaTopic_Remote_to_loca

swiftlet.xt$bridge.servers.orion1.bridgings.provaTopic_Remote_to_loca.direction=remote_to_local

swiftlet.xt$bridge.servers.orion1.bridgings.provaTopic_Remote_to_loca.localname=testtopic

swiftlet.xt$bridge.servers.orion1.bridgings.provaTopic_Remote_to_loca.localtype=topic

swiftlet.xt$bridge.servers.orion1.bridgings.provaTopic_Remote_to_loca.remotefactoryname=jms/TopicConnectionFactory

swiftlet.xt$bridge.servers.orion1.bridgings.provaTopic_Remote_to_loca.remotename=jms/demoOutTopic

swiftlet.xt$bridge.servers.orion1.bridgings.provaTopic_Remote_to_loca.remotetype=topic

swiftlet.xt$bridge.servers.orion1.bridgings.provaTopic_Remote_to_loca.transferpersistence=persistent

##############################################################################

##to create a bridge from a swift topic to an orion topic (see swift docs for queues)#######

swiftlet.xt$bridge.servers.orion1.bridgings.names=provaLocToRemBean

swiftlet.xt$bridge.servers.orion1.bridgings.provaLocToRemBean.direction=local_to_remote

swiftlet.xt$bridge.servers.orion1.bridgings.provaLocToRemBean.localname=testtopic

swiftlet.xt$bridge.servers.orion1.bridgings.provaLocToRemBean.localtype=topic

swiftlet.xt$bridge.servers.orion1.bridgings.provaLocToRemBean.remotefactoryname=jms/TopicConnectionFactory

swiftlet.xt$bridge.servers.orion1.bridgings.provaLocToRemBean.remotename=jms/demoTopic

swiftlet.xt$bridge.servers.orion1.bridgings.provaLocToRemBean.remotetype=topic

swiftlet.xt$bridge.servers.orion1.bridgings.provaLocToRemBean.transferpersistence=persistent

##############################################################################

 

swiftlet.xt$bridge.class=com.swiftmq.extension.bridge.BridgeSwiftlet

swiftlet.names=xt$bridge

4)create a bridge_orion.properties files containing these lines:

java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory

java.naming.provider.url=ormi://localhost/

java.naming.security.principal=admin

java.naming.security.credentials=123

5)define your queues/topics in jms.xml

6)start orion and swiftmq and try any JMS sample you want from orion and swiftmq

7)if you don't need the bridge (If you simply want to send messages from a servlet/JSP) you have to follow only step 1, copy smqclient.jar in orion/lib and create the initial context this way:

Hashtable env = new Hashtable();

env.put(Context.INITIAL_CONTEXT_FACTORY,"com.swiftmq.jndi.InitialContextFactoryImpl");

env.put(Context.PROVIDER_URL,"smqp://localhost:4001/timeout=10000");

context = new InitialContext(env);

8)Problems:

a) I don't know how to attach a message driven bean to a specific topic/queue.

b) A bug in 1.4.5 (#260 in bugzilla) prevents message driven beans to work.

 

 

 

 

Reply via email to