Error in Access JMS with JNDI
Hi all,
I am trying DB>XI>TIBCO (EMS).
I have included tibjms.jar library in aii_af_jmsproviderlib.sda and deployed using SDM.
In JMS receiver adapter I am using the following:-
Transport protocol: Access JMS Provider with JNDI.
JNDI Lookup Name of Queue connection factory: com.tibco.tibjms.TibjmsQueueConnectionFactory
JNDI Lookup Name of JMS Queue: com.tibco.tibjms.TibjmsQueue
Name of JNDI Initial Context Factory:
com.tibco.tibjms.naming.TibjmsInitialContextFactory
In RWB i am getting the following for this scenario:
2005-04-17 19:55:05 Success Using connection AFW. Trying to put the message into the receive queue.
2005-04-17 19:55:05 Success The message was successfully retrieved from the receive queue.
2005-04-17 19:55:05 Success The message status set to DLNG.
2005-04-17 19:55:05 Success Deliver to channel: TIB_Receiver_JNDI
2005-04-17 19:55:05 <b>Error Exception caught by adapter framework: Object not found in lookup of XIJMSService.</b>
2005-04-17 19:55:05 Success XI message converted to binary format successfully
2005-04-17 19:55:05 <b>Error Delivery of the message to the application using connection AFW failed, due to: Object not found in lookup of XIJMSService..</b>
2005-04-17 19:55:05 Success The asynchronous message was successfully scheduled to be delivered at Sun Apr 17 20:00:05 GMT+05:30 2005.
2005-04-17 19:55:05 Success The message status set to WAIT.
Kindly help what other configurations are required.
Regards,
Arpit Seth
Hi all,
Me too have the same problem.
I am trying to integrate XI with OpenJms (server) using JMS adapter.
But the error that i am getting is similar to yours:
Error Exception caught by adapter framework: Object not found in lookup of XIJMSService.
I am very interested to the solution.
Thanks in advence.
Best regards.
Lemin
Message was edited by: lemine ould-cheikh
Similar Messages
-
Error in Access JMS with MQSeries5.2
Hi,
I'm trying to integrate Xi (SP12) with MQSeries (5.2) using the JMS Adapter (receiver) with WebSphereMQ as Transport protocol. So flatfile>XI>MQSeries (JMS Adapter)
My Parameter configs:
QueueConnectionFactory Java Class: com.ibm.mq.jms.MQQueueConnectionFactory
Queue Java Class: com.ibm.mq.jms.MQQueue
Server Name:
Server Port: 1414
Queue Manager Name: QM1
Channel Name: CHANNEL1
Queue Name: QUEUE1
Transport/Network Protocol: TCP/IP
JMS-Compliant: WebSphereMQ (non-JMS)
In RWB..Adaptor monitoring it shows the following:
Receiver Channel. Details: null
Running scenario errors in RWB with Audit logs below:
Exception caught by adapter framework: The JMS channel with channel ID 86aa3972fbc332528aa2e51b3217b8f1 is errornous. Details:null
Delivery of the message to the application using connection AFW failed, due to: The JMS channel with channel ID 86aa3972fbc332528aa2e51b3217b8f1 is errornous. Details:null.
Any advice or help would be great.
Regards,
FelixI assume the server name is not empty, is it? In that case the solution is easy
You are sure, that the drivers are deployed correctly? The server can be reached by the XI?
The character set should be entered as well.
Regards
Stefan -
Error in Access JMS with SoniqMQ
Hi,
I am trying to integrate XI with SoniqMQ using JMS Adapter( as receiver) with SoniqMQ as Transport protocol. I have deployed the necessary jar files using SDM.
File > XI> SoniqMQ ( using JMS Adapter)
The parameters that i ahve specified here are exactly what have been mentioned in help.sap.com (JMS Adapter:
QueueConnectionFactory Java Class : progress.message.jclient.QueueConnectionFactory
Queue Java Class : progress.message.jclient.Queue
Server Name :localhost
Server Port : 2506
JMS Queue : SampleQ1
When i got to RWB>Component Monitoring-> Adapter Engine-> Adapter Monitoring>JMS, after activating the Object and it is showing following error:
Receiver Channel. Details: null
When i run the scenario, i get the following error in RWB,
Exception caught by adapter framework: The JMS channel with channel ID 5ecf574401ed3c6cafdf35f1536a2bf3 is errornous. Details:null
Error Delivery of the message to the application using connection AFW failed, due to: The JMS channel with channel ID 5ecf574401ed3c6cafdf35f1536a2bf3 is errornous. Details:null.
Please guide me, how to go about.
Regards,
Siva Maranani.Hi all,
Me too have the same problem.
I am trying to integrate XI with OpenJms (server) using JMS adapter.
But the error that i am getting is similar to yours:
Error Exception caught by adapter framework: Object not found in lookup of XIJMSService.
I am very interested to the solution.
Thanks in advence.
Best regards.
Lemin
Message was edited by: lemine ould-cheikh -
Error while accessing application with custom components
Hi experts,
I have an application (HAP_MAIN_DOCUMENT) of component FPM_OIF_COMPONENT which uses a Webdynpro component with the same name (HAP_MAIN_DOCUMENT). This Webdynpro component (HAP_MAIN_DOCUMENT) uses 2 other components (HAP_DOCUMENT_BODY and HAP_DOCUMENT_HEADER).
For my client requirement, i need to create the custom components by copying from standard components as the UI layout changes are quiet huge and not manageable with the enhancements. To accomodate this i have changed the standard configurations by replacing the standard web dynpro components with the custom ones copied. Apart fomr this there are no changes to the standard.
While trying to access the application, i am getting the error as Null object reference. the details of the error is as below. Please advice.
Portal Error
Error when processing your request
What has happened?
The URL http://ddrsap12.dubal.domain:8001/sap/bc/webdynpro/sap/HAP_MAIN_DOCUMENT/ was not called due to an error.
Note
The following error text was processed in the system DSD : Access via 'NULL' object reference not possible.
The error occurred on the application server ddrsap12_DSD_01 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: WDDOINIT of program /1BCWDY/LUR96POELQNL3TIUWPYS==CP
Method: IF_WDR_VIEW_DELEGATE~WD_DO_INIT of program /1BCWDY/LUR96POELQNL3TIUWPYS==CP
Method: DO_INIT of program CL_WDR_DELEGATING_VIEW========CP
Method: INIT_CONTROLLER of program CL_WDR_CONTROLLER=============CP
Method: INIT_CONTROLLER of program CL_WDR_VIEW===================CP
Method: INIT of program CL_WDR_CONTROLLER=============CP
Method: GET_VIEW of program CL_WDR_VIEW_MANAGER===========CP
Method: BIND_ROOT of program CL_WDR_VIEW_MANAGER===========CP
Method: INIT of program CL_WDR_VIEW_MANAGER===========CP
Method: INIT_CONTROLLER of program CL_WDR_INTERFACE_VIEW=========CP
ST22 Dump Analysis
Short text
Access via 'NULL' object reference not possible.
What happened?
Error in the ABAP Application Program
The current ABAP program "/1BCWDY/LUR96POELQNL3TIUWPYS==CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
Information on where terminated
Termination occurred in the ABAP program "/1BCWDY/LUR96POELQNL3TIUWPYS==CP" -
in "WDDOINIT".
The main program was "SAPMHTTP ".
In the source code you have the termination point in line 4640
of the (Include) program "/1BCWDY/B_LUXVEOR5WUW66V6QRRNU".
Termination occurred in a Web Dynpro application
Web Dynpro Component ZWD_HAP_DOCUMENT_HEADER
Web Dynpro Controller VW_HEADER_MAIN
The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in
procedure "WDDOINIT" "(METHOD)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.
The procedure is in program "/1BCWDY/LUR96POELQNL3TIUWPYS==CP "; its source
code begins in line
4619 of the (Include program "/1BCWDY/B_LUXVEOR5WUW66V6QRRNU ".
Active Calls/Events
No. Ty. Program Include Line
Name
33 METHOD /1BCWDY/LUR96POELQNL3TIUWPYS==CP /1BCWDY/B_LUXVEOR5WUW66V6QRRNU 4640
CL_VW_HEADER_MAIN_CTR=>WDDOINIT
Web Dynpro Component ZWD_HAP_DOCUMENT_HEADER
Web Dynpro Controller VW_HEADER_MAIN
32 METHOD /1BCWDY/LUR96POELQNL3TIUWPYS==CP /1BCWDY/B_LUXVEOR5WUW66V6QRRNU 70
CLF_VW_HEADER_MAIN_CTR=>IF_WDR_VIEW_DELEGATE~WD_DO_INIT
Web Dynpro Component ZWD_HAP_DOCUMENT_HEADER
Web Dynpro Controller VW_HEADER_MAIN
31 METHOD CL_WDR_DELEGATING_VIEW========CP CL_WDR_DELEGATING_VIEW========CM003 3
CL_WDR_DELEGATING_VIEW=>DO_INIT
30 METHOD CL_WDR_CONTROLLER=============CP CL_WDR_CONTROLLER=============CM00Q 3
CL_WDR_CONTROLLER=>INIT_CONTROLLER
29 METHOD CL_WDR_VIEW===================CP CL_WDR_VIEW===================CM00K 5
CL_WDR_VIEW=>INIT_CONTROLLER
28 METHOD CL_WDR_CONTROLLER=============CP CL_WDR_CONTROLLER=============CM002 7
CL_WDR_CONTROLLER=>INIT
27 METHOD CL_WDR_VIEW_MANAGER===========CP CL_WDR_VIEW_MANAGER===========CM008 70
CL_WDR_VIEW_MANAGER=>GET_VIEW
26 METHOD CL_WDR_VIEW_MANAGER===========CP CL_WDR_VIEW_MANAGER===========CM005 23
CL_WDR_VIEW_MANAGER=>BIND_ROOT
25 METHOD CL_WDR_VIEW_MANAGER===========CP CL_WDR_VIEW_MANAGER===========CM00B 17
CL_WDR_VIEW_MANAGER=>INIT
24 METHOD CL_WDR_INTERFACE_VIEW=========CP CL_WDR_INTERFACE_VIEW=========CM004 11
CL_WDR_INTERFACE_VIEW=>INIT_CONTROLLER
23 METHOD CL_WDR_CONTROLLER=============CP CL_WDR_CONTROLLER=============CM002 7
CL_WDR_CONTROLLER=>INIT
22 METHOD CL_WDR_VIEW_MANAGER===========CP CL_WDR_VIEW_MANAGER===========CM008 70
CL_WDR_VIEW_MANAGER=>GET_VIEW
Thanks in advance,
Regards,
Ravi.Hi ,
How are you able to configure Custom Web dynpro application to Appraisal document instead of HAP_MAIN_DOCUMENT. could you please share the steps. We have created custom application a copy of HAP_MAIN_DOCUMENT and the other two webdynpro components are also copied.
We dont know how to link this to Appraisal template. BADI HRHAP00_BSP_TMPL is used to change application names for BSP application. How to change application name for Web dynpro ABAP. Please share the stpes which will help us
Thanks and Regards,
Kothand -
Error while accessing application with the custom components
Hi experts,
I have an application (HAP_MAIN_DOCUMENT) of component FPM_OIF_COMPONENT which uses a Webdynpro component with the same name (HAP_MAIN_DOCUMENT). This Webdynpro component (HAP_MAIN_DOCUMENT) uses 2 other components (HAP_DOCUMENT_BODY and HAP_DOCUMENT_HEADER). For my client requirement, i need to create the custom components by copying from standard components as the UI layout changes are quiet huge and not manageable with the enhancements. To accomodate this i have changed the standard configurations by replacing the standard web dynpro components with the custom ones copied. Apart fomr this there are no changes to the standard.
While trying to access the application, i am getting the error as Null object reference.
the details of the error is as below. Please advice.
Heading 1: h1. P:ortal Error
The URL http://******************/sap/bc/webdynpro/sap/HAP_MAIN_DOCUMENT/ was not called due to an error.
Note
The following error text was processed in the system DSD : Access via 'NULL' object reference not possible.
The error occurred on the application server ddrsap12_DSD_01 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: WDDOINIT of program /1BCWDY/LUR96POELQNL3TIUWPYS==CP
Method: IF_WDR_VIEW_DELEGATE~WD_DO_INIT of program /1BCWDY/LUR96POELQNL3TIUWPYS==CP
Method: DO_INIT of program CL_WDR_DELEGATING_VIEW========CP
Method: INIT_CONTROLLER of program CL_WDR_CONTROLLER=============CP
Method: INIT_CONTROLLER of program CL_WDR_VIEW===================CP
Method: INIT of program CL_WDR_CONTROLLER=============CP
Method: GET_VIEW of program CL_WDR_VIEW_MANAGER===========CP
Method: BIND_ROOT of program CL_WDR_VIEW_MANAGER===========CP
Method: INIT of program CL_WDR_VIEW_MANAGER===========CP
Method: INIT_CONTROLLER of program CL_WDR_INTERFACE_VIEW=========CP
Heading 2: h2. ST22 - Dump Analysis
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
caught in
procedure "WDDOINIT" "(METHOD)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component.
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.
Information on where terminated
Termination occurred in the ABAP program "/1BCWDY/LUR96POELQNL3TIUWPYS==CP" -
in "WDDOINIT".
The main program was "SAPMHTTP ".
In the source code you have the termination point in line 4640
of the (Include) program "/1BCWDY/B_LUXVEOR5WUW66V6QRRNU".
Termination occurred in a Web Dynpro application
Web Dynpro Component ZWD_HAP_DOCUMENT_HEADER
Web Dynpro Controller VW_HEADER_MAIN
The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in
procedure "WDDOINIT" "(METHOD)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.
The procedure is in program "/1BCWDY/LUR96POELQNL3TIUWPYS==CP "; its source
code begins in line
4619 of the (Include program "/1BCWDY/B_LUXVEOR5WUW66V6QRRNU ".
Active Calls/Events
No. Ty. Program Include Line
Name
33 METHOD /1BCWDY/LUR96POELQNL3TIUWPYS==CP /1BCWDY/B_LUXVEOR5WUW66V6QRRNU 4640
CL_VW_HEADER_MAIN_CTR=>WDDOINIT
Web Dynpro Component ZWD_HAP_DOCUMENT_HEADER
Web Dynpro Controller VW_HEADER_MAIN
32 METHOD /1BCWDY/LUR96POELQNL3TIUWPYS==CP /1BCWDY/B_LUXVEOR5WUW66V6QRRNU 70
CLF_VW_HEADER_MAIN_CTR=>IF_WDR_VIEW_DELEGATE~WD_DO_INIT
Web Dynpro Component ZWD_HAP_DOCUMENT_HEADER
Web Dynpro Controller VW_HEADER_MAIN
31 METHOD CL_WDR_DELEGATING_VIEW========CP CL_WDR_DELEGATING_VIEW========CM003 3
CL_WDR_DELEGATING_VIEW=>DO_INIT
30 METHOD CL_WDR_CONTROLLER=============CP CL_WDR_CONTROLLER=============CM00Q 3
CL_WDR_CONTROLLER=>INIT_CONTROLLER
29 METHOD CL_WDR_VIEW===================CP CL_WDR_VIEW===================CM00K 5
CL_WDR_VIEW=>INIT_CONTROLLER
28 METHOD CL_WDR_CONTROLLER=============CP CL_WDR_CONTROLLER=============CM002 7
CL_WDR_CONTROLLER=>INIT
27 METHOD CL_WDR_VIEW_MANAGER===========CP CL_WDR_VIEW_MANAGER===========CM008 70
CL_WDR_VIEW_MANAGER=>GET_VIEW
26 METHOD CL_WDR_VIEW_MANAGER===========CP CL_WDR_VIEW_MANAGER===========CM005 23
CL_WDR_VIEW_MANAGER=>BIND_ROOT
25 METHOD CL_WDR_VIEW_MANAGER===========CP CL_WDR_VIEW_MANAGER===========CM00B 17
CL_WDR_VIEW_MANAGER=>INIT
24 METHOD CL_WDR_INTERFACE_VIEW=========CP CL_WDR_INTERFACE_VIEW=========CM004 11
CL_WDR_INTERFACE_VIEW=>INIT_CONTROLLER
23 METHOD CL_WDR_CONTROLLER=============CP CL_WDR_CONTROLLER=============CM002 7
CL_WDR_CONTROLLER=>INIT
22 METHOD CL_WDR_VIEW_MANAGER===========CP CL_WDR_VIEW_MANAGER===========CM008 70
CL_WDR_VIEW_MANAGER=>GET_VIEW
Thanks In advance,
Regards,
Ravi.Hi, I'm closing this thread and opening the same in another as the content got pasted in reader un friendly format and i'm unable to change the format.
Thanks,
Ravi. -
Error :- while accessing JMS topic messages in Design Studio
Hi,
Am getting this error while clicking update button in Design Studio to populate a dataobject using JMS Topic messages sent by oracle Bpel manager.
IMessageSourceReceiver->messageReceive: javax.naming.NoInitialContextException: Cannot instantiate class: oracle.j2ee.rmi.RMIInitialContextFactory. Root exception is java.lang.ClassNotFoundException: oracle.j2ee.rmi.RMIInitialContextFactory
Can you tell me where to find the class and how to use it to resolve the problem?
P.S:-
If you can provide any document how oracle BPEL process manager use JMS topic to send message to Oracle BAM and display in reports.
Thanks in advance
Cheers,
Praveen G
iSOFT R& D Pvt Ltd.
[email protected]Hi,
We are using BAM 10.1.3 against BPEL 10.1.2 and we cannot get it to work.
We are also getting the error "javax.naming.NoInitialContextException: Cannot instantiate class: oracle.j2ee.rmi.RMIInitialContextFactory...." .
Our startup paramters for Enterprise Source “Oracle (AS JMS and OJMS) looks like this:
JMS*".;C:\OracleBAM\OC4J\j2ee\home\lib\jms.jar;C:\OracleBAM\OC4J\j2ee\home\lib\jndi.jar;C:\OracleBAM\OC4J\j2ee\home\oc4j.jar;C:\OracleBAM\OC4J\j2ee\home\oc4jclient.jar;C:\OracleBAM\OC4J\j2ee\home\lib\oc4j-internal.jar;C:\OracleBAM\OC4J\j2ee\home\lib\ejb.jar;C:\OracleBAM\OC4J\j2ee\home\lib\servlet.jar;C:\OracleBAM\OC4J\j2ee\home\lib\jta.jar;C:\OracleBAM\OC4J\j2ee\home\lib\jms.jar;C:\OracleBAM\OC4J\j2ee\home\lib\javax88.jar;C:\OracleBAM\OC4J\j2ee\home\lib\javax77.jar;C:\OracleBAM\OC4J\j2ee\home\lib\jmxri.jar;C:\OracleBAM\OC4J\j2ee\home\lib\jmx_remote_api.jar;C:\OracleBAM\OC4J\j2ee\home\lib\adminclient.jar;C:\OracleBAM\OC4J\j2ee\home\ojspc.jar;C:\OracleBAM\OC4J\j2ee\home\jazn.jar;C:\OracleBAM\OC4J\opmn\lib\optic.jar;C:\OracleBAM\OC4J\rdbms\jlib\aqapi.jar;"".;c:\TIBCO\JMS\clients\java\tibjms.jar;c:\TIBCO\JMS\clients\java\jms.jar;c:\TIBCO\JMS\clients\java\jndi.jar;c:\TIBCO\JMS\clients\java\jta-spec1_0_1.jar;c:\TIBCO\JMS\clients\java\jcert.jar;c:\TIBCO\JMS\clients\java\jnet.jar;c:\TIBCO\JMS\clients\java\jsse.jar;c:\TIBCO\JMS\clients\java\tibcrypt.jar;"".;C:\Program Files\IBM\WebSphere MQ\Java\lib\com.ibm.mq.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\com.ibm.mqjms.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\connector.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\jms.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\jndi.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\jta.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\providerutil.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\fscontext.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\ldap.jar;"".;C:\Program Files\SonicSoftware\SonicMQ\lib\sonic_Client.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\gnu-regexp-1.0.6.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\jaxp.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\xerces.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\tools.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\providerutil.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\fscontext.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\sslj.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\jsafe.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\certj.jar;"".;C:\bea\weblogic700\server\lib\weblogic.jar;"".;C:\eGate\client\classes\stcjms.jar;C:\eGate\client\JRE\1.3\lib\ext\fscontext.jar;C:\eGate\client\JRE\1.3\lib\ext\providerutil.jar;C:\eGate\client\ThirdParty\sun\jms.jar;C:\eGate\client\ThirdParty\sun\jndi.jar;C:\eGate\client\ThirdParty\sun\jta.jar;"".;C:\JNDI-Directory_WebMethods\fscontext.jar;C:\JNDI-Directory_WebMethods\providerutil.jar;C:\JNDI-Directory_WebMethods\javax.jms.jar;C:\Program Files\webMethods6\Broker\lib\BrokerJMS60.jar;C:\Program Files\webMethods6\common\lib\client60.jar;C:\Program Files\webMethods6\Broker\lib\xerces.jar;"
We are trying to get to our oc4j container on our BPEL server. We have the following settings on our created message sourcein BAM architect:
Initial Context Factory: oracle.j2ee.rmi.RMIInitialContextFactory
JNDI Service Provider URL: opmn:ormi://hostname:6003:OC4J_BPEL
TopicConnectionFactory Name: java:comp/resource/ojms_ipl/TopicConnectionFactories/iplerror
Topic Name: java:comp/resource/ojms_ipl/Topics/iplerror
ojms_ipl refers to the datasource on our BPEL server that is defined in application.xml.
Where is the class located?
Best regards -
404-Errors when accessing servlets with accented characters or umlauts as a parameter
When accessing the following url
http://test.sdm.de:8080/servlets/testservlet?la=Constitucion
, the servlet works quite well and produces the desired response.
The accented character is recieved by the servlet, and can be processed and displayed.
But after once sending a request containing an accented character or an umlaut as parameter, all following requests result in 404-Errors (Only in IE, the Netscape seems to automatically encode all problematic characters).
The problem occurs only if the accented character is in the (action-)url. Passing it by a textfield works quite fine.
Has anyone any idea how to fix this?
Thank youHi,
please can you explain me in wich config-file is neccesary make the changes?
I'm working with Linux and I have the same problem. In Windows it's ok.
Thank's a lot. -
Error 20544 Access Denied with Crystal ActiveX control in VB6
Post Author: beckybear
CA Forum: General
We have a piece of legacy software written a while ago that is in VB6 using the Crystal ActiveX control crystl32.ocx. We use 8.5 of Crystal Reports.About 50 or so users have this program loaded and it runs a single crystal report from a server location. Most days, everything runs just fine, but lately more and more we've been having a problem where our some of our users get the message "Runtime Error 20544. Access to report file denied. Another program may be using it." The same user will continue to get this error, even after rebooting, while others continue with no issues. It's never the same people affected day to day. And it always works for everyone the next day.I've read about a 20 limit on reports, but new users can log in and use the program with no problem, so if it's a connection limit, it doesn't seem right that new users would work. Also, the workaround for that I found for that particular limit problem, setting it as a temporary report, doesn't seem to be available with the ActiveX control. We cannot reliably reproduce the problem.So I guess my questions are, do you have any idea why it would work the next day without a reboot of the server or the user's machine? If this is a limit problem, where is that limit stored, or how can I test to see that it is the limit problem? What else could it be and is there anything I can add in the VB program to try and prevent this (cleanup, checks, etc.)? Is this ActiveX control still supported and recommended with version 8.5? Is there a different component we should be using?Thanks in advance for any help you can offer for this frustrating problem. I searched the old archives and found others reporting this problem, but no solutions.Post Author: RayK
CA Forum: General
Did you find a solution for this problem? I'm having the same sporadic problem with Crystal 8.5. It usually goes away for a user by logging out and back in, but I'm getting a lot of complaints. The report is being sent directly to the printer - no Preview mode as has been reported as the cause for some people.
Thanks -
Hi,
I am trying to read response from JMS Queue hosted on Weblogic server and getting below exception. Any help on this will be appreciable.
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Environment not found on thread ]
at weblogic.jndi.internal.NamingNodeReplicaHandler.<init>(NamingNodeReplicaHandler.java:148)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:90)
at weblogic.common.internal.ChunkedObjectInputStream.readObjectWL(ChunkedObjectInputStream.java:159)
at weblogic.common.internal.ChunkedObjectInputStream$NestedObjectInputStream.readObjectWL(ChunkedObjectInputStream.java:341)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.readExternal(ReplicaAwareRemoteRef.java:356)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1686)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1644)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:452)
at weblogic.rmi.internal.StubInfo.readObject(StubInfo.java:95)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:838)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1746)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:111)
at weblogic.common.internal.ChunkedObjectInputStream.readObjectWL(ChunkedObjectInputStream.java:159)
at weblogic.common.internal.ChunkedObjectInputStream$NestedObjectInputStream.readObjectWL(ChunkedObjectInputStream.java:341)
at weblogic.jndi.internal.WLContextImpl.readExternal(WLContextImpl.java:425)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1686)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1644)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:111)
at weblogic.rjvm.ResponseImpl.getThrowable(ResponseImpl.java:117)
at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:106)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:127)
at weblogic.jms.dispatcher.DispatcherImpl_1035_WLStub.dispatchSyncNoTranFuture(Unknown Source)
at weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSyncNoTran(DispatcherWrapperState.java:341)
at weblogic.jms.client.JMSSession.createDestination(JMSSession.java:1735)
at weblogic.jms.client.JMSSession.createQueue(JMSSession.java:1296)
ThanksHi,
I am trying to read Queue standalone. Please find the code snippet below. code highlighted in where i am getting exception.
public static void main(String[] args) {
String jmsServerUrl = "t3://10.51.245.45:5858";
String jmsUserName = "weblogic";
String jmsPassword = "welcome123";
String jndiFactory = "weblogic.jndi.WLInitialContextFactory";
String jmsFactory = "jms/CBCMReplyConnectionFactory";
String qName = "jms/CBCMOrderReplyQueue";
QueueReceiver qReciever = null;
JMSQueueReader.getQueueSession(jmsServerUrl,jmsUserName,jmsPassword,jndiFactory,jmsFactory);
qReciever = JMSQueueReader.getQueueReceiver(qName);
if (qReciever == null) {
System.out.println("Unable to find JMS Queue Reciever for Queue Name: "
+ qName + " and JMS Server URL:"
+ jmsServerUrl);
//isProcess = false;
private static InitialContext getInitialContext(String url, String userName, String password, String jndiFactory) throws NamingException {
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, jndiFactory);
env.put(Context.PROVIDER_URL, url);
env.put(Context.SECURITY_PRINCIPAL, userName);
env.put(Context.SECURITY_CREDENTIALS, password);
return new InitialContext(env);
public static QueueReceiver getQueueReceiver(String qName) {
try {
if(qReceiver == null || !qName.equals(queueName))
queueName = qName;
if(qReceiver != null)
qReceiver.close();
qReceiver = null;
javax.jms.Queue queue = qSession.createQueue(queueName);
//qReceiver = qSession.createReceiver(queue);
qReceiver = qSession.createReceiver(queue, "JMSCorrelationID LIKE '"+SOHConstant.CBCM_BSCS_CORRELATION_ID_PREFIX+"%'");
} catch (Throwable e) {
e.printStackTrace();
return qReceiver; -
To all people with gmail error and accessing inbox with upgrade-
Go to your gmail on your computer, click settings on the top right, click the IMAP/POP tab, enable IMAP, and POP. Save Settings. Vuallah.
Or, as the French would say, "Voila!"
-
Error while using webmethod JMS provider with JNDI
Hi,
I am using webmethod JMS provider (not SAP JMS) with JNDI to connect to webmethod with XI. Central J2EE adapter engine is used and the comm chaneel is configured in with appropriate Provider JNDI Server address, initial context factory, Name of queue connection factory etc.
While activated the adapter short log shows: Adapter has not provided any status information about this channel"
In the detailed log following error message is displayed: "Obtained connection factory: null#"
#1.5 #001A4BAC31000052000001520000152200045090BF28DACA#1214482519514#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
#1.5 #001A4BAC31000052000001530000152200045090BF28DB65#1214482519514#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Debug##Plain###Looking up connection factory under name NAIP_XIQueueConnectionFactory#
#1.5 #001A4BAC31000052000001540000152200045090BF28E42E#1214482519516#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Debug##Plain###Obtained connection factory: null#
#1.5 #001A4BAC31000052000001550000152200045090BF28E4B3#1214482519516#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
#1.5 #001A4BAC31000052000001560000152200045090BF28E528#1214482519516#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeConnectionFactoryInvocations()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
#1.5 #001A4BAC31000052000001570000152200045090BF28E5A9#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeConnectionFactoryInvocations()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Info##Java###Sucessfully executed CF invocations for connection factory object: for profile: #2#<null>#ConnectionProfile of channel: CC_RCV_JMS_SAPJNDIon node: 3010950 having object id: e4413a5265a436459e271d5e0dd4859b#
#1.5 #001A4BAC31000052000001580000152200045090BF28E64E#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeConnectionFactoryInvocations()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
#1.5 #001A4BAC31000052000001590000152200045090BF28E6CA#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
#1.5 #001A4BAC310000520000015A0000152200045090BF28E741#1214482519517#com.sap.aii.adapter.jms.core.common.StringUtils##com.sap.aii.adapter.jms.core.common.StringUtils.isBlank(String str)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
#1.5 #001A4BAC310000520000015B0000152200045090BF28E7C3#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Debug##Plain###Creating connection...#
#1.5 #001A4BAC310000520000015C0000152200045090BF28EB51#1214482519518#com.sap.aii.adapter.jms.core.channel.AdapterImpl##com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(Channel cpaChannel)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Warning##Java###Catching #1#java.lang.NullPointerException
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection(ConnectorImpl.java:198)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.doConnect(ConnectorImpl.java:166)
at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.doConnect(JndiConnectorImpl.java:186)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connect(ConnectorImpl.java:151)
at com.sap.aii.adapter.jms.core.channel.ChannelImpl.doStart(ChannelImpl.java:235)
at com.sap.aii.adapter.jms.core.channel.ChannelImpl.start(ChannelImpl.java:154)
at com.sap.aii.adapter.jms.core.channel.AdapterImpl.doAddUpdateChannel(AdapterImpl.java:404)
at com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(AdapterImpl.java:376)
at com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl$1.run(ChannelLifecycleCallbackImpl.java:51)
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:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
#1.5 #001A4BAC310000520000015D0000152200045090BF28EC6A#1214482519518#com.sap.aii.adapter.jms.core.channel.AdapterImpl##com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(Channel cpaChannel)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Error##Plain###[[ChannelName:CC_RCV_JMS_SAPJNDI,ChannelId: e4413a5265a436459e271d5e0dd4859b]] Error adding/updating channel.#
#1.5 #001A4BAC310000520000015E0000152200045090BF28ECF8#1214482519518#com.sap.aii.adapter.jms.core.channel.AdapterImpl##com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(Channel cpaChannel)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
#1.5 #001A4BAC310000520000015F0000152200045090BF28ED76#1214482519519#com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl##com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl.channelAdded().run()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
#1.5 #001A4BAC3100005F000000660000152200045090BF65478A#1214482523474#com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl.channelAdded(Channel channel)#AAAAAAAAA#108##n/a##002ee500437911dd99cf001a4bac3100#SAPEngine_Application_Thread[impl:3]_29##0#0#Path##Plain###Exiting method#
Please let me know anyone has come accross the problem or has idea how to solve it. Thanks.Hi,
Ask ur basis admin to restart JMS adpater From Vis administrator and try again to activate the comm channel.
Hope this will solve ur problem and once again check connection fatcory and Queue name provided by Webmethod admin.
Regards,
Srini -
Question about "mod_security: Access denied with code 400"
Dear All,
After merged clone's configure the application tier server nodes. I can get in form window, but after merged clone's finishing tasks:1.Generate JAR files / generate message files / relink executables / copy files to destination. I can't open form window any more.
The apache error_log will show below
mod_security: Access denied with code 400. Pattern match "!^([-_@|#!=A-Za-z0-9/ :.$]){0,255}([-_@|#!=A-Za-z0-9/:.$]){0,255}$" at ARGS_NAMES. [hostname "hcp11et30.liteonit.com.tw"] [uri "/oprocmgr-service"] [unique_id TugHyQoG2lsAAFOwD84]
Then referred Note 389558.1, and can login normally, But the same error messages still keeping reporting in error_log.
Please advise?
Thanks,
JackieHi;
Did you check below notes:
Access Denied With Code 400 When Starting Forms or Calling MOD_PLSQL [ID 394587.1]
Why do we see Error: mod_security: access denied with code 400 IN OCO pages? [ID 976473.1]
Regard
Helios -
Error in JMS receiver adapter: "Error creating initial context with environment"
Hello,
I have some trouble with a JMS receiver adapter (access to JMS-provider with JNDI).
The message in adapter monitoring is:
A channel error occurred. Detailed error (if any) :
com.sap.aii.adapter.jms.api.connector.ConnectorException: Fatal Error looking up connection factoryJMSQueueConnectionFactory, for profile: ConnectionProfile of channel: CC_JMS_RCV_XLIMI00001on node: 503473150 having object id: 5b424f2f79b6350ca636ab35d528cfdd:
ConnectorException: Error creating initial context with environment: java.naming.provider.url=wcsefdev.example.com:9064; java.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory; for profile: ConnectionProfile of channel:
CC_JMS_RCV_XLIMI00001on node: 503473150 having object id: 5b424f2f79b6350ca636ab35d528cfdd: javax.naming.NoInitialContextException:
Cannot instantiate class: com.ibm.websphere.naming.WsnInitialContextFactory<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory
(JndiConnectorImpl.java:152)<br> ....
Message processing failed. Cause:
com.sap.aii.adapter.jms.core.fsm.DFA$InvalidTransitionException: No transition found from state: ERROR, on event: process_commence for DFA: CC_JMS_RCV_XLIMI00001:5b424f2f79b6350ca636ab35d528cfdd
The third party assured me that the specified JNDI parameters are right and everything is configured on their site, so it should work...
Might there be a problem with the JMS drivers?
Regards,
MarcusHi Marcus,
Have a look at below thread
Connecting to PI 7.11 JMS Queue from other PI 7.11 Server -
XI to IBM Websphere Default JMS Provider with JNDI
Hello everybody!
We face a problem with connecting SAP XI to IBM WebSphere Default JMS Provider (need to send a message from XI to WebSphere JMS and receive the response).
We have the following versions installed:
SAP XI: 7.0 SP8 , Sun JDK 1.4.2
IBM WebSphere: IBM WebSphere Application Server ND, 6.0.2.17, J2RE 1.4.2 IBM
We cannot set the JMS adapter of SAP XI for conecting with IBM WebSphere Default JMS Provider. The Communication Channel has erroneous state (at runtime) and the Communication Channel Monitoring tool displays the error message as described below (under "Variant 1" and "Variant 2" sub-headings) depending on the settings performed.
For connecting, the following JMS-provider settings were used at IBM WebSphere side:
JMS Providers: Default Messaging Provider
Queue Connection Factories: name:QueueConnectionFactory, jndi:jms/QueueConnectionFactory, provider: Default Messaging Provider
Queues: name Queue, jndi: jms/Queue, provider: Default Messaging Provider
The XI communication channel (and associated JMS-adapter) was set as Variants 1 and 2 show. Settings for both cases and received error messages were the following:
<b>Variant 1.</b>
Adapter type: JMS
Type: Receiver
JMS Provider: Access JMS Provider with JNDI (Java Naming and Directory Interface)
JNDI Lookup Name of QueueConnectionFactory: jms/QueueConnectionFactory
JNDI Lookup Name of JMS Queue: jms/Queue
Name of JNDI Initial Context Factory: com.sap.engine.services.jndi.InitialContextFactoryImpl
JNDI Server Address: iiop://WEBSPHERE.HOST:2809/
As the result, the Communication Channel Monitoring displays that the channel has erroneous state and the following error message is written:
"Error during channel initialization; exception trace: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of jms/QueueConnectionFactory.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:649)"
<b>Variant 2</b>
The same settings as in Variant 1 above, were used and additionally the following settings were done:
- Name of JNDI Initial Context Factory: com.ibm.websphere.naming.WsnInitialContextFactory
- The archive aii_af_jmsproviderlib.sda containing libraries required by WsInitialContextFactory, was deployed to the SAP WebAS where the XI is running. Those libraries were taken from WebSphere Application Server Pluggable Application Client installation package (described in the article "WebSphere Application Server Pluggable Application Client" located at http://www-128.ibm.com/developerworks/websphere/library/techarticles/0409_bhogal/0409_bhogal.html)
- Also, as it is recommended in the referred article, the files required by IBM's iiop protocol (ibmext.jar ibmorb.jar ibmorbapi.jar) were put to the folder jre/lib/endorsed of the server(Sun JVM 1.4.2 is used by SAP WebAS / XI).
As the result, the Communication Channel Monitoring displays that the channel has erroneous state as well and the following error message is written:
"No adapter registered for this channel"
We have not found the recommended solution either in SDN forums or in Internet in general. Is it yet possible to connect SAP XI to IBM WebSphere Default JMS Provider having mentioned product versioning? If yes, what settings have to be performed?IBM Websphere Default JMS Provider which is installed alongwith the application server is nothing but a scaled down version of the IBM WebSphere MQSeries. you should be able to connect to it with the same settings that can be used for a separate MQSeries server connectivity from XI.
-
Getting error to access the JMS resouce.
I have confabulated 4 managed servers (des1, des2,des3 and des4) with JMS servers in a cluster on WebLogic 9.2. The servers des1 and des2 are located on same host of admin server installed(e.g. the hostname is adminhost). The servers des3 and des4 are located on anther host (remotehost). I have confabulated the JMS Connection Factory and Uniform Distributed Topic and target them to the cluster by using a subdeployment. I started the admin server on adminhost:7001.
I set the JMS provider URL to t3://adminhost:5010,adminhost:5020,remotehost:5010,remotehost:5020 in my java code to look up my JMS topic.
I can get the JMS topic from the adminhost's servers (des1 and des2). But on the remote host, if I don't start adminhost:5010, the server will get got error when try to get the JMS topic.
javax.naming.NameNotFoundException: While trying to lookup 'peoplesoft.crm.omk.jms.omkBroadcastTopic'
didn't find subcontext 'peoplesoft'. Resolved ''; remaining name 'peoplesoft/crm/omk/jms/omkBroadcastTopic'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
The remote server will only can get the JMS topic when the adminhost:5010 is up and running, which is the first one listed in the JMS provider URL.
Can any one give me the idea that:
Q1: Why only the admin server's managed servers can access the JMS topic?(because the des2 does not rely on if the server on adminhost:5010 running).
Is there any way I can make it work on remote host?
Q2: Why only the first server is recognized in the JMS provider URL?
Q3: Why the JSM provider is singleton fail point?
Thank you in advance!
Lucy
Edited by: user710140 on Feb 20, 2009 3:27 PMHere are my config.xml and jms.xml. Thank you for help!
config.xml
<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://www.bea.com/ns/weblogic/920/domain" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90/security/xacml http://www.bea.com/ns/weblogic/90/security/xacml.xsd http://www.bea.com/ns/weblogic/90/security http://www.bea.com/ns/weblogic/90/security.xsd http://www.bea.com/ns/weblogic/920/domain http://www.bea.com/ns/weblogic/920/domain.xsd http://www.bea.com/ns/weblogic/90/security/wls http://www.bea.com/ns/weblogic/90/security/wls.xsd">
<name>omk</name>
<domain-version>9.2.0.0</domain-version>
<security-configuration>
<name>omk</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xmlns:xac="http://www.bea.com/ns/weblogic/90/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer xmlns:xac="http://www.bea.com/ns/weblogic/90/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
</realm>
<default-realm>myrealm</default-realm>
<credential-encrypted>{3DES}DCrNeNp+kXrDhSu/xl1jSPlzzeCAUak9MRuA+ZvX8Ih/gYhSJAhEXNBeX92iiOAFcusvheIQMuMPAtQfFmG7UOSiq8Rm3q8s</credential-encrypted>
<node-manager-username>system</node-manager-username>
<node-manager-password-encrypted>{3DES}sDP3fr4NSp2l89H2BtwOoA==</node-manager-password-encrypted>
</security-configuration>
<server>
<name>crm9</name>
<ssl>
<name>crm9</name>
<enabled>true</enabled>
<hostname-verification-ignored>true</hostname-verification-ignored>
<listen-port>444</listen-port>
<two-way-ssl-enabled>false</two-way-ssl-enabled>
<server-private-key-alias>rfas010</server-private-key-alias>
<identity-and-trust-locations>KeyStores</identity-and-trust-locations>
</ssl>
<log>
<name>crm9</name>
<file-name>./logs/PIA_weblogic.log</file-name>
<log-file-severity>Info</log-file-severity>
</log>
<execute-queue>
<name>weblogic.kernel.Default</name>
<thread-count>50</thread-count>
</execute-queue>
<listen-port>7001</listen-port>
<web-server>
<name>crm9</name>
<web-server-log>
<name>crm9</name>
<file-name>./logs/PIA_access.log</file-name>
<logging-enabled>false</logging-enabled>
</web-server-log>
<https-keep-alive-secs>120</https-keep-alive-secs>
</web-server>
<iiop-enabled>false</iiop-enabled>
<listen-address></listen-address>
<staging-directory-name>./stage</staging-directory-name>
<upload-directory-name>./upload</upload-directory-name>
<staging-mode>nostage</staging-mode>
<graceful-shutdown-timeout>30</graceful-shutdown-timeout>
<msi-file-replication-enabled>true</msi-file-replication-enabled>
<custom-identity-key-store-file-name>keystore/pskey</custom-identity-key-store-file-name>
<custom-identity-key-store-type>JKS</custom-identity-key-store-type>
<custom-trust-key-store-file-name>keystore/pskey</custom-trust-key-store-file-name>
<custom-trust-key-store-type>JKS</custom-trust-key-store-type>
</server>
<server>
<name>proxyServer</name>
<ssl>
<enabled>false</enabled>
<listen-port>5011</listen-port>
</ssl>
<machine>rhas001</machine>
<listen-port>5010</listen-port>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address>10.138.120.154</listen-address>
</server>
<server>
<name>des1</name>
<ssl>
<enabled>false</enabled>
<listen-port>5011</listen-port>
</ssl>
<log>
<file-name>./logs/PIA_weblogic.log</file-name>
<log-file-severity>Info</log-file-severity>
</log>
<machine>rfas010</machine>
<listen-port>5010</listen-port>
<cluster>PsftOmkCluster</cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address>10.138.121.100</listen-address>
<server-start>
<class-path>D:/PT849/webserv/omk/applications/crm/com.peoplesoft.crm.omk.jar;D:/PT849/webserv/omk/applications/crm/commons-fileupload-1.0.jar;D:/PT849/webserv/omk/applications/crm/commons-logging.jar;D:/PT849/webserv/omk/applications/crm/commons-net-1.2.2.jar;D:/PT849/webserv/omk/applications/crm/toplink.jar;D:/PT849/webserv/omk/applications/crm/xercesImpl.jar;D:/PT849/webserv/omk/applications/crm/xml-apis.jar;D:/PT849/webserv/omk/applications/crm/xmlparserv2.jar;D:/PT849/webserv/omk/applications/crm/xalan.jar;D:/PT849/webserv/omk/applications/crm/psjoa.jar;D:/PT849/webserv/omk/applications/crm/ptib.jar;D:/PT849/webserv/omk/lib/pluto-1.0.1.jar;D:/PT849/webserv/omk/lib/portlet-api-1.0.jar;D:/PT849/webserv/omk/lib/ps_patch.jar;D:/PT849/webserv/omk/lib/xerces.jar;C:/bea/weblogic92/platform/lib/p13n/p13n-schemas.jar;C:/bea/weblogic92/platform/lib/p13n/p13n_common.jar;C:/bea/weblogic92/platform/lib/p13n/p13n_system.jar;C:/bea/weblogic92/platform/lib/wlp/netuix_common.jar;C:/bea/weblogic92/platform/lib/wlp/netuix_schemas.jar;C:/bea/weblogic92/platform/lib/wlp/netuix_system.jar;C:/bea/weblogic92/platform/lib/wlp/wsrp-common.jar;c:/bea/JROCKI~1/jre/lib/tools.jar;C:/bea/weblogic92/server/lib/weblogic_sp.jar;C:/bea/weblogic92/server/lib/weblogic.jar;D:/PT849/webserv/omk/applications/crm/ojdbc14.jar</class-path>
<arguments>-server -Xms256m -Xmx512m -XX:MaxPermSize=128m -Dps_home=D:/PT849 -Dps_vault=D:/PT849/secvault/psvault -Djava.util.logging.config.file=D:/PT849/webserv/omk/applications/peoplesoft/logging.properties -Dtoplink.xml.platform=oracle.toplink.platform.xml.jaxp.JAXPPlatform -Djavax.net.ssl.trustStore=D:/PT849/webserv/omk/keystore/pskey -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger</arguments>
<password-encrypted>{3DES}HbT3X8jahd4=</password-encrypted>
</server-start>
<jta-migratable-target>
<user-preferred-server>des1</user-preferred-server>
<cluster>PsftOmkCluster</cluster>
</jta-migratable-target>
</server>
<server>
<name>des2</name>
<ssl>
<enabled>false</enabled>
<listen-port>5021</listen-port>
</ssl>
<log>
<file-name>./logs/PIA_weblogic.log</file-name>
<log-file-severity>Info</log-file-severity>
</log>
<machine>rfas010</machine>
<listen-port>5020</listen-port>
<cluster>PsftOmkCluster</cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address>10.138.121.100</listen-address>
<server-start>
<class-path>D:/PT849/webserv/omk/applications/crm/com.peoplesoft.crm.omk.jar;D:/PT849/webserv/omk/applications/crm/commons-fileupload-1.0.jar;D:/PT849/webserv/omk/applications/crm/commons-logging.jar;D:/PT849/webserv/omk/applications/crm/commons-net-1.2.2.jar;D:/PT849/webserv/omk/applications/crm/toplink.jar;D:/PT849/webserv/omk/applications/crm/xercesImpl.jar;D:/PT849/webserv/omk/applications/crm/xml-apis.jar;D:/PT849/webserv/omk/applications/crm/xmlparserv2.jar;D:/PT849/webserv/omk/applications/crm/xalan.jar;D:/PT849/webserv/omk/applications/crm/psjoa.jar;D:/PT849/webserv/omk/applications/crm/ptib.jar;D:/PT849/webserv/omk/lib/pluto-1.0.1.jar;D:/PT849/webserv/omk/lib/portlet-api-1.0.jar;D:/PT849/webserv/omk/lib/ps_patch.jar;D:/PT849/webserv/omk/lib/xerces.jar;C:/bea/weblogic92/platform/lib/p13n/p13n-schemas.jar;C:/bea/weblogic92/platform/lib/p13n/p13n_common.jar;C:/bea/weblogic92/platform/lib/p13n/p13n_system.jar;C:/bea/weblogic92/platform/lib/wlp/netuix_common.jar;C:/bea/weblogic92/platform/lib/wlp/netuix_schemas.jar;C:/bea/weblogic92/platform/lib/wlp/netuix_system.jar;C:/bea/weblogic92/platform/lib/wlp/wsrp-common.jar;c:/bea/JROCKI~1/jre/lib/tools.jar;C:/bea/weblogic92/server/lib/weblogic_sp.jar;C:/bea/weblogic92/server/lib/weblogic.jar;D:/PT849/webserv/omk/applications/crm/ojdbc14.jar</class-path>
<arguments>-server -Xms256m -Xmx512m -XX:MaxPermSize=128m -Dps_home=D:/PT849 -Dps_vault=D:/PT849/secvault/psvault -Djava.util.logging.config.file=D:/PT849/webserv/omk/applications/peoplesoft/logging.properties -Dtoplink.xml.platform=oracle.toplink.platform.xml.jaxp.JAXPPlatform -Djavax.net.ssl.trustStore=D:/PT849/webserv/omk/keystore/pskey -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger</arguments>
<password-encrypted>{3DES}HbT3X8jahd4=</password-encrypted>
</server-start>
<jta-migratable-target>
<user-preferred-server>des2</user-preferred-server>
<cluster>PsftOmkCluster</cluster>
</jta-migratable-target>
</server>
<server>
<name>des3</name>
<ssl>
<enabled>false</enabled>
<listen-port>5011</listen-port>
</ssl>
<log>
<file-name>./logs/PIA_weblogic.log</file-name>
<log-file-severity>Info</log-file-severity>
</log>
<machine>rtas043</machine>
<listen-port>5010</listen-port>
<cluster>PsftOmkCluster</cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address>10.138.123.106</listen-address>
<server-start>
<class-path>D:/PT849/webserv/omk/applications/crm/com.peoplesoft.crm.omk.jar;D:/PT849/webserv/omk/applications/crm/commons-fileupload-1.0.jar;D:/PT849/webserv/omk/applications/crm/commons-logging.jar;D:/PT849/webserv/omk/applications/crm/commons-net-1.2.2.jar;D:/PT849/webserv/omk/applications/crm/toplink.jar;D:/PT849/webserv/omk/applications/crm/xercesImpl.jar;D:/PT849/webserv/omk/applications/crm/xml-apis.jar;D:/PT849/webserv/omk/applications/crm/xmlparserv2.jar;D:/PT849/webserv/omk/applications/crm/xalan.jar;D:/PT849/webserv/omk/applications/crm/psjoa.jar;D:/PT849/webserv/omk/applications/crm/ptib.jar;D:/PT849/webserv/omk/lib/pluto-1.0.1.jar;D:/PT849/webserv/omk/lib/portlet-api-1.0.jar;D:/PT849/webserv/omk/lib/ps_patch.jar;D:/PT849/webserv/omk/lib/xerces.jar;C:/bea/weblogic92/platform/lib/p13n/p13n-schemas.jar;C:/bea/weblogic92/platform/lib/p13n/p13n_common.jar;C:/bea/weblogic92/platform/lib/p13n/p13n_system.jar;C:/bea/weblogic92/platform/lib/wlp/netuix_common.jar;C:/bea/weblogic92/platform/lib/wlp/netuix_schemas.jar;C:/bea/weblogic92/platform/lib/wlp/netuix_system.jar;C:/bea/weblogic92/platform/lib/wlp/wsrp-common.jar;c:/bea/JROCKI~1/jre/lib/tools.jar;C:/bea/weblogic92/server/lib/weblogic_sp.jar;C:/bea/weblogic92/server/lib/weblogic.jar;D:/PT849/webserv/omk/applications/crm/ojdbc14.jar</class-path>
<arguments>-server -Xms256m -Xmx512m -XX:MaxPermSize=128m -Dps_home=D:/PT849 -Dps_vault=D:/PT849/secvault/psvault -Djava.util.logging.config.file=D:/PT849/webserv/omk/applications/peoplesoft/logging.properties -Dtoplink.xml.platform=oracle.toplink.platform.xml.jaxp.JAXPPlatform -Djavax.net.ssl.trustStore=D:/PT849/webserv/omk/keystore/pskey -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger</arguments>
<password-encrypted>{3DES}HbT3X8jahd4=</password-encrypted>
</server-start>
<jta-migratable-target>
<user-preferred-server>des3</user-preferred-server>
<cluster>PsftOmkCluster</cluster>
</jta-migratable-target>
</server>
<server>
<name>des4</name>
<ssl>
<enabled>false</enabled>
<listen-port>5021</listen-port>
</ssl>
<log>
<file-name>./logs/PIA_weblogic.log</file-name>
<log-file-severity>Info</log-file-severity>
</log>
<machine>rtas043</machine>
<listen-port>5020</listen-port>
<cluster>PsftOmkCluster</cluster>
<web-server>
<web-server-log>
<number-of-files-limited>false</number-of-files-limited>
</web-server-log>
</web-server>
<listen-address>10.138.123.106</listen-address>
<server-start>
<class-path>D:/PT849/webserv/omk/applications/crm/com.peoplesoft.crm.omk.jar;D:/PT849/webserv/omk/applications/crm/commons-fileupload-1.0.jar;D:/PT849/webserv/omk/applications/crm/commons-logging.jar;D:/PT849/webserv/omk/applications/crm/commons-net-1.2.2.jar;D:/PT849/webserv/omk/applications/crm/toplink.jar;D:/PT849/webserv/omk/applications/crm/xercesImpl.jar;D:/PT849/webserv/omk/applications/crm/xml-apis.jar;D:/PT849/webserv/omk/applications/crm/xmlparserv2.jar;D:/PT849/webserv/omk/applications/crm/xalan.jar;D:/PT849/webserv/omk/applications/crm/psjoa.jar;D:/PT849/webserv/omk/applications/crm/ptib.jar;D:/PT849/webserv/omk/lib/pluto-1.0.1.jar;D:/PT849/webserv/omk/lib/portlet-api-1.0.jar;D:/PT849/webserv/omk/lib/ps_patch.jar;D:/PT849/webserv/omk/lib/xerces.jar;C:/bea/weblogic92/platform/lib/p13n/p13n-schemas.jar;C:/bea/weblogic92/platform/lib/p13n/p13n_common.jar;C:/bea/weblogic92/platform/lib/p13n/p13n_system.jar;C:/bea/weblogic92/platform/lib/wlp/netuix_common.jar;C:/bea/weblogic92/platform/lib/wlp/netuix_schemas.jar;C:/bea/weblogic92/platform/lib/wlp/netuix_system.jar;C:/bea/weblogic92/platform/lib/wlp/wsrp-common.jar;c:/bea/JROCKI~1/jre/lib/tools.jar;C:/bea/weblogic92/server/lib/weblogic_sp.jar;C:/bea/weblogic92/server/lib/weblogic.jar;D:/PT849/webserv/omk/applications/crm/ojdbc14.jar</class-path>
<arguments>-server -Xms256m -Xmx512m -XX:MaxPermSize=128m -Dps_home=D:/PT849 -Dps_vault=D:/PT849/secvault/psvault -Djava.util.logging.config.file=D:/PT849/webserv/omk/applications/peoplesoft/logging.properties -Dtoplink.xml.platform=oracle.toplink.platform.xml.jaxp.JAXPPlatform -Djavax.net.ssl.trustStore=D:/PT849/webserv/omk/keystore/pskey -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger</arguments>
<password-encrypted>{3DES}HbT3X8jahd4=</password-encrypted>
</server-start>
<jta-migratable-target>
<user-preferred-server>des4</user-preferred-server>
<cluster>PsftOmkCluster</cluster>
</jta-migratable-target>
</server>
<cluster>
<name>PsftOmkCluster</name>
<multicast-address>239.192.0.0</multicast-address>
<multicast-port>7009</multicast-port>
<multicast-ttl>2</multicast-ttl>
<number-of-servers-in-cluster-address>4</number-of-servers-in-cluster-address>
</cluster>
<embedded-ldap>
<name>omk</name>
<credential-encrypted>{3DES}6Sr2wTwijurtQum4aELROj7jVGCnAucX5/41CQo4NNw=</credential-encrypted>
</embedded-ldap>
<configuration-version>9.2.0.0</configuration-version>
<app-deployment>
<name>crm9</name>
<target>PsftOmkCluster</target>
<module-type>ear</module-type>
<source-path>applications/crm9</source-path>
<sub-deployment>
<name>/DCS</name>
<target>PsftOmkCluster</target>
</sub-deployment>
<deployment-order>1</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>proxyServer</name>
<target>proxyServer</target>
<module-type>war</module-type>
<source-path>C:\Temp\wlst\proxyApp.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<app-deployment>
<name>wlnav</name>
<target>crm9</target>
<module-type>war</module-type>
<source-path>D:\lucy\wlnav.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>stage</staging-mode>
</app-deployment>
<machine>
<name>rhas001</name>
<node-manager>
<nm-type>SSL</nm-type>
<listen-address>rhas001.us.oracle.com</listen-address>
<listen-port>5556</listen-port>
</node-manager>
</machine>
<machine>
<name>rfas010</name>
<node-manager>
<nm-type>SSL</nm-type>
<listen-address>rfas010.us.oracle.com</listen-address>
<listen-port>5556</listen-port>
</node-manager>
</machine>
<machine>
<name>rtas043</name>
<node-manager>
<nm-type>SSL</nm-type>
<listen-address>rtas043.us.oracle.com</listen-address>
<listen-port>5556</listen-port>
</node-manager>
</machine>
<jms-server>
<name>PsftOmkJMSServer1</name>
<target>des1</target>
</jms-server>
<jms-server>
<name>PsftOmkJMSServer2</name>
<target>des2</target>
</jms-server>
<jms-server>
<name>PsftOmkJMSServer3</name>
<target>des3</target>
</jms-server>
<jms-server>
<name>PsftOmkJMSServer4</name>
<target>des4</target>
</jms-server>
<migratable-target>
<name>des1 (migratable)</name>
<notes>This is a system generated default migratable target for a server. Do not delete manually.</notes>
<user-preferred-server>des1</user-preferred-server>
<cluster>PsftOmkCluster</cluster>
</migratable-target>
<migratable-target>
<name>des2 (migratable)</name>
<notes>This is a system generated default migratable target for a server. Do not delete manually.</notes>
<user-preferred-server>des2</user-preferred-server>
<cluster>PsftOmkCluster</cluster>
</migratable-target>
<migratable-target>
<name>des3 (migratable)</name>
<notes>This is a system generated default migratable target for a server. Do not delete manually.</notes>
<user-preferred-server>des3</user-preferred-server>
<cluster>PsftOmkCluster</cluster>
</migratable-target>
<migratable-target>
<name>des4 (migratable)</name>
<notes>This is a system generated default migratable target for a server. Do not delete manually.</notes>
<user-preferred-server>des4</user-preferred-server>
<cluster>PsftOmkCluster</cluster>
</migratable-target>
<jms-system-resource>
<name>PsftOmkJMSModule</name>
<target>PsftOmkCluster</target>
<sub-deployment>
<name>PsftOmkClusterSubdeployment</name>
<target>PsftOmkCluster</target>
</sub-deployment>
<descriptor-file-name>jms/psftomkjmsmodule-jms.xml</descriptor-file-name>
</jms-system-resource>
<admin-server-name>crm9</admin-server-name>
</domain>
jms
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-jms xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/920 http://www.bea.com/ns/weblogic/920.xsd">
<connection-factory name="omkBroadcaster">
<sub-deployment-name>PsftOmkClusterSubdeployment</sub-deployment-name>
<jndi-name>jms.connection.omkConFactory</jndi-name>
<load-balancing-params>
<server-affinity-enabled>false</server-affinity-enabled>
</load-balancing-params>
</connection-factory>
<uniform-distributed-topic name="omkBroadcastTopic">
<sub-deployment-name>PsftOmkClusterSubdeployment</sub-deployment-name>
<jndi-name>peoplesoft.crm.omk.jms.omkBroadcastTopic</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
</uniform-distributed-topic>
</weblogic-jms>
Edited by: user710140 on Feb 23, 2009 8:54 AM
Maybe you are looking for
-
Pearl 8220 external display inop...
I purchased an unlocked version of this phone on amazon. It was used however its in almost new cosmetic condition. All of the functions seem to work properly except the external display. Is there a common problem and fix? the phone seems to be a
-
I want to add some predicate in select clause. Alike we can add some predicate in where close using FGAC. Is it possible in oracle ? I want to retrieve some more columns in result. It doesn't matter if those columns are there in select clause or not
-
Hi, I was watching a normal .mp4 video in quicktime and I wanted to stop playback and stop Quicktime, so I clicked the red X to close the window. When I did that, Quicktime crashed and didn't respond for about 5 seconds, quit, and I got a crash repor
-
Devices button missing in Windows iTunes 11.1.3
There is no Devices button in iTunes in the upper right. When i plug in my iPhone, nothing happens except iTunes-wise (I get a prompt on the iPhone asking if I want to trust the computer and I click Trust and nothing happens; Windows asks me to defin
-
Hi all, Can any send me the piece of code to use any of the following FM to maintain source list ME01 ME_MAINTAIN_SOURCE_LIST ME_POST_SOURCE_LIST ME_GENERATE_SOURCE_LIST Thanks