Support for JMS Topic in SAP PI 7.11

Hi,
As per SAP Note 856346, JMS Topics are not supported in SAP PI (Question 2.1). However the Note is valid for SAP PI 7.1 and there is no mention for SAP PI 7.11
So can anybody please confirm if SAP PI7.11 supports JMS Topics?
Thanks,
Pankaj.

Hi,
There seems to be a lot of confusion between what is documented and what is available in actual. I did a search in help.sap.com for JMS Topic and got some information under PI7.11
http://help.sap.com/saphelp_nwpi711/helpdata/en/46/31558a9f1214dfe10000000a155369/frameset.htm
I hope that someone from SAP confirms the actual working. I dont want to raise an OSS for this
Thanks,
Pankaj.

Similar Messages

JNDI Lookup for JMS Topic issue.......!

Hi,
          Our application is deployed on two nodes (MS1 and MS2 in a cluster) and I created JMSServer on MS1, JMS ConnectionFactory and Distributed Topic are targeted on both MS1 and MS2 i.e on entire cluster.
          We have the JMS Code in postStart() method of starup class which extends ApplicationLifecycleListener which would create the JMS Subcriber and set the message listener on to it.
          code snippet:
               System.out.println("createSubscriber called");
               subSession = topicConnection.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
               // Lookup for the Topic
               Topic cadTopic = (Topic) ctx.lookup("JMSTopicLog4j");
               System.out.println("Topic is: " + cadTopic.getTopicName());
               // Create JMS Subscriber.
               cadSubscriber = subSession.createSubscriber(cadTopic);
               // Set the listener to Subscriber.
               cadSubscriber.setMessageListener(new CADMessageListener());
               topicConnection.start();
          When I start the cluster (managed Servers MS1 and MS2) for the first time and deploy the application on them (entire cluster) it works well i.e. message listener is active and able to receive messages published by publisher but when I try to stop and start MS2 it gives the following exception during server startup
          javax.naming.NameNotFoundException: Unable to resolve 'JMSTopicLog4j'. Resolved ''
          javax.naming.NameNotFoundException: Unable to resolve 'JMSTopicLog4j'. Resolved ''; remaining name 'JMSTopicLog4j'
          at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1123)
          at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:250)
          at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
          at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:204)
          at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:267)
          at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:362)
          Note: I thought my application context is getting started before JNDI tree is loaded but I could see that it is able to lookup the ConnectionFactory and throws the given exception when it comes to lookup code of JMS Topic.
          is there any configuration issue or am I missing something? Please help me in this regard.
          Thanks in advance.
          Kris.

Very interesting, I mean in the sense that we have the same setup, but instead of topic we are using the queues.
          And our problem is exactly the same,deployment works but after restart same javax.naming.NameNotFoundException happens on server 2.

Multi Language support for universes created on SAP BW/BI

Dear Gurus,
When I am going through the document "using SAP BW in Designing OLAP universes"
http://help.sap.com/businessobject/product_guides/boexir31/en/xi3-1_sap_olap_universes_en.pdf
in 13 th page under the heading "SAP BW Multilingual universes" I found the below statements.
"With Web Intelligence, it is possible to leverage the multilingual capabilities
of SAP BW. In order to implement a multilingual environment, the BW system
must include multilingual metadata and multilingual data.
You must create a universe for each language supported by the solution.
The language in which the universe connection is created determines the
language in which the universe is generated.
The user's SAP authentication determines the language of the data returned
to the query. The user must log into InfoView using SAP authentication and
specify the desired language for results returned from the SAP server.
The result-set language is dependent on SAPu2019s Unicode support. If the SAP
system does not contain the data in the desired language, the data is not
available in Web Intelligence in this language. Web Intelligence reverts to
displaying technical names instead of descriptions when the descriptions
are not translated in SAP BW."
After reading the above statements i got the impression that if i want to see the report in 10 languages then i need to create the universe in each language with seperate connection in each language.
if my understanding is correct. it araises below questions.
1. if i am creating one universe for each language will it not increase maintainance?
2. or is there any option available in universe designer which takes the replica of the universe into the desired language?
Please clarify me the above doubts.
Many thanks in Advance
Jagadeesh Ambati

Hi,
when you read it you will recognize it does make a difference between the actual data that you retrieve and the meta-data being retrieved from BW.
Meta-Data:
>>The language in which the universe connection is created determines the
>>language in which the universe is generated
Data:
The user's SAP authentication determines the language of the data returned
to the query. The user must log into InfoView using SAP authentication and
specify the desired language for results returned from the SAP server.
The result-set language is dependent on SAPu2019s Unicode support. If the SAP
system does not contain the data in the desired language, the data is not
available in Web Intelligence in this language
The user can set a Preferred Viewing language in the Preferences in InfoView.
Ingo

Support for Topics in XI JMS Adapter

Hello Everyone,
I am trying to configure Topics instead of queues for JMS Adapter and I am not able to exchange messages with Topics. However, when I change Topics with Queues in JMS configuration file on XI 2.0, the scenario works okay.
Can anyone let me know if JMS adapter for XI 2.0 or XI 3.0 supports topics. If yes, then what changes should I make in order to exchange messages with Topics via JMS adapter.
Thanks,

Hi Lalit,
No support for JMS topics in SAP XI 2.0 nor XI 3.0.
I don't know why it isn't supported. Maybe SAP wants to avoid the hassle of configuring durable subscribers. And customers forgetting to remove durable subscriptions whereby message pile up until the JMS broker runs out of disk space.
Kind regards, Guy Crets

Platforms supported by JMS adapter

Hi ,
Can anybody tell which platform/OS the JMS adapter supports ?
Regards,
Tarang

Tarang,
There is nothing to do compatibility support for JMS adapter. The one and only thing is the JMS provider like MQ-Series , Sonic MQ etc.. needs to be anlayzed for Platform/OS compatibility.
Best regards,
raj.

What are the Non SAP data sources supported for Analysis workbooks?

AO 1.4 SP6
BO 4.1 SP2
What are the Non SAP data sources supported for Analysis workbooks?
Thanks.

HANA is a data source (which could contain non-SAP data)
For other Excel front-ends that may connect to "non-SAP" data look at Live Office or Power BI by Microsoft - see Excel and Power BI connectivity to SAP BusinessObjects Universes | Power BI

How to configure a error queue for weblogic jms topic

Hi guys.
I want to configure a error queue for weblogic jms topic. Wanted: The message goes to error destination when messages have expired or reached their redelivery limit.
1. using jms transport configure proxy service:
Retry Count :3
Retry Interval:10
Error Destination: ErrorTopic
Expiration Policy: Redirect
I tried use the proxy service to consume message from the jms topic . and generation an error in the proxy message flow. But the message didn't goes into the error topic.
Any suggestions for this topic? Can anyone provide some helps or any useful links.
Thanks in advance.
Mingzhuang

Mingzhuang
I want to configure a error queue for weblogic jms topic. Wanted: The message goes to error destination when messages have expired or reached their redelivery limit.
1. using jms transport configure proxy service:
Retry Count :3
Retry Interval:10
Error Destination: ErrorTopic
Expiration olicy: RedirectUnlike File/SFTP, JMS proxy service definition does not have the concept of Error Destination. To accomplish similar functionality go to JMSQ on (for which proxy is configured) server console (http://localhost:7001/console) and configure the Error Destination. Following URL will help in how to configure JMS Q.
http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/jms_modules/queues/ConfigureQueues.html
http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/jms_modules/queues/ConfigureQueueDeliveryFailure.html
I tried use the proxy service to consume message from the jms topic . and generation an error in the proxy message flow. But the message didn't goes into the error topic.If every thing is configured as per above step, then the after retries, the weblogic server will put the message into JMS topic configured. Your proxy will receive from this topic.
Let me know if we are not on same page.
Cheers
Manoj

Flex with JMS Topic/Queue for Asynchronous messaging

I have been working on Flex and JMS integration using Data
Services for Asynchronous messaging. I am able to do this
successfuly. Now I am in need to do the same without using the Data
Services piece.
For doing this I have done the following ......
I have created a JMS Webservice in the Oracle JDeveloper 10G
along with Webservice Client.I am able to Listen to JMS Topic/Queue
( this has been created in the Oracle AS ) using this Webservice
and receive the messages from this JMS Topic/Queue
Asynchronously.....
But If I need to use the Flex Client , I am not able to
Communicate with this Webservice to listen to the JMS Topic/Queue.
Did any one in this forum tried to communicate with JMS
Topic/Queue without using Flex Data Service.If so please share your
inputs.

Here is my confusion (I'm using J2EESDK1.3).
On a local server I did the following
j2eeadmin -addJmsFactory jms/RemoteTCF topic -props url=corbaname:iiop:mars#mars
In the app client running on the local server I had the code
ic = new InitialContext();
// JNDI lookup. The resource factory ref points to the
// Remote Connection Factory I registered
tcf = (TopicConnectionFactory)ic.lookup("java:comp/env/jms/TopicConnectionFactory");
// The env ref points to jms/Topic of the local server
pTopic = (Topic)ic.lookup("java:comp/env/jms/PTopic");
So I'm assuming that I'm using a connection factory that connect to mars and a Topic on the local box.
On remote server mars, I deployed a MDB which use
jms/TopicConnectionFactory and jms/Topic. But I'm thinking this jms/Topic and the one I used on the local box are not the same one. Right? Then how could the app client and the MDB share messages?
Some of my explanation I don't if it makes sense or not.
ConnectionFactory is a way to tell what kind of connection it could generate (Queue, Topic, Durable etc) and Where the connection would go to (local or remote).'
As for as destination, I'm not sure. How could two server share one Topic?

SAP DDIC support for Index - Limitation of 16 fields

As some of you know DB2 Index advisor at times recommends indexes with more than 16 fields, Unfortunately SAP doesn't support it creating them from SAP DDIC level (SE11).
We had a recent issue in OLTP system where BW extractor on FAGLFLEXT wasn't performing as expected for a delta run. SAP OSS Support wasn't of much help. We already had an index on TIMESTAMP field, unfortunately the SQL generated by BW Delta run wasn't using TIMESTAMP field for the DELTA run. DB2advisor recommended index for the bad sql resolved the issue for us.
Is there a DB6 DBSL related profile parameter to remove the max index field limitation ?

Thanks Frank as always for quick response.
I have also got an official response from SAP DDIC Development team
Here are the details for others who want to know -
Regarding your question why DDIC supports only up to 16 index fields:
Our applications are supposed to run on several database platforms.
In order to guarantee portability of applications across all of these
DB platforms, we have to set the limits accordingly. Unfortunately,
there is at least one platform that does only support up to 16
index fields and thus we cannot support more in the DDIC. We can only
increase this limit when all supported DB versions - and this might be
very old ones because we cannot force customers to always migrate to
the newest DB version - support this.

Dell Equallogic SAN HIT Kit support for SAP in Linux 11.2

Hello Everyone,
I would like to use an Equallogic SAN as storage in SUSE Linux Enterprise Server 11.2. Is the Equallogic SAN supported in Linux when using the HIT Kit to provide MPIO and snapshot support? The article from thorsten.staerk describes Equallogic SAN + Linux + native iSCSI (no mention of the HIT Kit). I understand that there are restrictions on using third party kernel modules.
My understanding is that the Equallogic MPIO driver will provide a faster, more efficient, connection to the SAN along with additional features.
References:
Playing with an Equallogic storage
http://scn.sap.com/people/thorsten.staerk/blog/2009/02/10/playing-with-an-equallogic-storage
Thorsten describes using Equallogic with SAP on SUSE Linux Enterprise
Thorsten uses native iSCSI drivers
How to configure Multipath using Equallogic Host Integration Toolkit (HIT) on Linux for Oracle
http://en.community.dell.com/techcenter/enterprise-solutions/w/oracle_solutions/3795.how-to-configure-multipath-using-equallogic-host-integration-toolkit-hit-on-linux-for-oracle.aspx
Describes using Equallogic multipath on Linux
Mentions that the Equallogic mpio is a combination of user mode and kernel mode binaries
Dell EqualLogic Host Integration Tools
http://www.dell.com/downloads/global/products/pvaul/en/equallogic-host-software-new.pdf
Host Integration Tools Overview from Dell
Support for CentOS 5.7, Red Hat Enterprise Linux (RHEL) 5.7, 6.1 and 6.2, SUSE Enterprise Linux Server (SLES) 11 SP1
Dell EqualLogic Host Integration Tools for Linux
Installation and User's Guide Version 1.2.0
From the documentation "Installs a compatible prebuilt kernel module, if available. Otherwise, the installation script loads the Dynamic Kernel Module Support (DKMS) package and compiles the Dell EqualLogic-supplied kernel module."
EqualLogic Integration: Installation and Configuration of Host Integration Tools for Linux – HIT/Linux
The Dell EqualLogic HIT/Linux MPIO software consists of two components:
1. The EqualLogic Host Connection Manager daemon, ehcmd, which monitors the iSCSI session state and the configuration of the Linux server and PS Series group. Running in the background, the ehcmd daemon uses the Open-iSCSI management tool (iscsiadm) to add, remove, or modify iSCSI sessions to maintain an optimal number of iSCSI sessions. It also gathers information on the volume layout from the PS Series group.
2. A loadable kernel module, dm-switch, which implements a new Device Mapper target to the multipath devices. Based on the volume layout on the array members, the dm-switch module routes each I/O to the optimal path within the PS Series group.
SAP Note 784391 - SAP support terms and 3rd-party Linux
kernel drivers
The use of binary-only Linux kernel modules or drivers on the same server as SAP software is not recommended by SAP.
Thank You,
Kevin

I'll take a moment to provide an update on the solution. There were some issues with the initial configuration of the in guest iSCSI volumes. If I had to start from scratch, I would run all the storage through VMware. The last round of software updates appears to have resolved a potentially serious issue with iSCSI disconnects. iSCSI has run perfectly for two months now. I'll consider the issue resolved once I have six months without any iSCSI issues.
One remaining issue is that LVM won't initialize properly without implementing a custom init script. The init script work-around is simple and it works.
Configuration Overview:
VMware ESXi v5.5
Equallogic SAN (with v.7.0.3 firmware)
SUSE SLES v11.3
Equallogic HIT Kit for Linux v1.3

MaxDB support for SAP XI 3.0 SP 18 (NW04)

Hi,
I need an advice.
We are using SAP XI 3.0 SP 18 (NW04) on MaxDB 7.5.0.046. Because of some issues with the database we are considering upgrading to 7.6. However, it is not clear if MaxDB 7.6 is supported for NW04.
service.sap.com/pam -> SAP NetWeaver -> SAP NetWeaver 04 suggests:
1. tab Database platforms
SAP KERNEL 6.40 64-BIT UNICODE Maintained until 31.03.2013; MaxDB
supported database version: MaxDB 7.5 64-BIT
2. tab Process integration (PI/XI)
supported database version: MaxDB 7.6 64-BIT
QUESTION IS: which tab (1,2) should I trust regarding supported database version for XI?
Best Regards,
Piotr

Hi,
2. tab Process integration (PI/XI)
supported database version: MaxDB 7.6 64-BIT <b>is correct</b> as ..
1. tab Database platforms
SAP KERNEL 6.40 64-BIT UNICODE Maintained until 31.03.2013; MaxDB
<b> is for application server ABAP</b>
Award points if helpful
Regards
Umesh

Connectivity to the JMS Topic for the server synchronization information

Hi,
I am gettign below error, Can any body knows it, Please help
ProcessService 'GoYar/2011-09-16 20:21:38-04:00' created successfully.
Session initialized for participant User1 (User1 User1) with roles [ADMIN, CHECK_USER:US, APPR_USER:US, MOD_USER:US, WORK_ADMIN]
Unreachable Engine Tolerance (seconds):
by default: 0
to be used: 0
This papi client will not cache exceptions which imply that an engine could not be reached.
The connection to the JMS Topic engine was completed successfully.
Starting Fuego PAPI News Listener [cddbpdvg_dev] Service [GoYar/2011-09-16 20:21:38-04:00:46354487:29112942]
Topic Lookup topicFactoryLookupName: XATopicCF
topicLookupName: NewsTopic
The connectivity to the JMS Topic for the server synchronization information has been temporarily interrupted.
Details:
Error looking up Topic Connection Factory 'XATopicCF'.
Details:
javax.naming.NameNotFoundException: Unable to resolve 'XATopicCF'. Resolved ''; remaining name 'XATopicCF'
Caused by: Unable to resolve 'XATopicCF'. Resolved ''
fuego.papi.impl.j2ee.JMSTopicLookUpException: Error looking up Topic Connection Factory 'XATopicCF'.
Details:
javax.naming.NameNotFoundException: Unable to resolve 'XATopicCF'. Resolved ''; remaining name 'XATopicCF'
at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.lookupTopic(J2EEEngineAccessImpl.java:741)
at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.run(J2EEEngineAccessImpl.java:620)
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'XATopicCF'. Resolved ''; remaining name 'XATopicCF'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.lookupTopic(J2EEEngineAccessImpl.java:732)
... 1 more

Could this be a CLASSPATH issue?
Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)

SAP Netweaver browser support for Windows 7 OS

Hi,
can anyone provide the SAP Netweaver Portal browser support matrix for Windows 7 OS?
I could see SAP NetWeaver 7.00 Browser Support For End Users and Admin Functionality in case of Windows XP and Vista but not for Windows 7. Where can I find this information? Does SAP provided any info on this?
Regards,
Ravi.

Hi Ravi ,
win7+IE 8 will be compatible with EP 7.0 starting SP21 onwards . For more details pls check PAM - https://websmp108.sap-ag.de/pam .
Regards
Mayank

Online Meet-up 3. Does SAP provide explicit support for ALE?

hi,
yes, it does support.
for details on what is ALE please refer
Online Meet-up, 4. What is ALE?
regards,
arul sekar

Please refer to SLIDE NO: 11 of the On-line Meetup Presentation for details on where ALE fits in SAP context.
It is between AII and Device controller.
regards,
arul sekar.

Is HAGEO supported for SAP Systems?

Could anyone enlighten me as to whether HAGEO (or HACMP/XD) is supported for SAP systems? I have a client who wishes to use this and believes it is fully supported. However, I have been unable to find any references to SAP systems running on HAGEO software.
The IBM competence centre has not so far deigned to respond to my call.
Does anyone know if it is supported/recommended or actually in use for SAP installations anywhere?
This provides essentially HACMP over a much further distance than normal HACMP.
We have proposed a simple HACMP cluster with mirrored disk to a second datacentre to provide DR, however our client thinks it will be cheaper to just have two systems, one in each datacentre, and linked by HAGEO.
I have my doubts but have no evidence to the contrary currently.
Thanks
Andy

For completeness, the ISCC (i.e. IBM) said (basically) don't do it. Use standby databases.
What they actually said was that it was a very complex issue and perhaps we should get lots of IBM consulting in to answer this very difficult question.
But i took the first answer as the likely outcome - don't do HAGEO or HACMP/XD with SAP systems.
Andy.

Support for JMS Topic in SAP PI 7.11

Similar Messages

Maybe you are looking for