JMS in SLD

Hi!
Actually this topic is similar to JCo destination/ SLD configuration/ message server GRANT POINTS! where the problem remains unsolved.
So, the question is HOW to make JMS server to appear in step 4.2 of creating JCO connection
(http://host:port/webdynpro/welcome/Welcome.jsp -> Content Admin ->Local->MyProject->MyModel->JCO Connections)
Perhaps it's something to do with SLD...
In SLD I see that I have my technical system "J2E on myhost"
I have no JCo Destinations in "J2E on myhost" Should I Click "Add... "??
And what to pass as parameters for follows:
Name:
Web AS ABAP:
Message Server:
Logon Group:   ????????
Logon Client:   ?????????
Logon Language:
Description:
Any Ideas?
Thanks in advance

Hi Kartikeya,
What you have done is right....
if required you can refer to the below blogs
http://help.sap.com/saphelp_nw04/helpdata/en/f4/b028723570466c8182628dfe479a15/frameset.htm
How to Correlate JMS
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5059f110-0d01-0010-7c8b-fdc983be70c0
JMS Sender Adapter handling too short lines
The specified item was not found.
An approach to handle total record counts in IDOC to JMS scenarios
An approach to handle total record counts in IDOC to JMS scenarios
how to install and configure external drivers for JDBC and JMS adapters
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f04ce027-934d-2a10-5a8f-fa0b1ed4d88f
Thanks,
Madhu

Similar Messages

JMS to File

Hi
I have gone through all the previous posts on this topic. But I am still not clear. Can anyone give me the step by step procedure for JMS to file scenario?

Hi Arthi,
I configured similar kind of scenario in my project.
Here JMS is sender, File is receiver. here mq i used is Webshpere of JMS complaint
SLD
one third party business system would be enough for this scenario.
IR
1. Create a datatype similar to the structure of the message that is residing in WebsphereMQ
2. Create messagetype (one datatype, message type would be enough)
3. create two interfaces, outbound for jms and inbound for file
4. create message mapping and interface mapping.
ID
1. Import BS and create 2 comm channels
2. one jms sender, one file receiver
3. in jms sender, select WebsphereMQ( select the appropriate mq vendor)
defualt values appear for queue connectionfactory and and queue class
give ip address of the system on which MQ is installed, its port by default it is 1414, give queue manager name, channel name, and queue name. Remember all the characters shuld be in upper case only. select transport protocol as tcp/ip and jms complaint. give the userid and password of the system on which this MQ is installed. all these details u can get from MQ team.
4. create file receiver com.channel
5. remaining steps like sender, receiver agreement and interface, reciever determination can be created.
let me know if you have any doubts in this.
Regards,
Ravi.

JMS error while configuring SLD

HI folks,
I'm, encountering a tricky problem while connecting the SLD to the SolMan - running on the same host.
During making all neccessary steps it was no longer possible to log on to the
J2ee-Engine by /nwa or whatever application.
It just shows User locked or ONKNOWN ERRR
We unlocked the J2ee_admin again (strage, because the cause in Configtool was "locked after 0 unsuccessfull logins" weired! )
Then unset again the Superadmin, restartet the server... and again:
Application cannot be started.
Details: com.sap.engine.services.deploy.container.ExceptionInfo: JMS error.
Back to Superadmin Mode, Unlocking J2ee_admin, starting application manually in this mode, it comes up - I can see a loginscreen again but of course cannot login while superadmin mode is active...
After restarting cluster... same effect.
It seems, that the JMS cannot start due to locked User J2ee_admin and afterwards no other application is able to run.
Does anybody know, why this User J2ee_admin might be locked just before the JMS Service is started ?
Many many thanks in advance for any hint. Struggling since 2 days with this issue.
Nicolas

Problem is solved... Logging in to Abap Part in UME-Linked CLient 001 and unlocking j2ee_admin did what VA was not able to...

Buttons not enabling for JCO Creation in SLD

Hi Experts,
When i logged in into my Webdynpro Content Administrator with administrative rights, all the button like Create JCo Destination, Maintain JCo Destination and Start assigned SLD are getting disabled expect Check SLD Connection Button.
Moreover, displaying a message : "Connection to System Landscape Directory (SLD) could not be opended successfully." at the bottom of the screen.
When i click on the Check SLD Connection Button and then Test Connection, it gives again the same message i.e "Connection to System Landscape Directory (SLD) could not be opended successfully."
Now, When i click on the Check SLD Connection Button and then Start SLD, SLD server is staring and running.
Another thing is, When i am starting my sld server from logging in into http://<hostname>:<port>/sld, SERVER status is running. I stopped it and again started, then it is starting, but giving an error message as:
"Failed to send start signal for complete cluster, SLD may still be stopped on other cluster nodes."
When saving any parameters like profile information, it is not saving and saying error as:"
Cannot save profile settings CIM_ERR_FAILED: Failed to initialize cluster notification sender."
My setting are correct in SLD Data Supplier in Visual Administrator. I had filled the host/port/user/password information for both "HTTP Settings" and "CIM Client Generation Settings".
It went worked well earlier, i come across this problem recently with my sld.
Another thing that i noticed is when i click on the "CIMClient Test" button, its getting an error message saying "Failed to Generate and Test CIMOMClient Object". But, ealier it came as successfull.
I have full authorization to use admin tools.
What might be the problem.
any help must be appreciated.
regards
sunil kumar

Hi Sunil,
We just had this issue couple of days before, this has to do with the JMS Provider Authorization. We did the following steps to solve our issue:
I. Default security configuration of JMS resources is in place (this is by far the most common scenario) and named anonymous users have been created.
Change the mapping of the "clients" jms role as follows:
1. Start the Visual Admin
2. Browse the tree in the left pane
<SID> -> Server 0 -> Services -> Security Provider
3. The "Policy Configurations" tab should be selected by default on the right hand side
4. Select the "service.jms.default.authorization" node from the "Components" list (should be the nineth entry from the top down)
5. Select the "Security Roles" tab
6. Select the "clients" node from the security roles list
7. You should see on the right hand side "Security Roles" list in which the "guests" node is marked
8. Switch to edit mode by pressing the change button on top (pencil icon). The "Modify" button should now become active
9. Press the "Modify" button
10.Select the "all" entry from the "Security Roles" list. The "Groups" pane should show one entry named "Everyone"
11. Press the "Save" button
12. Restart the cluster so that JMS and applications using it can reliably reinitialize.
Check
Note 971249 - JMSServerSecurityException thrown accessing JMS resources
for more details.
Hope this helps!
Regards,
Preetha Rethinam

JMS adapter does not recover from error

Hello everyone,
We are noticing some strange behavior with the JMS adapter, and would like your help. We have messages coming into XI from WebSphere MQ. We have configured a Sender Comm channel (MQ_SENDER) with the appropriate JMS adapter, with a specified queue name (TEST.Q) . We have installed the appropriate MQ-JMS libraries for v6.0.
Here's the problem scenario... initially the application sending the messages to the specified queue was putting an incorrectly formatted MQRFH2 structure in the message. Predictably, this caused our comm channel to fail, and it shows up on the adapter monitor in the failed state with the message "MQJMS1050: The MQRFH2 header has an incorrect format Code: MQJMS1050". This in itself is not a problem, we realized that the application was sending a malformed message. The problem occurs when we fixed the sending application to completely strip out the MQRFH2 header altogether. When the new message is sent, the comm channel seems "stuck" on the previous error, and does not even pick up the new message from the queue. The adapter monitor continues to show the same error for the comm channel. Now when we modified the comm channel to read from a DIFFERENT queue (TEST2.Q) , the comm channel got out of the error state and is able to successfully process new messages coming into that queue. However, when we revert the comm channel back to the original queue (TEST.Q) it reverts back to the original MQJMS1050 error, and does not pick up new messages on the queue.
Any assistance would be greatly appreciated...

Hi,
1) Try to refresh the metadata
2) Check the Queue status
3) Once again check the Queue name. try to make the Sender JMS adapter inactive .save it..again make it active and save it and activate the object.
4) Refresh the Cache :
a)Start transaction SXI_CACHE.
b)From the context menu XI Runtime Cache select Start Complete Cache Refresh.
If you still face issue try this .
Many actions require to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.
However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason that we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.
To clear the SLD cache, from the Integration Builder main menu, choose Environment ® Delete Cache for SLD Data.
Once we have deleted the cache for SLD data, accessing objects in the SLD may take longer than usual initially.
Regards
Agasthuri Doss

Adapter monitoring with central SLD!

Hi ,
we have central SLD in our landscape(different host from XI server),and our basis guys installed PI7.0 SP12.And AE is local as I can see under Integration server.
I can see JPR in adapter in adapter monitoring.
I have question here!
should it needs to show all the list of adapters (FILE,JDBC,JMS,SOAP etc)in adapter monitoring in RWB?does it vary,if sld is central or local ?
what is the ideal way.
thank you,
babu

where the adapter engine should appear in RWB under integration server or under non central adapter engine if we have installed central AE and central SLD?
Under Component monitoring -> Integration server -> Adapter Engine
and it has show all the adapters when we install central AE and with central SLD when we furthur click the show all adapters?
As i mentioned above, u may view all the adapters after clicking
Adapter Engine -> Adapter Monitoring
or is it changed since PI 7.0 to cummunication channel monitoring and no adapter monitoring?
Yes. Now the monitoring of adapters r much intensively done by Communication Channel Monitoring
Regards,
Prateek

SLD server will not start

Hi, I am having an issue with my SLD server. The java will not start completely. This is the log i get:
If you have any clue that would be great.
thanks
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[./log/defaultTrace.trc]/>
<!PATTERN[defaultTrace.trc]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[Cp1252]/>
<!FILESET[0, 20, 10485760]/>
<!PREVIOUSFILE[defaultTrace.19.trc]/>
<!NEXTFILE[defaultTrace.1.trc]/>
<!LOGHEADER[END]/>
#1.5#000BCDEF4B75001E0000000100000B4400046A834059524E#1243011859688#com.sap.di.sdic.srv.java.SDICServiceFrame##com.sap.di.sdic.srv.java.SDICServiceFrame#######SAPEngine_System_Thread[impl:5]_70##0#0#Error#1#/Applications/SDIC/Service#Java###Failed to initialize the SDIC service. An unanticipated error has occured; Error description - #1#com.sap.di.sdic.exception.DiException: StateStore Initialization requires the values to be specified for the properties"sdic.state.store.storeManager" and "sdic.nwdiservers.admin.user"#
#1.5#000BCDEF4B75001E0000000300000B4400046A8340596B1D#1243011859688#com.sap.engine.core.service630.container.ServiceRunner##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_70##0#0#Error#1#/System/Server#Plain###Service tcdisdic~srv error. Nested exception is: com.sap.engine.frame.ServiceException: StateStore Initialization requires the values to be specified for the properties"sdic.state.store.storeManager" and "sdic.nwdiservers.admin.user"
 at com.sap.di.sdic.srv.java.SDICServiceFrame.start(SDICServiceFrame.java:162)
 at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
 at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
 at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
 at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.di.sdic.exception.DiException: StateStore Initialization requires the values to be specified for the properties"sdic.state.store.storeManager" and "sdic.nwdiservers.admin.user"
 at com.sap.di.sdic.srv.java.SDICServiceFrame.start(SDICServiceFrame.java:149)
 ... 5 more
Caused by: java.lang.Exception: StateStore Initialization requires the values to be specified for the properties"sdic.state.store.storeManager" and "sdic.nwdiservers.admin.user"
 ... 6 more
#1.5#000BCDEF4B7500260000000000000B4400046A8340A5D8ED#1243011864701#com.sap.caf.um.metadata.imp.MetaDataTools##com.sap.caf.um.metadata.imp.MetaDataTools.MetaDataTools()#######SAPEngine_System_Thread[impl:5]_54##0#0#Info#1#/System/Server#Plain###sap.com caf/um/metadata/imp MAIN_APL70VAL_C 963656#
#1.5#000BCDEF4B75002F0000000100000B4400046A8340D0C614#1243011867513#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.newProperties(int prcs, int conn)#######SAPEngine_System_Thread[impl:5]_35##0#0#Error#1#/System/Server#Java###enter newProperties()##
#1.5#000BCDEF4B75002F0000000300000B4400046A8340D702A6#1243011867919#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.init()#######SAPEngine_System_Thread[impl:5]_35##0#0#Error#1#/System/Server#Java###SNC properties not found ##
#1.5#000BCDEF4B7500300000000000000B4400046A8340F313F1#1243011869762#com.sap.caf.um.relgroups.imp.persistence.DataSource##com.sap.caf.um.relgroups.imp.persistence.DataSource.DataSource()#######SAPEngine_System_Thread[impl:5]_4##0#0#Info#1#/System/Server#Plain###sap.com caf/um/relgroups/imp MAIN_APL70VAL_C 963842#
#1.5#000BCDEF4B7500380000000100000B4400046A83412AA249#1243011873402#com.adobe.service.sap.configuration##com.adobe.service.sap.configuration#######OrderedChannel for service##0#0#Error#1#/System/Security#Plain###Error while reading trusted anchor configuration information:
com.sap.security.core.server.securestorage.exception.ObjectRetrievalException: Could not find clientID servicescomadobeDocumentServicesConfigurationAdobeConfigurationService~jar
 at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.getClientsStorageLocation(RemoteSecureStorageClientContextImpl.java:231)
 at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.retrieveObject(RemoteSecureStorageClientContextImpl.java:724)
 at com.adobe.service.sap.configuration.ConfigurationService.readXML(Unknown Source)
 at com.adobe.service.sap.configuration.ConfigurationService.<init>(Unknown Source)
 at com.adobe.service.sap.configuration.ServiceFrame.start(Unknown Source)
 at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
 at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
 at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
 at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
#1.5#000BCDEF4B7500380000000300000B4400046A83412AAC7B#1243011873402#com.adobe.service.sap.configuration##com.adobe.service.sap.configuration#######OrderedChannel for service##0#0#Error#1#/System/Security#Plain###Error while reading credential configuration information:
com.sap.security.core.server.securestorage.exception.ObjectRetrievalException: Could not find clientID servicescomadobeDocumentServicesConfigurationAdobeConfigurationService~jar
 at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.getClientsStorageLocation(RemoteSecureStorageClientContextImpl.java:231)
 at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.retrieveObject(RemoteSecureStorageClientContextImpl.java:724)
 at com.adobe.service.sap.configuration.ConfigurationService.readXML(Unknown Source)
 at com.adobe.service.sap.configuration.ConfigurationService.<init>(Unknown Source)
 at com.adobe.service.sap.configuration.ServiceFrame.start(Unknown Source)
 at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
 at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
 at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
 at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
#1.5#000BCDEF4B7500380000000500000B4400046A83412AB51D#1243011873402#com.adobe.service.sap.configuration##com.adobe.service.sap.configuration#######OrderedChannel for service##0#0#Error#1#/System/Security#Plain###Error while reading CRL configuration information:
com.sap.security.core.server.securestorage.exception.ObjectRetrievalException: Could not find clientID servicescomadobeDocumentServicesConfigurationAdobeConfigurationService~jar
 at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.getClientsStorageLocation(RemoteSecureStorageClientContextImpl.java:231)
 at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.retrieveObject(RemoteSecureStorageClientContextImpl.java:724)
 at com.adobe.service.sap.configuration.ConfigurationService.readXML(Unknown Source)
 at com.adobe.service.sap.configuration.ConfigurationService.<init>(Unknown Source)
 at com.adobe.service.sap.configuration.ServiceFrame.start(Unknown Source)
 at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
 at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
 at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
 at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
#1.5#000BCDEF4B7500380000000700000B4400046A83412ABDBE#1243011873402#com.adobe.service.sap.configuration##com.adobe.service.sap.configuration#######OrderedChannel for service##0#0#Error#1#/System/Security#Plain###Error while reading password configuration information:
com.sap.security.core.server.securestorage.exception.ObjectRetrievalException: Could not find clientID servicescomadobeDocumentServicesConfigurationAdobeConfigurationService~jar
 at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.getClientsStorageLocation(RemoteSecureStorageClientContextImpl.java:231)
 at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.retrieveObject(RemoteSecureStorageClientContextImpl.java:724)
 at com.adobe.service.sap.configuration.ConfigurationService.readXML(Unknown Source)
 at com.adobe.service.sap.configuration.ConfigurationService.<init>(Unknown Source)
 at com.adobe.service.sap.configuration.ServiceFrame.start(Unknown Source)
 at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
 at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
 at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
 at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Jean Seguin

Hi,
The user SAPJSF is not lock and here is the output of the Stdserver.out
stdout/stderr redirect
node name : server0
pid : 5800
system name : IS1
system nr. : 01
started at : Fri May 22 14:50:38 2009
Reserved 1610612736 (0x60000000) bytes before loading DLLs.
[Thr 5756] Fri May 22 14:50:39 2009
[Thr 5756] MtxInit: -2 0 0
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
SAP J2EE Engine Version 7.00 PatchLevel is starting...
Loading: LogManager ... 6420 ms.
Loading: PoolManager ... 0 ms.
Loading: ApplicationThreadManager ... 440 ms.
Loading: ThreadManager ... 76 ms.
Loading: IpVerificationManager ... 46 ms.
Loading: ClassLoaderManager ... 30 ms.
Loading: ClusterManager ... 638 ms.
Loading: LockingManager ... 227 ms.
Loading: ConfigurationManager ... 8136 ms.
Loading: LicensingManager ... 76 ms.
Loading: CacheManager ... 410 ms.
Loading: ServiceManager ...
Loading services.:
Service memory started. (45 ms).
Service cross started. (243 ms).
Service file started. (289 ms).
Service runtimeinfo started. (30 ms).
Service timeout started. (106 ms).
Service trex.service started. (106 ms).
Service p4 started. (744 ms).
Service classpath_resolver started. (30 ms).
Service userstore started. (243 ms).
Service jmx_notification started. (532 ms).
Service log_configurator started. (24331 ms).
Service locking started. (15 ms).
Service http started. (759 ms).
Service naming started. (1775 ms).
Service appclient started. (228 ms).
Service failover started. (213 ms).
Service jmsconnector started. (304 ms).
Service javamail started. (410 ms).
Service ts started. (349 ms).
Service licensing started. (30 ms).
Service connector started. (380 ms).
Service iiop started. (652 ms).
Service webservices started. (1700 ms).
Service deploy started. (31390 ms).
Service configuration started. (61 ms).
Service MigrationService started. (106 ms).
Service bimmrdeployer started. (30 ms).
Service dbpool started. (6041 ms).
Service com.sap.security.core.ume.service started. (7680 ms).
Service tcdisdic~srv started. (1776 ms).
Service security started. (4068 ms).
Service classload started. (228 ms).
Service applocking started. (228 ms).
Service shell started. (379 ms).
Service ejb started. (547 ms).
Service tceCATTPingservice started. (425 ms).
Service telnet started. (501 ms).
Service dsr started. (1062 ms).
Service servlet_jsp started. (1791 ms).
Service webdynpro started. (1426 ms).
Service cafummetadata~imp started. (2095 ms).
Service keystore started. (2474 ms).
Service ssl started. (15 ms).
Service cafruntimeconnectivity~impl started. (50818 ms).
Service jmx started. (3111 ms).
Service tcsecsecurestorage~service started. (1199 ms).
Service tcsecwssec~service started. (835 ms).
Service cafumrelgroups~imp started. (4099 ms).
Service CUL started. (2550 ms).
Service tcsecdestinations~service started. (2824 ms).
Service apptracing started. (1351 ms).
Service com.adobe~DataManagerService started. (3187 ms).
Service pmi started. (1138 ms).
Service tcsecvsi~service started. (1988 ms).
Service sld started. (5525 ms).
Service basicadmin started. (4568 ms).
Service com.adobe~DocumentServicesDestProtoService started. (1548 ms).
Service com.adobe~DocumentServicesBinaries2 started. (1624 ms).
Service com.adobe~DocumentServicesLicenseSupportService started. (1336 ms).
Service adminadapter started. (364 ms).
Service com.adobe~LicenseService started. (470 ms).
Service monitor started. (1564 ms).
Service com.adobe~DocumentServicesConfiguration started. (2762 ms).
Service com.adobe~TrustManagerService started. (182 ms).
Service com.adobe~PDFManipulation started. (4888 ms).
Service tc.CBS.Service started. (10564 ms).
Service com.adobe~FontManagerService started. (10049 ms).
Service com.sap.aii.af.cpa.svc started. (9821 ms).
Service com.sap.aii.af.security.service started. (31 ms).
Service tc.monitoring.logviewer started. (19216 ms).
Service com.sap.aii.af.svc started. (2808 ms).
Service com.sap.aii.af.ms.svc started. (1366 ms).
Service com.adobe~XMLFormService started. (6315 ms).
Service com.sap.aii.adapter.bc.svc started. (106 ms).
Service com.sap.aii.adapter.marketplace.svc started. (243 ms).
Service com.sap.aii.adapter.xi.svc started. (182 ms).
Service com.sap.aii.adapter.file.svc started. (304 ms).
Service com.sap.aii.adapter.jdbc.svc started. (288 ms).
Service com.sap.aii.adapter.rfc.svc started. (122 ms).
Service jms_provider started. (22373 ms).
Service com.sap.aii.adapter.mail.svc started. (1442 ms).
Service com.sap.aii.adapter.jms.svc started. (895 ms).
Service com.sap.aii.af.ispeak.svc started. (728 ms).
Service rfcengine started. (73524 ms).
ServiceManager started for 148445 ms.
Framework started for 166083 ms.
SAP J2EE Engine Version 7.00 PatchLevel is running!
PatchLevel October 23, 2006 07:41 GMT

XI 3.0 - How to increase performance using TibCo JMS Adapter...

Hi,
Does anyone have any idea if/which properties can be modified to improve the polling interval of the JMS adapter for Tibco?
Another forum message mentioned a method called setPollingInterval, but this only seems to relate to MQ series.
I have tried options like creating multiple communiction channels pointing to the same non-exclusive queue, increasing the server node count (this improves pickup, but reduces overall throughput as the SLD data is no longer buffered).
I have also tried the method called "setConnAttemptDelay" on the com.tibco.tibjms.TibjmsQueueConnectionFactory class but this did no seem to help.
Any suggestions please?
thanks
Brian

The answer is to either add additional J2EE server nodes to your PI/XI instance or add additional Business Services and configure addition Comms channels for these

Unable to create the JCO connections in webdypro (JAVA) No SLD Connection

HI All,
In webdynpro i am unable to create standard JCo connections. create Jco connections and Maintain Jco COnnections are disabled. when i click any of the standard content of the Jco connections it displays error message No sld check. But SLD is running fine. I have checked in Visual Admin there also SLD supplier is running fine.
But i am unable to create or maintain the Standard content of the JCo Destinations.
Thank You,
Mahesh C

Hi ,
I am having all admin rights. And also i have checked in Check SLD Connection. It showing the error connection to SLD Could not opened successfully. But SLD is running fine and i have checked in Visual admin SLD datasupplier is running fine.
When i check in the log of the SLD there it is showing
#2852 11/18/2008 18:27:18.265 [SAPEngine_Application_Thread[impl:3]_29] FATAL com.sap.lcr.cimsrv.CIMOMServlet: SLD initialization failure, can not set up cluster-wide event notification. Please check your JMS provider for errors.
Thrown:
com.sap.sld.api.wbem.exception.CIMException: CIM_ERR_FAILED: Failed to initialize cluster notification. Please check your JNDI service and JMS provider for errors.
Is that i need to change the CIM content?
I could not able to get clue on this.
Thank You,
Mahesh C

Facing Problem in SLD(getting 500 INTERNAL SERVER ERROR IN PORTAL)

Dear All,
we had ESS application just few days back it went to Go live , very frequently we are facing the issue
Regards JCO 's , we are getting "500 Internal Server Error" in production Portal
After getting the error ,the " Maintained JCO's" and "Created JCO'S " are both are disabled
uder contenten administraton->webdynpro.
But the SDL is in active , we can able to open SLD url every thing is also fine
Technical system and every thing coming fine
we checked SLD User also in SLD User Administration , the SLD user is also there it is not unlocked
The problem is : if the problem is happend after restarting the server again it is coming properly
Again after some time it is getting same error ,whith out doing any thing also some times the problem is resolving automatically
we are not getting Root cause of this behaviour
In our client side SLD is centralized ,they are not maintain locally
If the SLD is Proble , the error has to come in Quality and Production also why bcz it is centralized
But Some times 500 ERROR IN Prodution and some times in Quality.
And some times the Portal is very slowly opening especially ESS application ,after restart happening it is some better
again it is getting down after some time
If it is NETWORK Iuuse or any firewall ect...in which way we can can with them and where
Guru's share your knowledge it's a very critical for me what are he possible ways...
Regards,
Giri

Here I am giving the LOG details which is available in SLD (J2EE) server
#2.0 #2012 03 03 14:24:57:513#+0530#Error#com.sap.aii.af.service.sld.SLDRegistrationJob#
#BC-XI-CON-AFW#com.sap.aii.af.lib#005056BB552201A70000000000000DF0#151402750000001894##com.sap.aii.af.service.sld.SLDRegistrationJob.SLDRegistrationJob.invoke()#Guest#0##1014F5C2650011E1B811005056BB5522#1014f5c2650011e1b811005056bb5522#1014f5c2650011e1b811005056bb5522#0#Application [17]#Plain##
SLD Registration Job: No access to SLD. Waiting for next retry. Error: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties)#
#2.0 #2012 03 03 14:26:06:739#+0530#Error#com.sap.nw.lm.aci.engine.base.sld.connection.AccSldConnector#
#BC-AC-7XX#sap.com/tc~lm~aci~engine~baselib~05#005056BB552201AB0000000100000DF0#151402750000008310#sap.com/tc~lm~aci~monitor~app#com.sap.nw.lm.aci.engine.base.sld.connection.AccSldConnector.getSldComputerSystemsForMonitoring(String)#Administrator#0#SAP J2EE Engine JTA Transaction : [9638fffffffe00fffffff85]#1014F5C2650011E1B811005056BB5522#1014f5c2650011e1b811005056bb5522#1014f5c2650011e1b811005056bb5522#0#Thread[Managed_Application_Thread_29,5,Managed_Application_Thread]#Java##
Unable to obtain Computer Systems, associated to NW Admin NWA_FOR_FirstLandScpSrvcName, from SLD. CIM_ERR_FAILED: No such instance: SAP_NWAdministrator.CreationClassName="SAP_NWAdministrator",Name="NWA_FOR_FirstLandScpSrvcName" [this message was repeated 9 times]
[EXCEPTION]
{0}#1#com.sap.sld.api.wbem.exception.CIMException: CIM_ERR_FAILED: No such instance: SAP_NWAdministrator.CreationClassName="SAP_NWAdministrator",Name="NWA_FOR_FirstLandScpSrvcName"
     at com.sap.sld.api.wbem.client.WBEMRequestSender.convertErrorResponse(WBEMRequestSender.java:127)
     at com.sap.sld.api.wbem.client.WBEMRequestSender.convertErrorResponse(WBEMRequestSender.java:48)
     at com.sap.sld.api.wbem.client.WBEMRequestSender.send(WBEMRequestSender.java:272)
     at com.sap.sld.api.wbem.client.WBEMRemoteClient.sendAndCast(WBEMRemoteClient.java:936)
     at com.sap.sld.api.wbem.client.WBEMRemoteClient.associatorNamesImpl(WBEMRemoteClient.java:507)
     at com.sap.sld.api.wbem.client.WBEMAbstractClient.associatorNames(WBEMAbstractClient.java:544)
     at com.sap.nw.lm.aci.engine.base.sld.connection.AccSldConnector.getSldComputerSystemsForMonitoring(AccSldConnector.java:3731)
     at com.sap.nw.lm.aci.monitor.fetch.util.MonitoringSldAdapter.getAllHostnames(MonitoringSldAdapter.java:277)
     at com.sap.nw.lm.aci.monitor.fetch.manager.PrefetchPackageUtil.repackageCs(PrefetchPackageUtil.java:71)
     at com.sap.nw.lm.aci.monitor.fetch.manager.PrefetchPackageUtil.repackageAll(PrefetchPackageUtil.java:58)
     at com.sap.nw.lm.aci.monitor.fetch.manager.FetchManager.repackageIfRequired(FetchManager.java:1046)
     at com.sap.nw.lm.aci.monitor.fetch.manager.FetchManager.run(FetchManager.java:435)
     at com.sap.nw.lm.aci.monitor.fetch.job.FetchJobBean.onJob(FetchJobBean.java:67)
     at com.sap.engine.services.scheduler.runtime.mdb.MDBJobDelegateImpl$2.run(MDBJobDelegateImpl.java:233)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAs(Subject.java:396)
     at com.sap.engine.services.scheduler.runtime.mdb.MDBJobDelegateImpl.onMessage(MDBJobDelegateImpl.java:267)
     at com.sap.scheduler.runtime.mdb.MDBJobImplementation.onMessage(MDBJobImplementation.java:60)
     at sun.reflect.GeneratedMethodAccessor284.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MessageListenerType.invoke(Interceptors_MessageListenerType.java:110)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Lock.invoke(Interceptors_Lock.java:21)
     at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
     at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
     at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
     at com.sap.engine.services.ejb3.runtime.impl.MDBProxyInvocationHandler.invoke(MDBProxyInvocationHandler.java:77)
     at $Proxy1058.onMessage(Unknown Source)
     at com.sap.jms.resourceadapter.RaServerSession.internalOnMessage(RaServerSession.java:188)
     at com.sap.jms.resourceadapter.RaServerSession.onMessage(RaServerSession.java:330)
     at com.sap.jms.client.session.JMSSession.deliverMessage(JMSSession.java:805)
     at com.sap.jms.client.session.JMSSession.run(JMSSession.java:709)
     at com.sap.jms.resourceadapter.RaServerSession.run(RaServerSession.java:379)
     at com.sap.engine.services.connector.jca15.work.TaskImpl.run(TaskImpl.java:420)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
#2.0 #2012 03 03 14:26:57:526#+0530#Error#com.sap.aii.af.service.sld.SLDRegistrationJob#
#BC-XI-CON-AFW#com.sap.aii.af.lib#005056BB552201B00000000000000DF0#151402750000001894##com.sap.aii.af.service.sld.SLDRegistrationJob.SLDRegistrationJob.invoke()#Guest#0##1014F5C2650011E1B811005056BB5522#1014f5c2650011e1b811005056bb5522#1014f5c2650011e1b811005056bb5522#0#Application [6]#Plain##
SLD Registration Job: No access to SLD. Waiting for next retry. Error: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties)#
#2.0 #2012 03 03 14:28:57:522#+0530#Error#com.sap.aii.af.service.sld.SLDRegistrationJob#
#BC-XI-CON-AFW#com.sap.aii.af.lib#005056BB552201B70000000000000DF0#151402750000001894##com.sap.aii.af.service.sld.SLDRegistrationJob.SLDRegistrationJob.invoke()#Guest#0##1014F5C2650011E1B811005056BB5522#1014f5c2650011e1b811005056bb5522#1014f5c2650011e1b811005056bb5522#0#Application [5]#Plain##
SLD Registration Job: No access to SLD. Waiting for next retry. Error: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties)#
#2.0 #2012 03 03 14:30:57:519#+0530#Error#com.sap.aii.af.service.sld.SLDRegistrationJob#
#BC-XI-CON-AFW#com.sap.aii.af.lib#005056BB552201BE0000000000000DF0#151402750000001894##com.sap.aii.af.service.sld.SLDRegistrationJob.SLDRegistrationJob.invoke()#Guest#0##1014F5C2650011E1B811005056BB5522#1014f5c2650011e1b811005056bb5522#1014f5c2650011e1b811005056bb5522#0#Application [20]#Plain##
SLD Registration Job: No access to SLD. Waiting for next retry. Error: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties)#
Edited by: giriep on Mar 3, 2012 11:38 AM

SLD Server does not start

Hi,
I try to configure my local SLD. I created all the roles and groups mentioned in http://help.sap.com/saphelp_nw70/helpdata/EN/43/ce62c162cd0cd4e10000000a1553f7/content.htm. I put my Administrator User in all of the created groups. When entering the SLD I get told that the "SLD Server has stopped".
When I try to start the server it fails with some error messages. This is the first one:
#57 03/21/2008 18:00:32.360 [SAPEngine_Application_Thread[impl:3]_24] ERROR com.sap.lcr.cimsrv.ClusterNotificationSender$JMSSender: Failed to initialize cluster notification sender. Please check your JNDI service and JMS provider for errors.
Thrown:
javax.jms.JMSSecurityException: You do not have permissions: action produce and instance SLDClusterNotificationTopic.
at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:231)
at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2614)
at com.sap.jms.client.session.Session.createProducer(Session.java:2397)
at com.sap.jms.client.session.TopicSession.createPublisher(TopicSession.java:46)
at com.sap.lcr.cimsrv.ClusterNotificationSender$JMSSender.<init>(ClusterNotificationSender.java:97)
at com.sap.lcr.cimsrv.ClusterNotificationSender$JMSSender.<init>(ClusterNotificationSender.java:72)
at com.sap.lcr.cimsrv.ClusterNotificationSender.newInstance(ClusterNotificationSender.java:44)
at com.sap.lcr.cimsrv.RareClusterNotifications.send(RareClusterNotifications.java:28)
at com.sap.lcr.cimsrv.RareClusterNotifications.sendStartStopUpdate(RareClusterNotifications.java:56)
at com.sap.lcr.webui.CimIO.startCIMServer(CimIO.java:563)
at com.sap.lcr.webui.Admin.actionStartStop(Admin.java:855)
at com.sap.lcr.webui.Admin.doGet(Admin.java:190)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
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)
Maybe it is a problem with permissions. But I cannot find the action mentioned in the error message "action produce and instance SLDClusterNotificationTopic".
Any idea how I can solve this problem.
Thanks in advance.
Best,
Stephan

Hi,
Just a hint from the link you mentioned.
"If you want to set up SLD security for test purposes, you only have to map the LcrAdministrator role to the SAP_SLD_ADMINISTRATOR group and assign an administrator user to this group."
Did you add Administrator user to SAP_SLD_ADMINISTRATOR group mapped to LcrAdministrator role? If not, try it too.
Also check these blogs for configuring SLD.
Configuring SLD in Sneak Preview SAP NetWeaver '04 Sneak
Discovering SLD--PART 1
Discovering SLD-PART 2
Regards,
Harini S
Consider rewarding for helpful answers

JMS Configuration

Hi All,
I have configured the scenario to communicate with external JMS system.I have created the party and business service for the external JMS system. I used this business service and its communication channel for the configuration. I have not defined anything in SLD related to JMS system. Is it the right approach?
Thanks in Advance,
Kartikeya

Hi Kartikeya,
What you have done is right....
if required you can refer to the below blogs
http://help.sap.com/saphelp_nw04/helpdata/en/f4/b028723570466c8182628dfe479a15/frameset.htm
How to Correlate JMS
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5059f110-0d01-0010-7c8b-fdc983be70c0
JMS Sender Adapter handling too short lines
The specified item was not found.
An approach to handle total record counts in IDOC to JMS scenarios
An approach to handle total record counts in IDOC to JMS scenarios
how to install and configure external drivers for JDBC and JMS adapters
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f04ce027-934d-2a10-5a8f-fa0b1ed4d88f
Thanks,
Madhu

Deployment JMS-MQ driver crashes the PI repository and Directory

Hi Expert,
we have scenario ECC--> XI --> MQ. So we deployed the JMS driver for MQ 6.0 to PI 7.0, the jar files are like stated in SAP Note : 747601. However after we deployed the new aii_af_jmsproviderlib.sda, sxmb_sfr can NOT start the page successfully, we got error page like :Unable to start component REPOSITORY since unable to execute StartupCodeEntry class com.sap.aii.ibrep.server.applcomp.StartupCodeEntry. Therefor the ID and IR are not accessible any more. Anyone knows how this happens? Anyone has experience to deploy JMS MQ driver to PI 7.0?
Thanks
Jayson

Guys,
Any success????
I am working on PI 7.1. I m also facing same issue..... when I tried to upgrade SAP-XICONS and SAP_XIPCK component from SP 4.0 to 7.0.
In my case the SLD, RWB and NWA is working... but I am not able to access
http://pidev:50000/dir/start/index.jsp.
The error says:
Internal error: Unable to start component DIRECTORY_SERVER. Specified StartupCodeEntry class "com.sap.aii.ibdir.server.applcomp.StartupCodeEntry" does not exist
deatiled error ************************
Stacktrace
Thrown:
com.sap.aii.ib.core.applcomp.StartupException: Internal error: Unable to start component DIRECTORY_SERVER. Specified StartupCodeEntry class "com.sap.aii.ibdir.server.applcomp.StartupCodeEntry" does not exist
     at com.sap.aii.ib.core.applcomp.StartupException.newEntryClassNotFound(StartupException.java:78)
     at com.sap.aii.ib.core.applcomp.ExplicitApplicationComponentImpl.startup(ExplicitApplicationComponentImpl.java:101)
     at com.sap.aii.ib.core.applcomp.ExplicitApplicationComponents.startup(ExplicitApplicationComponents.java:438)
     at com.sap.aii.ib.core.applcomp.ApplicationComponent.startup(ApplicationComponent.java:203)
     at JEE_jsp_start_index_6931850_1232360340765_1232372432437._jspService(JEE_jsp_start_index_6931850_1232360340765_1232372432437.java:122)
     at com.sap.engine.services.servlets_jsp.lib.jspruntime.JspBase.service(JspBase.java:102)
     at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:433)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:240)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
     at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
     at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
     at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
     at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
     at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
     at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
     at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
     at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
     at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
     at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
     at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:295)
     at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
     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:152)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Initial Startup Exception
Internal error: Unable to start component DIRECTORY_SERVER. Specified StartupCodeEntry class "com.sap.aii.ibdir.server.applcomp.StartupCodeEntry" does not exist
Thrown:
com.sap.aii.ib.core.applcomp.StartupException: Internal error: Unable to start component DIRECTORY_SERVER. Specified StartupCodeEntry class "com.sap.aii.ibdir.server.applcomp.StartupCodeEntry" does not exist
     at com.sap.aii.ib.core.applcomp.StartupException.newEntryClassNotFound(StartupException.java:78)
     at com.sap.aii.ib.core.applcomp.ExplicitApplicationComponentImpl.startup(ExplicitApplicationComponentImpl.java:101)
     at com.sap.aii.ib.core.applcomp.ExplicitApplicationComponents.startup(ExplicitApplicationComponents.java:438)
     at com.sap.aii.ib.core.applcomp.ApplicationComponent.startup(ApplicationComponent.java:203)
     at com.sap.aii.ibdir.server.cache.monitoring.CacheMonitorServlet.startup(CacheMonitorServlet.java:104)
     at com.sap.aii.ibdir.server.cache.monitoring.CacheMonitorServlet.init(CacheMonitorServlet.java:45)
     at javax.servlet.GenericServlet.init(GenericServlet.java:241)
     at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:97)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAs(Subject.java:396)
     at com.sap.engine.services.servlets_jsp.server.application.WebComponents.addServlet(WebComponents.java:341)
     at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:849)
     at com.sap.engine.services.servlets_jsp.server.deploy.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:219)
     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:152)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Regards,
Siddhesh S.Tawate

Sap ecc(RFC) to Java application (jms) scenario in sap pi

Hi Team, How to configure SAP(ECC) to JMS scenario with steps.If have any documents please send me. I have urgent requirement please help me. Thanks in advance Regards.. Ravi

Hi,
For JMS no need to maintain any thing in SLD.Just create Communication component in ID.
When comes to sender RFC channel.
App server -- sender system hostname
App server gateway:sapgwSystemNo of sender system
Program ID :any meaning full name (make sure to maintain the same name in trfc created in your sender system)
Give log on details of ECC system.
Regards
Venkat

SLD : Failed to initialize cluster notification during SLD startup

hello,
We are using WAS 7.0.
While starting the SLD the server gives following error.
Failed to send start signal for complete cluster, SLD may still be stopped on other cluster nodes.
in the log of SLD following entries are there..
FATAL com.sap.lcr.cimsrv.CIMOMServlet: SLD initialization failure, can not set up cluster-wide event notification. Please check your JMS provider for errors.
3428858 11/22/2007 13:42:11.515 [SAPEngine_Application_Thread[impl:3]_70] FATAL com.sap.lcr.cimsrv.CIMOMServlet: SLD initialization failure, can not set up cluster-wide event notification. Please check your JMS provider for errors.
Thrown:
com.sap.sld.api.wbem.exception.CIMException: CIM_ERR_FAILED: Failed to initialize cluster notification. Please check your JNDI service and JMS provider for errors.
at com.sap.lcr.cimsrv.ClusterNotificationListener.<init>(ClusterNotificationListener.java:154)
at com.sap.lcr.cimsrv.ClusterNotificationListener.start(ClusterNotificationListener.java:69)
at com.sap.lcr.cimsrv.CIMOMServlet.init(CIMOMServlet.java:109)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.getServlet(WebComponents.java:339)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:354)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
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: javax.jms.JMSException:
at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:271)
at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2614)
at com.sap.jms.client.session.Session.createConsumer(Session.java:2173)
at com.sap.jms.client.session.TopicSession.createSubscriber(TopicSession.java:39)
at com.sap.lcr.cimsrv.ClusterNotificationListener.<init>(ClusterNotificationListener.java:142)
... 18 more
caused by:
javax.jms.JMSException:
at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:271)
at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2614)
at com.sap.jms.client.session.Session.createConsumer(Session.java:2173)
at com.sap.jms.client.session.TopicSession.createSubscriber(TopicSession.java:39)
at com.sap.lcr.cimsrv.ClusterNotificationListener.<init>(ClusterNotificationListener.java:142)
at com.sap.lcr.cimsrv.ClusterNotificationListener.start(ClusterNotificationListener.java:69)
at com.sap.lcr.cimsrv.CIMOMServlet.init(CIMOMServlet.java:109)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.getServlet(WebComponents.java:339)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:354)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
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)
Please help.
Thanks,
Manoj

Hi Pankaj,
The ABAP RFC is working fine but the JCo RFC is not there.
But in the create JCo connect button in Content Administration -->webdynpro.
Please suggest.
Thanks
Manoj

JMS in SLD

Similar Messages

Maybe you are looking for