Sendin messages to a jmstopics

Hi,
We want to send messages to a WAS topic in the same was as we send to a queue.
To that purpose a communication channel based on JMS adapter type is defined.
Adapter type: JMS
Receiver
Transport Protocol: Acces JMS Provider with JNDI
Message Protocol: JMS 1. x
Adapter Engine : Integration Server.
When we continue we face the firs challenge. ( We can only enter information related to queues,
Why are there no option for entering topics ? )
I enter the topic information :
JNDI Lookup Name of QueueConnectionFactory : jmsfactory/default/TopicConnectionFactory
JNDI Lookup Name of JMS Queue: jmstopics/default/DK.POST.PMA.MBTK.ENCRYPTIONKEY
Name of JNDI Initial Context Factory : com.sap.engine.services.jndi.InitialContextFactoryImpl
But the communication channel does not work. Anybody who has an idea.
Can it be that transferring message to at topic is not supported by XI 3.0.?
Kind Regards
Ugur Er

Hi,
JMS Adapters in XI do not support topics.
From the SAP note : 856346
Question: Does the JMS Adapter support JMS topics (publish&subscribe)?
Answer: No. The JMS Adapter works with JMS queues because 100% Exactly Once (In Order) service quality can only be guaranteed with JMS queues. See also: "Java Message Service", Monson-Haefel/Chappel, O'Reilly Publishers, 0-596-00065-5 2001, page 102 "... In this case, the once-and-only-once is in doubt".
Regards
Bhavesh

Similar Messages

Cant get it to email photos anymore

it says sending message but never shows up. It used to show up in my email.
I have tried it using 3 different contacts.
What I did was setup a contact
put in a phone number and an email
goto messages select new
select the one i want to send a message
select addselect add photo
select photo, the picture shows in the list.
select the photo it shows in the message
then type something
then click send.
It will say sending message, but message never appears.

I got it to send only ny manually typing in my email address.
I am sending to email accounts
I think It always wants to send to a phone MMS picture message type thing.
I set up contacts with real house phone and real emails, Never arrives.
I set up contact with fake phone number and real email, never arrives.
For only one week I managed to send email photos to my inlaws email, He does not have a wireless phone just a house phone and email account. So I thought that worked pretty good but a few weeks later and it stopped sending him the photos.
Meaning one week I sent hime 20 pictures, a few week later using the same exact contact I used before in the phone, he did not get them. It always says sending, but where do they go??
It always seems to work if I manually type in an email adress. I dont want to do that, I want to use my contact list. It is not easy to keep typing in email adresses, why have to do that when they are in the contact list?
I tried sending a bunch of photos to myself using my house phone contact name and email.
It always said sendin message but never arrived. So I gave up and typed in my email adress, it popped up with my same contact name and then I recieved them in my email account.
Perhaps it is buggy and unreliable, works some times, does not work other times.

Namespace replace/rename issue in ALSB

Hi,
As part of our project we have been using ALSB3.0. In one of our outbound Proxy flows we have configured transform stage which intern executing XQuery transormation. Post transformation it publish message on BEA JMSTopic in following format.
*<?xml version="1.0" encoding="UTF-8" ?>
<ref:ABCMessage xmlns:ref="http://www.indteur.org/abc/2.1/reference">
<ref:FromEANNumber>NA</ref:FromEANNumber>
<ref:SenderIdentifier>
<ref:SenderIDType></ref:SenderIDType>
<ref:IDValue></ref:IDValue>
</ref:SenderIdentifier>
<ref:SentDate>2009-10-10T18:41:27.870-04:00</ref:SentDate>
<ref:Product>
<ref:RecordReference></ref:RecordReference>
<ref:NotificationType>04</ref:NotificationType>
<ref:RecordSourceName></ref:RecordSourceName>
</ref:Product>
</ref:ABCMessage>*
Please help us in rename/replace namespace prefix from 'ref:' to 'ns1:' at post transformation and before publishing the saem to JMS Topic.
Thanks in advance........

Personally I would mandate that what ever is the consumer of the JMSQ should be compatible with XML name space constructs. If it is not under our control then one solution would be
1) Convert the xml to string
let $strContent := fn-bea:serialize($body)
2) Replace the ref: with ns1:
return fn-bea:inlinedXML(fn:replace( $strContent, "ref:", "ns1:") )
This is a very bad solution but should solve your issue if XML is not huge (huge XML will consume lot of cpu for this transformation ) .Ideally I would recommend changing the behavior of the message consumer.
Also you can try defining name space for http://www.indteur.org/abc/2.1/reference as ns1 in sbconsole proxy name space definitions. I believe even this will work but never tried.Let me know if this works for you.
My two cents
Manoj
Edited by: mneelapu on Oct 13, 2009 9:18 AM

XI receiving scenario example

Hi Friends,
I had searched on sdn for different scenario in XI , most of them are for sendin message out of system, but I didnt got any scenario which shows receiving of message from external system...
So can you please provide some link where I can get receiving scenario example..
Thanks ,
Brijesh......

Hi Brijesh,
Any scenario involving XI will have always XI at one end as reciever and at another end as sender.
Consider the simple Idoc to file scenario where you get Idoc into XI from any R3 system and XI is the receiver system for that R3 system.
Similarly there are other scenarios (lets say SOAP to RFC)where you get SOAP requests from Third party system into XI via SOAP sender channel and then from XI Box to R3 via RFC receiver channel.
You can refer to the link below for SOAP to SOAP scenario. Invoke Webservices using SAPXI and search on sdn you will get many more examples.
Thanks!

Expiration of messages in JMSTopics / Queue Subscription to topics.

Hi all,
I tried to use topics in one of my OSB flows.
i have 2 doubts in this regard.
1. Is there a way in with i can subscribe my JMS queues to JMS topics?
2. If in my OSB flow i subscribe directly to the topic(instead of my queue subscribing to topic and my OSB flow subscibing to queue), even after my flow has taken the message from the topic, the message is still retained in the topic. How do i get rid of these retained messages in the queue dynamically. I dont want to delete those messages manually.

I'm not familiar with OSB particulars (this is a JMS forum -- OSB has its forum), but I can try answer your questions with respect to WL JMS only.
1. There's no direct facility at the WebLogic Server layer for subscribing a queue to a topic. The standard approaches are to write a basic MDB for the purpose, or configure a Messaging Bridge.
2. Are the messages in the subscription getting deleted? If not, then the problem is either in your app or at the OSB layer (failure to acknowledge/commit received messages). If so, then messages are likely accumulating in another subscription -- you can check for other subscriptions on the console, and keep in mind that distributed topics implicitly create subscriptions for forwarding messages between members. As you know, a message that is sent to a topic must be acknowledged/filtered-out/committed by all subscriptions before it is fully deleted.
It would be interesting to know the details about your use case, as I suspect it is a fairly common one. In particular, why do want to subscribe a queue to a topic subscription in the first place? I can then forward your write-up to OSB and JMS Product Managers, which might help accelerate the release of certain features on our roadmap. (email tom . barnes at oracle . com)
Tom

Error while deploying a message driven bean

I am deployeing a MDB which is done successfully but the message is not retrieved(No message in teh queue). The following description is given in the log file.
#1.5#0016E6197593004B0000000B000013040004288DE20D6CD8#1170489754872#com.sap.security.core.policy.PolicyInfoManagerImpl##com.sap.security.core.policy.PolicyInfoManagerImpl.copyApplicationConfiguration#Administrator#523####e5dbec01b35c11db90e70016e6197593#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/System/Security/WS/SecurityProtocol#Java###An error occured while copying configurations for application . Reason: #3#sap.com/MessageEAR#com.sap.engine.frame.core.configuration.NameNotFoundException#A configuration with the path "webservices/services/sap.com/MessageEAR" does not exist.#
Can you please tell where to look for it and what to do?

the session bean is ::
public class SenderBean implements SessionBean {
public static final boolean DEBUG = false;
private SessionContext ctx;
private TopicConnectionFactory factory;
private TopicConnection connection;
private Topic topic;
public SenderBean() {
 log("constructor");
public void ejbCreateSender() throws CreateException {
 log("ejbCreate");
 try {
 InitialContext naming = new InitialContext();
 factory = (TopicConnectionFactory)naming.lookup("jmsfactory/default/ExceptionTopicFactory");
 topic = (Topic)naming.lookup("jmstopics/default/ExceptionTopic");
 log("factory: " + factory);
 allocateResources();
 } catch (Exception exc) {
 log("exception occured during ejbCreate().");
 throw new CreateException("Unexpected exception in ejbCreate().");
public void ejbCreate() throws CreateException {
public void ejbActivate() {
 log("ejbActivate");
 try {
 allocateResources();
 } catch (Exception exc) {
 exc.printStackTrace();
public void ejbPassivate() {
 log("ejbPassivate");
 try {
 releaseResources();
 } catch (Exception exc) {
 exc.printStackTrace();
public void ejbRemove() {
 log("ejbRemove");
public void setSessionContext(SessionContext _ctx) {
 log("setSessionContext");
 ctx = _ctx;
public void sendMessage(String text) throws MessageNotSentException {
 log("sendMessage");
 log("text = " + text);
 TopicSession session = null;
 try {
 session = connection.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
 log("topic = " + topic);
 TopicPublisher publisher = session.createPublisher(topic);
 TextMessage textMessage = session.createTextMessage();
 textMessage.setText(text);
 publisher.publish(textMessage);
 System.out.println("Message Sent");
 log("message sent");
 } catch (JMSException jmse) {
 jmse.printStackTrace();
 throw new MessageNotSentException(jmse.toString());
 } finally {
 try {
 if (session != null) {
 session.close();
 } catch (Exception exc) {
private void releaseResources() throws JMSException {
 connection.close();
 connection = null;
private void allocateResources() throws JMSException {
 connection = factory.createTopicConnection();
 log("connection = " + connection);
 connection.start();
 log("connection started");
private void log(String message) {
 if (DEBUG) {
 System.out.println("SenderBean: " + message);
the mdb is::
public class MessageDisplayBean implements MessageDrivenBean, MessageListener {
 public static final boolean DEBUG = false;
 private MessageDrivenContext ctx;
 private QueueConnectionFactory factory;
 private QueueConnection connection;
 private Queue queue;
 public MessageDisplayBean() {
 System.out.println("In constructor");
 log("constructor");
 public void onMessage(Message message) {
 TextMessage textMessage = (TextMessage)message;
 try {
 String text = textMessage.getText();
 log("message received. Text follows:\n\n " + text + "\n\n");
 connection = factory.createQueueConnection();
 connection.start();
 QueueSession session = connection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
 TextMessage confirmation = session.createTextMessage();
 confirmation.setText("Message \""+ textMessage.getText() + "\" received.");
 //queue = session.createQueue("ConfirmationQueue");
 QueueSender sender = session.createSender(queue);
 sender.send(confirmation);
 session.close();
 connection.close();
 System.out.println("Message received");
 } catch (javax.jms.JMSException jmse) {
 public void ejbRemove() {
 log("ejbRemove()");
 public void setMessageDrivenContext(MessageDrivenContext _ctx) {
 log("setMessageDrivenContext()");
 ctx = _ctx;
 System.out.println("In context");
 public void ejbCreate() {
 try {
 System.out.println("In ejbcreate");
 InitialContext naming = new InitialContext();
 factory = (QueueConnectionFactory)naming.lookup("jmsfactory/default/ExceptionQueueFactory");
 queue = (Queue)naming.lookup("jmsqueues/default/ExceptionQueue");
 log("factory: " + factory);
 } catch (Exception exc) {
 log("exception occured during ejbCreate().");
 log("ejbCreate()");
 private void log(String str) {
 if (DEBUG) {
 System.out.println("MessageDisplayBean: " + str);
th ejb-j2ee-engine.xml is::
<ejb-j2ee-engine>
 <enterprise-beans>
 <enterprise-bean>
 <ejb-name>MessageDisplayBean</ejb-name>
 <jndi-name>MessageDisplayBean</jndi-name>
 <message-props>
 <destination-name>ExceptionTopic</destination-name>
 <connection-factory-name>ExceptionTopicFactory</connection-factory-name>
 </message-props>
 </enterprise-bean>
 <enterprise-bean>
 <ejb-name>MessageSender</ejb-name>
 <jndi-name>MessageSender</jndi-name>
 <session-props/>
 </enterprise-bean>
 </enterprise-beans>
</ejb-j2ee-engine>
the ejb-jar.xml is::
 <ejb-jar>
 <display-name> Message Driver Bean Example </display-name>
 <enterprise-beans>
 <session>
 <display-name> MessageSender </display-name>
 <ejb-name>MessageSender</ejb-name>
 <home>com.sap.message.sender.SenderHome</home>
 <remote>com.sap.message.sender.Sender</remote>
 <local-home>com.sap.message.sender.SenderLocalHome</local-home>
 <local>com.sap.message.sender.SenderLocal</local>
 <ejb-class>com.sap.message.sender.SenderBean</ejb-class>
 <session-type>Stateful</session-type>
 <transaction-type>Container</transaction-type>
 <ejb-local-ref>
 <ejb-ref-name>ejb/SenderBean</ejb-ref-name>
 <ejb-ref-type>Session</ejb-ref-type>
 <local-home>com.sap.message.sender.SenderLocalHome</local-home>
 <local>com.sap.message.sender.SenderLocal</local>
 <ejb-link>MyEJB.jar#MessageSender</ejb-link>
 </ejb-local-ref>
 <resource-ref>
 <res-ref-name>ExceptionTopicFactory</res-ref-name>
 <res-type>javax.jms.TopicConnectionFactory</res-type>
 <res-auth> Container</res-auth>
 </resource-ref>
 <resource-env-ref>
 <resource-env-ref-name>ExceptionTopic </resource-env-ref-name>
 <resource-env-ref-type> javax.jms.Topic </resource-env-ref-type>
 </resource-env-ref>
 </session>
 <message-driven>
 <ejb-name>MessageDisplayBean</ejb-name>
 <ejb-class>com.sap.message.mdb.MessageDisplayBean</ejb-class>
 <transaction-type>Container</transaction-type>
 <message-driven-destination>
 <destination-type>javax.jms.Topic</destination-type>
 </message-driven-destination>
 <resource-ref>
 <res-ref-name> ExceptionQueueFactory </res-ref-name>
 <res-type> javax.jms.QueueConnectionFactory </res-type>
 <res-auth> Container </res-auth>
 </resource-ref>
 <resource-env-ref>
 <resource-env-ref-name> ExceptionQueue </resource-env-ref-name>
 <resource-env-ref-type> javax.jms.Queue </resource-env-ref-type>
 </resource-env-ref>
 </message-driven>
 </enterprise-beans>
 <assembly-descriptor>
 <container-transaction>
 <method>
 <ejb-name>MessageDisplayBean</ejb-name>
 <method-name>onMessage</method-name>
 </method>
 <trans-attribute> NotSupported </trans-attribute>
 </container-transaction>
 </assembly-descriptor>
</ejb-jar>

"message could not be delivered"

MAILER-DAEMON are replying that message can not be delivered when sendin to my mac addresses!?
this started last night.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can
delete your own text from the attached returned message.

Nothing made sense I thought but I just recieved an answer from my web host and they explained it like this:
Our technicians are aware about this issue and they have contacted the proof point support to get the block removed
This should be done in the next couple of days and then you shoudl be able to send emails without any issues
No explanation though why there was a block.
Thanks

Error in java code for removing messages from a Topic

Trying to write a code using oracle.jms package to remove messages from Topic. I have a similar code with javax.jms package for removing messages from Queue and it is working well. Whereas i have written this new code for removing messages from topic using oracle.jms package as methods like CreateBrowser and CreateTopicReceiver for topic are provided in oracle package only and can't be used from javax.jms package.
Error i am getting is JMS-126: Invalid Topic specified at
         receiverTopic   = (Topic) ctx.lookup(((String)receiverProps.get( "Q_NAME")).trim() );
         System.out.println ("receiverTopic is[" + receiverTopic + "]");
         MBeanHome home = (MBeanHome) Helper.getAdminMBeanHome("username","pwd","url:port");
         ((AQjmsSession)topicSession).grantSystemPrivilege("MANAGE_ANY", "SA", true);
         for(Iterator i = home.getMBeansByType("JMSTopic").iterator();i.hasNext(); )
          WebLogicMBean wmb = (WebLogicMBean)i.next();
          System.out.println("topic name found: " + wmb.getName());
            topicBrowser   = ((AQjmsSession) topicSession).createBrowser(receiverTopic, "Edin");topic handle which i am receiving in receiverTopic is same as what i am expecting but still it says Invalid topic specified on createBrowser method. Anyone who can help me to write this type of code, please reply. If anyone has ready code for this situation, please reply with the same as i am working on a prodcution system and we are in serious situation to resolve this problem.

Hi,
I am afraid this is impossible. You need to find another solution like a filtering queue. Your messages can be sent to a queue that is monitored by let say a MDB. This MDB will maintain a map of title and only forward once a given title/message to your topic.
Hope it helps.
Arnaud
www.arjuna.com

Response delay in Soap Sender while processing large messages

Hi Experts,
 In one of the scenario our sender adapter is SOAP. After receiving the message its sending back the Response as HTTP 200 OK for success messges it is working fine when the message is small. When ever i am getting a large message that time its taking little bit processing time so my sender system not getting the HTTP 200 OK with in the time. (Suppose with in 3 seconds). In this case source system is sendin again the same message thinking that message is not success.
My Sender system they dont want to increase the waiting time from 3 second to .. Seconds
I cont use AAE becasue we are at 7.0.
I have to use Adapter Engine. I will not using direct communicatin with Integration Server.
 Can you please let me know how can i resolve this issue..
Thanks & Regards,
Puru

>>In this case source system is sendin again the same message thinking that message is not success.My Sender system they dont want to increase the waiting time from 3 second to .. Seconds
Looks like you are doing asynchronous SOAP scenario. You could adjust the message reprocessing time little bit later. I meant Pi does automatic reprocess messages after sometime if the mesg gets in to error state.
<IRRELEVANT LINK>
Edited by: Prateek Raj Srivastava on Mar 12, 2011 6:24 PM

Error when sending message: 500 Timeout

while sendin a message in the http to rfc scenario, im gettin this error message "Error when sending message: 500 Timeout".
can any1 throw some light on this.

Hi venu,
you need to go to RZ10 and there select the profile instance and go with the extended maintance option in the change mode.
there are two ways you can change it:
1. check out note: 824554
TCODE - rz10
icm/server_port_0 = PROT=HTTP,PORT=8010,TIMEOUT=800,PROCTIMEOUT=800
(for 800 seconds)
8010 is my HTTP port so you have to change it:)
2. SXMB_ADM -> configure integration server -> change specific identifiers
runtime parameter:
Parameter HTTP_TIMEOUT
Meaning
Specifies the timeout for http connections (time between two data packages at line level). This value overrides the system profile parameter icm/server_port_n (for example, icm/server_port_0 : PROT=HTTP, PORT=50044, TIMEOUT=900). If you do not set the parameter HTTP_TIMEOUT or if you set the parameter to 0, then the setting for the system profile parameter is used.
Personally I only changed the one from the instance profile but the second one should work too
My suggestion is change only PROCTIMEOUT to 600 or 900 but dont change TIMEOUT. Imp thing is u need to restart the XI, then onlychanges will take place.
If these dosent work out go for changing TIMEOUT also. Just set the value for the instance and dont maintain the HTTP_Timeout in the sxmb_adm
Let me know what u have done , if it works
Thanks,
srini

Dequeue a text message

Hello everyone,
DB version : 11.2.0.1.0
I'm able to add a text message on an AQ queue, but I'm not able to dequeue it from java.
When I run the dequeue method, it waits ... it doesn't get any message in, even if new messages are being put on the queue.
What am I missing ?
Creation of the AQ queue:
EXEC DBMS_AQADM.STOP_QUEUE('textmessage_queue');
EXEC DBMS_AQADM.DROP_QUEUE('textmessage_queue');
EXEC DBMS_AQADM.DROP_QUEUE_TABLE('queue_textmessage_table');
EXEC DBMS_AQADM.CREATE_QUEUE_TABLE (queue_table => 'queue_textmessage_table', queue_payload_type => 'SYS.AQ$_JMS_TEXT_MESSAGE', multiple_consumers => false);
EXEC DBMS_AQADM.CREATE_QUEUE (queue_name => 'textmessage_queue', queue_table => 'queue_textmessage_table');
EXEC DBMS_AQADM.START_QUEUE (queue_name => 'textmessage_queue');The createJMSClient(); used by the enqueue and dequeue methods
    private JMSTopic createJMSClient() {
        JMSTopic aq = new JMSTopic();
        try {
            TopicConnectionFactory topicConnectionFactory = null;
            // Get topic connection factory
            Properties info = new Properties();
            info.put(userName, userPassword);
            topicConnectionFactory = AQjmsFactory.getTopicConnectionFactory(connectString, info);
            // Creates an AQ topic connection and session
            aq.connection = topicConnectionFactory.createTopicConnection(userName, userPassword);
            // If a session is transacted, message acknowledgment is handled automatically
            //   by commit and recovery is handled automatically by rollback
            aq.session = aq.connection.createTopicSession(true, // Session is transacted
                        Session.CLIENT_ACKNOWLEDGE); // Acknowledges by commit and rollback
            System.out.println("Successfully created AQ session");
        } catch (Exception ex) {
            System.err.println("AQApplication.createJMS(): " + ex.getMessage());
            System.err.println("user = " + userName + ", password = " + userPassword + ", destination = " +
                               connectString);
            ex.printStackTrace();
        return aq;
    }Java code to enqueue a text message
        JMSTopic client = myMessage.createJMSClient();
        AQjmsSession aqjmssession = (AQjmsSession) client.session;
        AQjmsDestination destination = (AQjmsDestination)aqjmssession.getQueue(myMessage.DB_AQ_ADMIN_NAME, "textmessage_queue");
        TextMessage createTextMessage = aqjmssession.createTextMessage("This is my first text message");
        MessageProducer producer = aqjmssession.createProducer(destination);
        producer.send(createTextMessage);
        aqjmssession.commit();Java code to dequeue a text message
        JMSTopic client = myMessage.createJMSClient();
        AQjmsSession aqjmssession = (AQjmsSession)client.session;
        AQjmsDestination destination =
            (AQjmsDestination)aqjmssession.getQueue(myMessage.DB_AQ_ADMIN_NAME, "textmessage_queue");
        MessageConsumer consumer = client.session.createConsumer(destination);
        System.out.println("Waiting for a message ...");
        Message message = consumer.receive();
        System.out.println("Message received !!");

You have to start the connection (aq.connection) to receive the message. This is not required for enqueue, but required for dequeue.

Dynamic subscription of Topic "jmstopic/default/BPMMailsTopic"

Hi guys,
is it possible to subscribe a topic during the runtime (dynamically)?
I'm working with: SAP NetWeaver 7.3 (Java), JDK 1.6, NWDS 7.3 SP03.
In my coding, I'm using a Message Driven Bean with annotation to the BPMMailsTopic you can find under "SAP NetWeaver (Administration) --> Configuration --> Infrastructure --> JMS Server configuration --> jmstopic/default/BPMMailsTopic. On that topic, a component is defined, but no (durable) subscribers.
Many thanks and regards,
Cengiz

Marc,
I think I see what you're trying to do. You'll have to separate process that renders the LOV as a series of check boxes from the process that sets the checked values for each user.
Before the LOV is rendered on a page, make sure you set the session state value of the LOV item to a colon separated set of IDs based on your query:
SELECT mesg_id
FROM subscriptions
WHERE upper(network_id) = upper(:APP_USER)
If you have trouble, let me know, I'll try to come up with an example.
Sergio

WL JMS - Enterprise Message Source

Hi,
We have recently installed Oracle BAM 10.1.3. When we try to configure an Enterprise Message Source, we get only "Map Message" and "Text Message" in the drop downs for JMS Message Type.
What needs to be done to get other JMS message types such as Object Message in the drop down?
Any help in this regard will be highly appreciated.
Thanks,
KM

Hello. In the current version of BAM - we support only TextMsg type, your incoming msg on JMS should be 'xml format' only. Also note that we support only JMSTopic in current version. See webpage for full details, docs, technotes, and samples

I iphone 4 is not sending texts to my friends and family with iphones. The blue messages are not going through. My green messages are going through. Help!

My Ipone is not sending text messages. i can recieve the messages, but my replies are not being sent.. this seems to only be an issue to sendin to other iphones. The blue messages are not being sent. if the box is green, the meessage is sent.this seems to ahve started after i down;oaded the latest operating system. HELP!!

Welcome to the Verizon family, ivpacks! I regret to learn that your alarms didn't work. I also regret that there is a problem with the messages. Have you tried the alarm again? Does it still not work? For instance, just set the alarm for a couple of minutes away to ensure that the alarm goes off.
When you send a text, do you get an error? If you power the phone off/on, do the messages send? This particular issue is expecting a software update to resolve the issue with texts and picture messages.
I believe that you have chosen a great device, but keep in mind that there is a 14 day exchange period. If you exchange for the same make/model, you will not pay the restocking fee.
If you do exchange for a different make/model, there is a $35.00 restocking fee.
TamaraH_VZW
Follow us on Twitter @VZWSupport

Help/Example needed for creating JMSQueues/JMSTopics using the MBean API

I am trying to create JMSQueues programmatically using the MBean API. When
I use MBeanHome.createAdminMBean(), a queue appears in the root of the
config file. This is progress, but the queue is in the wrong place! I need
the queues to be part of my JMS server's "destinations" as seen on the
console.
So now I am trying to use createConfigurationMBean() instead, but I can't
figure out what the "parent" parameter should be- no documentation! My
first guess was that the parent might be the JMSServer, but that doesn't
work.
Anyone have example code to insert JMSQueues and JMSTopics into a specific
JMS server's destinations?
Here is the code I tried... All goes well until the final
createConfigurationMBean call, where it throws a MBeanCreationException:
// Get the MBeanHome bean
Object obj = jndiContext.lookup("weblogic.management.adminhome");
MBeanHome mbeanhome = (MBeanHome) javax.rmi.PortableRemoteObject.narrow
(obj, MBeanHome.class);
// Get the server MBean
JMSServerMBean jmsServerMB =
(JMSServerMBean)mbeanhome.getMBean("examplesJMSServer",
JMSServerMBean.class);
// Create the new Queue
JMSQueueMBean jmsQMB = (JMSQueueMBean)mbeanhome.createConfigurationMBean
("weblogic.examples.jms.fooQueue", "JMSQueue", jmsServerMB);

Ok, I still don't see how I can do it differently with the admin tool. If
you want to see the commands I'm using, I can post them, but the basic one
is shown below in the previous message. We're trying to set up a script so
that developers can just run it and properly configure WebLogic with the
right components.
Thanks,
Michelle
"Michelle Baxter" <[email protected]> wrote in message
news:[email protected]...
I am using the weblogic.Admin tool, not doing this in code. I will attempt
to translate your advice when I get time again.
My commands look like this:
java weblogic.Admin -url 127.0.0.1:7001 -username system -passwordweblogic
CREATE -mbean "mydomain:Type=JMSQueue,Name=MyJMSQueue"
I create this, I create the JMSServer MBean, then do and INVOKE (insteadof
CREATE) and call the addDestination method, adding the JMS Queue MBeanthat
I created previously, using the same naming scheme as in the above CREATE.
"Viresh Garg" <[email protected]> wrote in message
news:[email protected]...
Daron Cole wrote:
You can use createConfigurationMBean with JMSQueueConfig but in the
end
I used
the code below to create a topic.The code that you posted is the right way to create queus/topics. alwayscreate admin mbeans to admin
server and let admin server internally create config Mbeans on the
managed
server as per the
location/targets that you set in admin Mbeans.
Queue's are the same, just replace the word
Topic with Queue and it should work. It should show up in the console
app.
MBeanHome home = (MBeanHome)ctx.lookup(MBeanHome.JNDI_NAME+".myserver");
ServerMBean myserver =(ServerMBean)home.getMBean("myserver",ServerMBean.class);
String topicName = "MyNewTopic";
JMSServerMBean jmsServerMB =(JMSServerMBean)home.getMBean("JMSServer","JMSServer","mydomain");
JMSTopicMBean jmsTopicMB =(JMSTopicMBean)home.createAdminMBean(topicName,"JMSTopic","mydomain");
jmsTopicMB.setJNDIName(topicName);
jmsServerMB.addDestination(jmsTopicMB);
Viresh Garg
Principal Developer Relations Engineer
BEA Systems
"Michelle Baxter" <[email protected]> wrote:
There is no JMSQueueConfigMBean. What do you mean?
"Daron Cole" <[email protected]> wrote in message
news:[email protected]...
Try JMSQueueConfig instead of JMSQueue.
"Michelle Baxter" <[email protected]> wrote:
Me too! I'm trying to use the weblogic.Admin class to set up
queues
and
topics and the JMS server. The same results in the config file:
the
queues
and topic were set up at the root, the JMS server was added, but
no
destinations, even though I invoked the addDestination method withthe
created MBean queues and topic as arguments. No exceptions, just
no
destinations on the JMS server resulted. What's the right order ofexecution
for this stuff??
Thanks,
Michelle
"Jude DeMeis" <[email protected]> wrote in message
news:[email protected]...
I am trying to create JMSQueues programmatically using the MBean
API.
When
I use MBeanHome.createAdminMBean(), a queue appears in the root
of
the
config file. This is progress, but the queue is in the wrong
place!
I
need
the queues to be part of my JMS server's "destinations" as seen
on
the
console.
So now I am trying to use createConfigurationMBean() instead,
but
I
can't
figure out what the "parent" parameter should be- no
documentation!
My
first guess was that the parent might be the JMSServer, but that
doesn't
work.
Anyone have example code to insert JMSQueues and JMSTopics intoa
specific
JMS server's destinations?
Here is the code I tried... All goes well until the final
createConfigurationMBean call, where it throws aMBeanCreationException:
// Get the MBeanHome bean
Object obj =
jndiContext.lookup("weblogic.management.adminhome");
MBeanHome mbeanhome = (MBeanHome)javax.rmi.PortableRemoteObject.narrow
(obj, MBeanHome.class);
// Get the server MBean
JMSServerMBean jmsServerMB =
(JMSServerMBean)mbeanhome.getMBean("examplesJMSServer",
JMSServerMBean.class);
// Create the new Queue
JMSQueueMBean jmsQMB =(JMSQueueMBean)mbeanhome.createConfigurationMBean
("weblogic.examples.jms.fooQueue", "JMSQueue", jmsServerMB);

Sendin messages to a jmstopics

Similar Messages

Maybe you are looking for