Creating jms administered object

I am getting the message "Object Not Found Code - 32" while creating jndi naming service under jms administered object stores. Can anyone help me how to create an object.

Looks like the entry your trying to add doesn't have a parent... I suggest that you check the DN (Context) of the entry you're trying to add and/or that the parent entry exist in your directory.
Regards,
Ludovic.

Similar Messages

Creating the JMS Administered Objects

Hi.. All
I am new to JMS..... I have written two simple programs which are given in the examples SimpleQueueSender.java and SimpleQueueReciever.java..
I successfully Compiled the programs..
But When I am trying to run the SimpleQueueSender I am getting the following error...
D:\jms>java SimpleQueueSender MyQueue 3
Queue name is MyQueue
BEFORE
AFTER
JNDI API lookup failed:javax.naming.NameNotFoundException: Unable to resolve MyQueue. Resolved: '
' Unresolved:'MyQueue' ; remaining name ''
The structure of config.xml is as follows....
<JMSConnectionFactory JNDIName="SeshuConnectionFactory"
Name="MyQueue" Targets="myserver"/>
I am using Weblogic 6.1 Server. I suppose the problem should be in creating the MyQueue JMS Administration Object...
Please help me out in solving this problem..
The portion of the code where exactly the exception is rising is as follows....
System.out.println("BEFORE");
queueConnectionFactory =(QueueConnectionFactory)jndiContext.lookup("SeshuConnectionFactory");
System.out.println("AFTER");
queue =(Queue)jndiContext.lookup(queueName);

have you configured your queues, topic, connection factory in weblogic through its admin console?
Ashwani

JMS Administered Objects

Why are "ConnectionFactory" and "Destination" administered objects?
What does the spec mean by saying that they are administered objects?
What are the advantages of having them as administered objects? (and not any other objects in the spec)?
What are the difficulties in maintaining them programatically? Why should some one admin them? What does the admin do?
Besides the above, I have another Question:
What makes anyone use multiple Sessions in one Connection, instead of using a Single Session to send messages? Why is there a Concept of a Session? Can't it just be Connection?
Can someone throw light on (any of) these?
Thanks,
Kalyan.

hi.
all applications that have a JMS Connection in order to send and receive messages, should have their Connection objects hook to the same server (the JMS provider). It is therefore appropriate that they all use a ConnectionFactory that has the same characteristics and metadata. The easiest way to do it, is to register the ConnectionFactory somewhere in the system that's well-known - e.g. a JNDI service. It doesn't make sense to have all clients configured individually. This is why you administer a ConnectionFactory.
Destination objects are also common to all clients. everyone who uses your JMS provider should have access to the correct list of destinations. again - it just doesn't make sense to configure each client separately, so you register all public Destination objects in the same service (again - JNDI is a good choice).
All other objects are application-specific. a Connection/Session/MessageConsumer (and so on) object is valid only for the application that created it. there's no need to register it elsewhere, because no one else should have access to those objects. Basically, you could say, that only objects that every client should access - are to be administered.
Multiple Session objects on a Connection are used when you want to separate parts of the application. a Session means that you are serializing the delivery of messages. if you have multiple threads in your app, you might want to give each sending thread a different Session object, because otherwise - they will all block on the communal Session.
additionally - you should not use one Session object for both consuming and producing of messages, so -if your app wishes to do both, it should have at least two Session objects.
moreover - when consuming messages, you do not use the same Session object for synchronous and a-synchronous consuming. so - if you need a consumer to block until it gets a message, and you need another consumer to wake up as a listener when a message arrives - you will need two Session objects.
Last but not least, suppose you have two producers in your application. one of them needs to use a transacted Session, and the other one does not - (or you need different acknowledge modes) - you must use multiple Session objects.
hope that helps.
Nimo.

Looking up JMS administered objects in a rich client

We have JMQ running as a broker. Using 'jmqjmsadm.sh' we added a Topic and a
TopicConnectionFactory, using
../jmqjmsadm.sh t theLogTopic logTopic
../jmqjmsadm.sh tf providerTopicFactory TopicConnectionFactory
and also set up the proxy using
../jmspadm theTopicFactory providerTopicFactory
Everything seemed to work, and all three objects show up under
SOFTWARE\iPlanet\Application Server\6.0\JMSObjects in kregedit. This is
depicted in the attached JPG.
We also have an application client running in the ACC, and this client needs
to access these JMS objects. My understanding is that iPlanet does NOT
support resource references for JMS, so even though this is a rich client my
subsequent expectation is that we would access the connection factory using
TopicConnectionFactory conFactory = (TopicConnectionFactory) jndi.lookup(
"java:comp/env/jms/providerTopicFactory" );
This does not work, unfortunately, resulting in a
javax.naming.NameNotFoundException, on the lookup on
"jms/providerTopicFactory". I have, however, also tried looking up
"java:comp/env/providerTopicFactory", and
"java:comp/env/jms/TopicConnectionFactory", and none of them are successful.
I might add thgat an earlier JNDI lookup on an env-entry is successful, so
the CosNaming is set up OK, as near as I can tell.
The app client is definitely running in the ACC; it is not a standalone.
This seems to be a combination (JMS plus rich client running in the ACC)
that is poorly documented. I am wondering if anyone has any suggestions.
TIA.
Regards,
Arved Sandstrom
[Attachment jmsobjects.jpg, see below]

Hi Arved,
Can you try to set the initial context factory using:
Properties prop = System.getProperties();
prop.put("java.naming.factory.initial","com.netscape.server.jms.RefFSContextFactory");
prop.put("java.naming.provider.url","/");
and then do a lookup using:
ctx.lookup("jms/providerTopicFactory");
Regards,
Durga
Arved Sandstrom wrote:
We have JMQ running as a broker. Using 'jmqjmsadm.sh' we added a Topic and a
TopicConnectionFactory, using
./jmqjmsadm.sh t theLogTopic logTopic
./jmqjmsadm.sh tf providerTopicFactory TopicConnectionFactory
and also set up the proxy using
./jmspadm theTopicFactory providerTopicFactory
Everything seemed to work, and all three objects show up under
SOFTWARE\iPlanet\Application Server\6.0\JMSObjects in kregedit. This is
depicted in the attached JPG.
We also have an application client running in the ACC, and this client needs
to access these JMS objects. My understanding is that iPlanet does NOT
support resource references for JMS, so even though this is a rich client my
subsequent expectation is that we would access the connection factory using
TopicConnectionFactory conFactory = (TopicConnectionFactory) jndi.lookup(
"java:comp/env/jms/providerTopicFactory" );
This does not work, unfortunately, resulting in a
javax.naming.NameNotFoundException, on the lookup on
"jms/providerTopicFactory". I have, however, also tried looking up
"java:comp/env/providerTopicFactory", and
"java:comp/env/jms/TopicConnectionFactory", and none of them are successful.
I might add thgat an earlier JNDI lookup on an env-entry is successful, so
the CosNaming is set up OK, as near as I can tell.
The app client is definitely running in the ACC; it is not a standalone.
This seems to be a combination (JMS plus rich client running in the ACC)
that is poorly documented. I am wondering if anyone has any suggestions.
TIA.
Regards,
Arved Sandstrom
[Image]--
Durgaprasad Swaminathan
iPlanet E-Commerce Solutions, A Sun-Netscape Alliance
+65 - 337 3658 (DID)
+65 - 337 4688 (Fax)

What is meant by administered objects in jms

what is meant by administered objects in jms..
and
is this Analogy true : JMS Provider like JDBC Driver
or JMS Provider like DBMS(IBM MQ)
what that provider is.....

In my previous job I was developer/administrator etc for the was environment and although I don't know if there are any hard and fast rules to what administered objects are I classed anything that get created in WAS as adminstered objects so that would be the likes of:
JMS Queues
JMS Queue Connection Factories
Datasources
J2C Aliases
JDBC Providers e.g. Sybase driver
In the case of WAS 6+ then that would also include your service integration buses, foreign MQ buses etc.
Basically anything that you can script using wsadmin
Hope that helps.
Matt

Create administered object

Hi,
I have a stand alone application which connect to an EJB server, so I would like to use the JMS provider in my application but I don't want to use my JMS provider for the creation of TopicFactory and Topic (and then use a lookup).
Is there a portable way to do this?
The only way I found is like that (with sun MQ) :
     com.sun.messaging.TopicConnectionFactory myConnFactory = new com.sun.messaging.TopicConnectionFactory();
         try {
              myConnFactory.setProperty("imqAddressList", "mq://localhost:7676/jms");
         } catch (JMSException je) {
         TopicConnection connection = myConnFactory.createTopicConnection();
         TopicSession pubSession = connection.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
        TopicSession subSession = connection.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
        com.sun.messaging.Topic myTopic = new com.sun.messaging.Topic();
        try {
             myTopic.setProperty("imqDestinationName", "new_topic_name");
        } catch (JMSException je) {
        TopicPublisher publisher = pubSession.createPublisher((javax.jms.Topic)myTopic);
        TopicSubscriber subscriber = subSession.createSubscriber((javax.jms.Topic)myTopic);
        // Set a JMS message listener
        subscriber.setMessageListener(this);
        // Intialize the Chat application
        set(connection, pubSession, subSession, publisher, username);
        // Start the JMS connection; allows messages to be delivered
        connection.start();

Several JMS implementations support JNDI lookups in pretty much any context. JNDI lookups are the recommended method of creating administered objects and they are for the most part portable (if by portable, you mean portable from JMS provider to JMS provider).
If you must create concrete objects, the only JMS agnostic method would be reflection and that would be pretty ugly.
Dwayne
============
http://dropboxmq.sourceforge.net

Sun One App Server 8.1,Sun One Message Q3.6,administered objects in LDAP

Hi,
Has anyone tried hosting an MDB on Sun One App Server 8.1 listening to a queue on Sun One Message Queue 3.6 through administered objects in directory server...? It looks quite straight forward but somehow it doesn't seems to work. Any idea if Sun one app server supports this type of architecture...?
Regards,
Pritesh

Hi,
Even I didn't see any obvious reason why it shouldn't work untill I found that Sun One App Server 8.1 does not support external JNDI lookup to Sun MQ 3.6 through administered objects. However, it is possible using a newly released generic resource adapter for JMS 1.5 RC1. I am still fighiting on it and let you know if it works.
I was getting an error "JMS resource can not be created" during deployment time.
Regards,
Pritesh Thakor

JMS Destination object not found

Hi everyone,
I have a weird problem with SunONE Message Queue 3.
I have a queue and a connection factory defined (using the SunONE Application Server 7 Admin Console) as well as a physical resource.
I can verify their existance using asadmin....
asadmin>list-jmsdest -u admin server1
queue_1 queue {}
asadmin>list-jms-resources -u admin server1
jms/newqueue_1
jms/newQCF_1
When I attempt to deploy a message driven EJB I get the following error
SEVERE ( 1484): javax.naming.InvalidNameException: JMS Destination object not found:`jms/newqueue_1`
This question has already been asked on the App Server board here http://swforum.sun.com/jive/thread.jspa?threadID=15517&tstart=0 (that post is nine months old btw).
I am posting this here in the hope that someone more familiar with MQ3 may have an idea of how to help us.
Thanks in advance.

I have now solved this problem. External JNDI resources are required in the AppServer.
They can be created with the following commands:
asadmin>create-jndi-resource jndilookupname jms/newQCF_1 resourcetype javax.jms.QueueConnectionFactory factoryclass com.sun.jndi.fscontext.RefFSContextFactory enabled=true --property java.naming.provider.url=file\:///c\:/java/mqjndi:java.naming.security.authentication=none newQCF_1
asadmin>create-jndi-resource jndilookupname jms/queue_1 resourcetype javax.jms.Queue factoryclass com.sun.jndi.fscontext.RefFSContextFactory enabled=true --property java.naming.provider.url=file\:///c\:/java/mqjndi newqueue_1
Both these commands assume that the file system context is being used however the LDAP commands are similar (just more properties).
This step, which seems vital, is missing from the AppServer documentation (in fact it specifically states that this step is not necessary). The irony is that I found the answer in the IBM MQ documentation!

What are administered objects

Examples of administered objects are apparently JMS destinations and connection factories, but what exactly are they?
Can anything "managed" by the container be called an administered object (e.g. EJBs, DataSources, etc)?
resource-ref is used to indicate "resource manager connection factory" objects, while resource-env-ref is used to indicate "admistered objects associated with resources", though that doesn't clear up much...
Could anybody please clarify?
Thanks.

Administered object is a term used by the connector specification to describe global resources exposed by resource adapters and other backend systems. JMS destinations and connection factories are two good examples.
Regarding the Java EE private component environment (java:comp/env),
the original intent was that resource-refs be used to refer to
factory objects such as JMS Connection Factories and Datasources, whereas resource-env-refs
refer to opaque resources such as JMS Destinations. In retrospect it
didn't help that much to make that distinction and it has caused a lot of confusion.
The annotations in Java EE 5 help abstract a lot of this by allowing @Resource
to be used for anything that would map to either a resource-ref or resource-env-ref.
Things like ejb references, web service references, and persistence unit/context references
each have special enough behavior that they are assigned their own unique environment
types, so those would not be refered to as administered objects.
--ken

How to create JMS Queues and Topics - OAS 10.1.3?

Hi,
Is there a way to create JMS Queues and Topics via the command line for OAS 10.1.3, say through admin-client.jar ?
I have read the "Managing Adminitered Objects" chapter from the "Oracle Containers for J2EE Resource Adapter" book and could not find the information I am looking for.
Thanks.
-Sachin

Hi Sachin --
In the 10.1.3.1 release, a set of new commands have been added to admin_client.jar to support the command line creation of JMS resources:
-addJMSConnectionFactory -domain <domain> -jndiLocation <jndiLocation> [options]
-removeJMSConnectionFactory -jndiLocation <jndiLocation>
-getJMSConnectionFactories
-addDestination -domain <domain> -name <name> -jndiLocation <jndiLocation> [options]
-removeDestination -name <name> [options]
-getDestinations
You can read about it in the doc:
http://download-west.oracle.com/docs/cd/B31017_01/web.1013/b28950/adminclient.htm#CHDDFJJA
cheers
-steve-

Issue in Creating BO Search Object Connectors

Hello,
We are in process of configuring the Enterprise Search in our project.
1. The Enterprise Search is available in ERP 6.0 , Netweaver 731 system
2. To the above system we are planning to connect a SAP ERP6 system ( SearchProvider).
3. We are using the following configuration guide.
Creating BO Search Object Connectors - SAP NetWeaver Enterprise Search - SAP Library
Issues we are facing :
1. The Administation cockpit screen does not have the options to connect the backend system.
2. Also, there are no BO search variants available in Cockpit for Step - 'choosing the SAP BO Search Variants'.
3. Also, for some of the steps provided in the guide for creating BO search object connector , there are no options available to proceed.
Is this due to some non-installation software pack not available for Enterprise Search in our SAP system where Enterprise search implemented,
or any user authorization problems?
Could you please help us in the above queries.
Regards,
Hari.

Hi Luke ,
According to one of your article , I run HRALXSYNC in r/3 , in that all indian employee are green but USA employee in RED . I found following error , can you please guide me that what is mean by that ?
The error occurred in program CL_HRRCF_INFOTYPE=============CM003 line 117
Qualification 90007487 does not exist
The incorrect HR object has the key 01NA90011026
The incorrect infotype record is 40601NA900110265105 1 1900010199991231
The error occurred in program CL_HRRCF_QUALIFICATION========CM001 line 69
Serious error; see log
The error occurred in program CL_HRRCF_CANDIDATE_INFOTYPE_BLCM00B line 99
Serious error; see log
The error occurred in program CL_HRRCF_INFOTYPE=============CM003 line 117
Qualification 90007487 does not exist
The incorrect HR object has the key 01NA90011026
The incorrect infotype record is 40601NA900110265105 1 1900010199991231
The error occurred in program CL_HRRCF_QUALIFICATION========CM001 line 69
Serious error; see log
The error occurred in program CL_HRRCF_CANDIDATE_INFOTYPE_BLCM00B line 99
Thanks
Tarun

Error while creating a callable object - User Interface

Hello,
When i'm trying to create a callable object - User Interface in the guided procedure design time. i'm getting an error. An internal server error. This is happening while i'm trying to create a guided procedure with webdynpro's.
Is there any body who allready had somthing like this.
Greetings
Kurt

Hi Raja Akella,
I allready had the roles and my portal version is upgraded until SP8 and all the possible patches.
I get an internal server error when i want to create a callable object. specially when i want to create a webdynpro ( ABAP / JAVA).
In the visual administrator i get the following errors.
Error 1
Exception occured during processing of a Web Dynpro application: "com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.".
[EXCEPTION]
com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
 at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:640)
 at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponentInternal(IWDApplicationInfo.java:286)
 at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponent(IWDApplicationInfo.java:270)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.addWdappsElement(COConfigWDApp.java:646)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readWebDynproApps(COConfigWDApp.java:631)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readApplications(COConfigWDApp.java:308)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalCOConfigWDApp.readApplications(InternalCOConfigWDApp.java:190)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.initCreate(VSelect.java:306)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.onPlugFromDispatch(VSelect.java:174)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalVSelect.wdInvokeEventHandler(InternalVSelect.java:168)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
 at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:178)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLPersistence.doReadVMO(XMLPersistence.java:126)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.readVMO(RepositoryPersistence.java:356)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.doFindRepositoryObject(RepositoryPersistence.java:598)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.findRepositoryObject(RepositoryPersistence.java:170)
 at com.sap.tc.webdynpro.repository.model.Repository.findRepositoryObjectInternal(Repository.java:590)
 at com.sap.tc.webdynpro.repository.model.RepositoryObjectRelation$XMLGuidWrapper.getModelObject(RepositoryObjectRelation.java:462)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.getCurrentLayerObject(RepositoryPersistence.java:702)
 at com.sap.tc.webdynpro.repository.model.Repository.getCurrentLayerObject(Repository.java:1483)
 at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.doMergeInheritedTarget(NonSharedRelationToOne.java:85)
 at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.mergeInheritedTargets(NonSharedRelationToOne.java:49)
 at com.sap.tc.webdynpro.repository.model.RelationToOne.getTarget(RelationToOne.java:93)
 at com.sap.tc.webdynpro.repository.model.AbstractRepositoryModelClass.getRelatedModelObject(AbstractRepositoryModelClass.java:234)
 at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:636)
 ... 39 more
Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)(:main:, row=1, col=491) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
 at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:148)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:166)
 ... 52 more
Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
 at com.sap.engine.lib.xml.parser.XMLParser.scanAttList(XMLParser.java:1566)
 at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1687)
 at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2792)
 at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259)
 at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:278)
 at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:340)
 at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
 ... 53 more
error 2
Processing HTTP request to servlet [dispatcher] finished with error. The error is: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
 at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:640)
 at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponentInternal(IWDApplicationInfo.java:286)
 at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponent(IWDApplicationInfo.java:270)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.addWdappsElement(COConfigWDApp.java:646)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readWebDynproApps(COConfigWDApp.java:631)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readApplications(COConfigWDApp.java:308)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalCOConfigWDApp.readApplications(InternalCOConfigWDApp.java:190)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.initCreate(VSelect.java:306)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.onPlugFromDispatch(VSelect.java:174)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalVSelect.wdInvokeEventHandler(InternalVSelect.java:168)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
 at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:178)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLPersistence.doReadVMO(XMLPersistence.java:126)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.readVMO(RepositoryPersistence.java:356)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.doFindRepositoryObject(RepositoryPersistence.java:598)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.findRepositoryObject(RepositoryPersistence.java:170)
 at com.sap.tc.webdynpro.repository.model.Repository.findRepositoryObjectInternal(Repository.java:590)
 at com.sap.tc.webdynpro.repository.model.RepositoryObjectRelation$XMLGuidWrapper.getModelObject(RepositoryObjectRelation.java:462)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.getCurrentLayerObject(RepositoryPersistence.java:702)
 at com.sap.tc.webdynpro.repository.model.Repository.getCurrentLayerObject(Repository.java:1483)
 at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.doMergeInheritedTarget(NonSharedRelationToOne.java:85)
 at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.mergeInheritedTargets(NonSharedRelationToOne.java:49)
 at com.sap.tc.webdynpro.repository.model.RelationToOne.getTarget(RelationToOne.java:93)
 at com.sap.tc.webdynpro.repository.model.AbstractRepositoryModelClass.getRelatedModelObject(AbstractRepositoryModelClass.java:234)
 at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:636)
 ... 39 more
Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)(:main:, row=1, col=491) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
 at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:148)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:166)
 ... 52 more
Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
 at com.sap.engine.lib.xml.parser.XMLParser.scanAttList(XMLParser.java:1566)
 at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1687)
 at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2792)
 at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259)
 at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:278)
 at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:340)
 at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
 ... 53 more
error 3
Processing HTTP request to servlet [dispatcher] finished with error.
The error is: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
Exception id: [00505691431B006F0000003E00000FE800041B45B87F7617]
thanks in advance
Kurt

Error while creating a system object for R3 in portal

Hi,
I am getting error while trying to create a system object in portal.
Following are the details I used :
Under WAS...
Web AS Host Name :<XXXX>:8001
Web AS path: /sap/bc/bsp/sap/
Web AS protocol : http
Under User management:
Authentication Ticket Type : SAP Logon Ticket
Logon Method :SAPLOGONTICKET
User Mapping Type : admin,user
Under Connector:
SAP Client : <Client NO>
SAP System ID : <System ID>
SAP System No : <System No>
System Type : SAP_R3
While trying with connection test... I am getting like this:
SAP Web AS Connection
Test Details:
The test consists of the following steps:
1. Checks the validity of system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Check whether a SAP system is defined in the system object
4. Validate the following parameters: WAS protocol; WAS host name
5. Checks if the host name of the server can be resolved.
6. Pings the server to see if it is alive.
7. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
8. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (<FQDN server name>:8001)
5. The host name <FQDN Server Name> was resolved successfully.
6. The server sapdwh01 could not be pinged successfully.
Test Connection with Connector
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
Retrieval of default alias successful
Connection failed. Make sure that Single Sign-On is configured correctly
It seems that the portal is not able to ping to R3 system. I tried to ping to R3 server from portal server by command prompt. I am able to ping. Also under SICF, I can see ping service as in activated state.
Kindly help.
Regards,
Niraj
Edited by: Niraj Kumar on Dec 11, 2008 10:41 AM

I created a SAP Transactional iView for transaction SE80.
Also, I tried from under System Administration -> Support -> SAP Transaction. It is not working.
Got portal Runtime error :
Portal Runtime Error
An exception occurred while processing your request
Exception id: 12:57_11/12/08_0003_2795650
See the details for the exception ID in the log file.
Regards,
Niraj

What is the use of creating a detail object on a measure.

Hi Experts,
In BI 4.X business layer, we can create a detail object of a dimension and as well as measure.
Can you please let me know what could be the use of the detail object of a measure object?
In the business layer, it is showing like this...
<Measure object>
-><Detail Object>
Dimensions have attributes, we create those attributes as details objects.
when we want to see the different grains of the measure in one report. we will use these details objects.
Example:
1. Query 1 returns country, sales revenue
2. Query 2 Returns Country,State,Sales revenue.
But in the report if we want to show the State wise Revenue. It is not possible bcz both the quires are returning different grain.
state object is incompatible object, so you can't drag the object into report.
in this scenario we will merge the Country dimension , create the state object as details with merged dimension, then you can drag the state details detail object.
this will give expected results Country and State wise revenue.
Normally Dimensions and details objects will drives the measures values in report.
So, Detail object on measure not helpful in case of relational database(Please correct me if i am wrong). It is useful only for OLAP database because when I have created a webi report on top of BEx query then it is automatically created a detail object on measure object.
As far I know, 'Measure attribute' introduced for OLAP based business layer. which can provides information for the formatted value like unit, currency or value.
For example:-
Amount is key figure in BEx query and when I have created Webi report on top of that then it will create three object.
1. Amount as meausre.
->2. Amount currency(detail).
->3. Amount formatted value(detail).
Below is the output after running the report.
Amount || Amount currency || Amount formatted value
30 || $ || 30.00
8 || $ || 8.00
I have found one difference, We can't implement the index awareness on detail object which we have created on measure object although we can implement the index awareness on detail object which we have created on top dimension object.
But Still I am looking for good example of Detail object on measure object..
Any thought would be welcome...
Thanks,
Sachin

I moved this to the Semantic Layer space for faster response.

How to create a text object at runtime?

Hi,
I am using crystal reports for visual studio 2010 and using c# to programming.
I need to create a text object in a specific section like section 2. and also I need to control the text object's position and text.
I tried to move a object like:
reportDocument1.ReportDefinition.Sections[j].ReportObjects.Left = 0x8760;
but object's position doesn't change at all.
How can I do these (create a text object and change a object postion)?
Thanks

Hi Don,
Thank you.
I have downloaded a RAS ( report application Server ) sample.
The sample uses the Business Objects Enterprise XI release 2. I am using win 7 and crystal reports for vs2010. Can I use this version of crystal reports to create a text object at runtime? If not, what is the lowest version I have to purchase to achieve what I want?
Basicly I need following capabilities at runtime:
1) craete text objects, line objects, image objects.
2) change text object, line object and image object positions, sizes, values of text object. If can I like to be able to change font as well.
3) supress objects, sections.
4) change section's height

Creating jms administered object

Similar Messages

Maybe you are looking for