Sld registration
Hi all,
after running note 764176 I can now only see my DEV and QA objects in my master SLD.
My PROD components (adapter engine, integration server etc.) are not self registrering in the Master SLD.
How could I make this happen? (I would like my master to have ALL the components, and then trasnport the PROD components to the my slave SLD)
Thanks!
UPDATE:
We were able to work through and
resolve the error we initially posted in this Thread. Now we run sldreg
and all looks good; however, we are seeing nothing in SLD (on our XI
System) even after stop/restart of SLD Server:
Steps for the Reconstruction
1. Generate SLD Configuration Files:
sldreg -usekeyfile -configure /usr/sap/TXD/TRX00/slddest.cfg
2. Copied files to Global SLD
/sapmnt/TXD/global
3. Run command to transfer data to SLD:
saposcol -b | sldreg -user <user acct> -pass <password> -host
<hostname> -port <port #> -datatrace -httptrace -
logfile /usr/sap/TXD/TRX00/sld_reg.log -stdin
Looks successful:
Thu Dec 27 20:31:06 2007 HTTP body length: 0 --- HTTP body: empty
Thu Dec 27 20:31:06 2007 Return code: 200 --- Return message: (OK)
Thu Dec 27 20:31:06 2007 HTTP response: Success. HTTP status code: 200
Thu Dec 27 20:31:06 2007 *** End SLD Registration ***
Thu Dec 27 20:31:06 2007 Data send status: true
However in SLD , under content maintenance selecting "All With
Instances" in the dropdown list and "Class" , no TREX Services showing.
And no technical system showing for TXD (TREX System)
Similar Messages
-
SLD registration for TREX not working...
SDN Members,
I am unable to register TREX in SLD. I have put in an OSS message; however, I have yet to receive a response back from SAP... So any help would be much appreciated.
Thanks,
-Patrick
Steps for the Reconstruction
1. Generate SLD Configuration file:
sldreg -configure /usr/sap/TXD/TRX85/slddest.cfg
2. Copy the SLD Config. File to the Global SLD Directory and run
command (to transfer data to SLD):
saposcol -b | sldreg -connectfile slddest.cfg -stdin -oldtransferdtd
Receive the following:
(hostnames, ip's, and ports altered to protect the innocent)
prtdiag can only be run in the global zone
Thu Dec 27 10:33:04 2007 SLD Registration Program [2.0] (May 8 2006) [None Unicode]
Thu Dec 27 10:33:04 2007 No XML data input file set. Will read input data from standard input.
Thu Dec 27 10:33:04 2007 Supplier Name: ComputerSystem / Supplier Version: 1.0 / Supplier Vendor: / CIM Model Version: 1.3.21
Thu Dec 27 10:33:04 2007 Group:
Thu Dec 27 10:33:04 2007 Group name system1
Thu Dec 27 10:33:04 2007 validateAttributes OK
Thu Dec 27 10:33:04 2007 Property Status
Thu Dec 27 10:33:04 2007 Value OK
Thu Dec 27 10:33:04 2007 Property NameFormat
Thu Dec 27 10:33:04 2007 Value IP
Thu Dec 27 10:33:04 2007 Property Caption
Thu Dec 27 10:33:04 2007 Value hostname01
Thu Dec 27 10:33:04 2007 Property Name
Thu Dec 27 10:33:04 2007 Value usahstxutxd01
Thu Dec 27 10:33:04 2007 Property IPAddress
Thu Dec 27 10:33:04 2007 Value X.X.X.X
Thu Dec 27 10:33:04 2007 Property OpSysReleaseName
Thu Dec 27 10:33:04 2007 Value SunOS
Thu Dec 27 10:33:04 2007 Property OpSysCategory
Thu Dec 27 10:33:04 2007 Value Solaris
Thu Dec 27 10:33:04 2007 Property VendorRelease
Thu Dec 27 10:33:04 2007 Value SunOS 5.10
Thu Dec 27 10:33:04 2007 Property CPUType
Thu Dec 27 10:33:04 2007 Value sun4v
Thu Dec 27 10:33:04 2007 Property MachineCategory
Thu Dec 27 10:33:04 2007 Value SPARC
Thu Dec 27 10:33:04 2007 Property OpSysBits
Thu Dec 27 10:33:04 2007 Value 64
Thu Dec 27 10:33:04 2007 Property NumberOfCPUs
Thu Dec 27 10:33:04 2007 Value 32
Thu Dec 27 10:33:04 2007 Property CPURate
Thu Dec 27 10:33:04 2007 Value 1200
Thu Dec 27 10:33:04 2007 Property PhysicalRAMInMB
Thu Dec 27 10:33:04 2007 Value 65528
Thu Dec 27 10:33:04 2007 Property VirtualRAMInMB
Thu Dec 27 10:33:04 2007 Value 87224
Thu Dec 27 10:33:04 2007 Using connect file 'slddest.cfg'.
Thu Dec 27 10:33:04 2007 No key file 'slddest.cfg.key' used.
Thu Dec 27 10:33:04 2007 HTTP trace: false
Thu Dec 27 10:33:04 2007 Data trace: false
Thu Dec 27 10:33:04 2007 Using connect file 'slddest.cfg'.
Thu Dec 27 10:33:04 2007 No key file 'slddest.cfg.key' used.
Thu Dec 27 10:33:04 2007 *** Start SLD Registration ***
Thu Dec 27 10:33:04 2007 Used URL: http://hostname01:50000/sld/ds
Thu Dec 27 10:33:04 2007 HTTP open status: true - NI RC=1
Thu Dec 27 10:33:04 2007 HTTP send successful.
Thu Dec 27 10:33:04 2007 Return code: 401 --- Return message: (Unauthorized)
Thu Dec 27 10:33:04 2007 HTTP response: Failure. HTTP status code: 401
Thu Dec 27 10:33:04 2007 *** End SLD Registration ***
Thu Dec 27 10:33:04 2007 Data send status: false
Consequently SLD is not updated with TREX information. Using IE I can go to
the url http://hostname01:50000/sld/ds , get popup asking for
credentials (we log in using SLDDSUSER account - w/ Basis Admin level
auth.), and we receive: Page Cannot be displayed (HTTP 400 - Bad Request
Internet Explorer ).
If we go to http://hostname01:50000/sld and login with the same
account (SLDDSUSER) we see the full SLD Toolset.
Edited by: Patrick Riggins on Dec 27, 2007 6:06 PMUPDATE:
We were able to work through and
resolve the error we initially posted in this Thread. Now we run sldreg
and all looks good; however, we are seeing nothing in SLD (on our XI
System) even after stop/restart of SLD Server:
Steps for the Reconstruction
1. Generate SLD Configuration Files:
sldreg -usekeyfile -configure /usr/sap/TXD/TRX00/slddest.cfg
2. Copied files to Global SLD
/sapmnt/TXD/global
3. Run command to transfer data to SLD:
saposcol -b | sldreg -user <user acct> -pass <password> -host
<hostname> -port <port #> -datatrace -httptrace -
logfile /usr/sap/TXD/TRX00/sld_reg.log -stdin
Looks successful:
Thu Dec 27 20:31:06 2007 HTTP body length: 0 --- HTTP body: empty
Thu Dec 27 20:31:06 2007 Return code: 200 --- Return message: (OK)
Thu Dec 27 20:31:06 2007 HTTP response: Success. HTTP status code: 200
Thu Dec 27 20:31:06 2007 *** End SLD Registration ***
Thu Dec 27 20:31:06 2007 Data send status: true
However in SLD , under content maintenance selecting "All With
Instances" in the dropdown list and "Class" , no TREX Services showing.
And no technical system showing for TXD (TREX System) -
Initial Setup Problem - Starting the SLD Registration process
Hi,
we are installing our PI development system. During initial configuration with "NWA --> Configuration Management --> Scenarios --> Configuration Wizard --> Netweaver initial setup" the wizard stands still at Step 68 (of 561) "Starting the SLD Registration process".
We have restarted the system but after starting again the wizard it stands still again.
Same problem on our PI quality assurance system.
PI 7.11 on Windows 2008 R2 with MSSQL 2008 R2.
Steps of installation:
1) Installation of PI 7.11
2) Postworks ABAP (License, TMS, Profiles, rz04, ...)
3) Kernelupdate to 106
4) Updates SPS7 ABAP
5) Updates SPS7 JAVA
6) Run NWA Initial Setup with J2EE_ADMIN
Could someone help?
Thanks
Regards
Thomas MühlThen possibly the password was set wrong somewhere (since the "-" character is not blocked). Its advisable to check all service users passwords, to prevent other issues like this one to occur. Please check the OSS note "999962 - PI 7.10: Change passwords of PI service users" for more information on this.
-
RWB / SLD Registration / MsgUrl is null?!?
Hi there,
i have a Problem. when i go to the SLD Registration in the RWB to Register
Runtime Workbench
Repository
I Become the Message:
Runtime Workbench reports registration status: completely registered
XIDomain.IntegrationServer.MsgUrl: MsgUrl of Integration Server is.00.server1 is null.
XIDomain.IntegrationServer.SecureMsgUrl: SecureMsgUrl of Integration Server is.00.server1 is null.
XIDomain.IntegrationServer.BusinessSystem: BusinessSystem is null. No BusinessSystem associated to the Integration Server is.00.server1.
also on the Adapter Engine
Messaging URL of Integration Server: URL currently used by Adapter Engine is null!
Messaging URL of Integration Server: URL stored in SLD is null!
Messaging URL of Integration Server: URL currently used by Adapter Engine and URL stored in SLD are the same
XIDomain.IntegrationServer.MsgUrl: MsgUrl of Integration Server is.00.server1 is null.
XIDomain.IntegrationServer.BusinessSystem: BusinessSystem is null. No BusinessSystem associated to the Integration Server is.00.server1.
The directory is another message:
Directory: Unable to get directory instance and read data from SLD; details: Unable to create an object that represents the SLD entry for the XI component
Can someone help here?
Regards
Edited by: Bjoern Bayerschmidt on Jun 2, 2010 8:55 AM
Edited by: Bjoern Bayerschmidt on Jun 2, 2010 8:56 AMand you looked at both notes?
all of this was provided in the two notes in my first post..... if this did not work.....
Solution
Checking completeness and consistency of SLD
First check whether the PI structures in SLD are incorrect. Start the SLD user interface (http:<host name>:<port>/sld), navigate to Technical Systems --> Process Integration
For a correct PI registration, the tabular display of the PI structure must contain the following entries:
- One entry for the domain of the Integration Server
- One entry for each PI component: Integration Server, Adapter Engine, Directory, Repository and Runtime Workbench (RWB). Each must be assigned to the domain above, i.e. the domain name must appear in column "Domain".
If some of the PI components Adapter Engine, Directory, Repository or Runtime Workbench are missing in the table, you need to explicitly register those as described below. If they appear in the table, but are not assigned to a domain, you have to delete them and register them explicitly.
Deleting PI components
Navigate to
Technical Systems --> Process Integration
Select the components you want to delete, push "remove" button.
Beware: Do not accidentally delete the XIIntegrationServer.
Triggering SLD Registration of PI components
You can trigger registration of a PI component by restarting the associated application. Navigate to the start/stop UI in the Netweaver Administrator:
http:<host name>:<port> --> SAP Netweaver Administrator --> Configuration Management --> infrastructure --> application modules
Here you restart the applications for the missing PI components:
com.sap.xi.directory (Integration Builder/Configuration)
com.sap.aii.af.app (Adapter Engine)
com.sap.xi.rwb (Runtime Workbench)
com.sap.xi.repository (Integration Builder/Design)
this is why i gave both notes as the information you provided was far from complete...
what version are you using? is it a new install? or a restore? or did it just go like this??? -
PIRWBUSER / not enough Permissions / SLD Registration / Adapter Engine / PI
Hi Community,
i have a Problem. I go to the SLD Registration in the RWB
When i click on Adapter Engine and Register i become the Message
Adapter Engine P11 (HOST): Unable to get Adapter Engine instance and read the data from SLD; details: Cannot connect to component Adapter Engine P11 (HOST); user PIRWBUSER does not have sufficient authorization to call servlet at URL http://HOST:50000/AdapterFramework/regtest.
My PIRWBUSER has the following Roles:
SAP_SLD_CONFIGURATOR
SAP_XI_RWB_SERV_USER
SAP_XI_RWB_SERV_USER_MAIN
Can someone help here?
Regards
BjoernHello!
Apply the note below according to your system version:
999962 - PI 7.10: Change passwords of PI service users
936093 - XI 7.0: Changing the passwords of XI service users
721548 - XI 3.0: Changing the passwords of the XI service users
If not worked, try working with the SAP_ALL and check if works.
Regards,
Caio Cagnani -
Delete SLD Registration in RWB
Hi,
I would like to delete the component Name (Adapter Engine) listed in Non-central components, as the host name/system doesn't exists anymore. The reason I would like to delete is, whenever we make the changes to any IB objects, save and activate and error messge pops up with this host name.
Thank youGo to SLD -> Technical Systems -> Technical System Type (process integration) ->
If you find the relavent adapter engine.. remove it and try..
http://wiki.scn.sap.com/wiki/display/XI/How+to+Manually+Correct+the+Registration+of+XI+Components+Within+the+SLD -
I want to register a J2EE instance into a SLD that runs on a separate XI instance. The registration of the XI J2EE instance itself into the SLD works fine but when i register the other J2EE instance with exactly the same parameters in the SLD the following error is reported: 'Invalid HTTP connect data'.
Any help is appreciated,
JackHi Pascal,
I did that, now when I run dtr.bat I receive this message:
dtr is DTR's client tool for the command line.
It can be used in 2 modes
- As a simple command line client
- As a shell
The shell can be started using dtrshell
In both these modes the user will require to logon through a popup unless the co
mmands being used do not connect to the DTR server(Exa: help command).
If it is required that the login popup does not appear then one of the following
should be true.
1. The vfs config folder should have a user.xml file.
2. The username & password should be specified using the following commandline o
ptions:
a. --username/-un <username>
b. --password/-pwd <pwd>
Note that if only the user name is specified as commandline argument even then t
he user will be asked for the password via a popup.
using the -def option the client to be used can be specified
Once in the shell all commands can be used without using dtr before them
Try:
dtr help simple list most common commands
dtr help commands list all commands
dtr help command help on a specific command
dtr help usage generic command line arguments
dtr help configure lists properties to cinfigure commands/options
Commandline client Version : 1.60
And When I run dtrshell.bat I receive login screen and when I enter valid credentials I receive this exception:
>Initializing...
>This may take a few seconds. Please wait...
>Connecting to client ""
Exception in thread "main" java.lang.IllegalStateException: The client specified
is not correct or there is no active client present
at com.tssap.dtr.client.commandline.Cache.getContext(Cache.java:143)
at com.tssap.dtr.client.commandline.Cache.initialize(Cache.java:49)
at com.tssap.dtr.client.commandline.Cache.getCache(Cache.java:63)
at com.tssap.dtr.client.commandline.DTRShell.main(DTRShell.java:79) -
Problem during installation. sld registration
Hello,
I'm installing a SAP ERP 2005 system. The installation is stopped when sapinst try to register the system in the SLD. (SLD on solution manager 4.0).
Here is the errors from the log:
FRF-0007 (Unable to open RFC connection)
MUT-03025 (Name or password is incorrect).
Connection to http://hostname:50000/sld/admin with user J2EE_ADMIN is ok.
Any ideas?
Does problem come from a bad password entered in sapinst at the beginning?
Could anyone tell me how to force sapinst to enter new sld informations again without restarting all the installation? Note that I've exactly the same problem with another similar installation which also use the same SLD.
Many thanks for your support!
Vanderperre OlivierMy problem is solved!
Sapinst tried to execute the RFC connexion with DDIC on client 300 witch was empty at this moment. I changed to use 001 and the installation finished successfully.
Best Regards,
Vanderperre Olivier -
Hi All,
While installing our SRM server we chose "no SLD". We planned to register the SLD in SOLMAN later on. Currently SRM SLD is
up and running, but there are no data supplier in AS ABAP. We tried to run RZ70 by pointing to SRM Host And Gateways. It fails.
While RZ70 runs fine if we point to SOLMAN.
We want to understand how to register SLD of SRM in SOLMAN or if not needed can we have a local SLD in SRM configured now?
As we will be using EP 7.0; SLD is an integral part to make the things happen.
Some technical help or suggestions will be ueful for us.
Thanks & Regards,
IshanDear Ishan,
First of all you need to check your landscape design blueprint. If you are going to have a central SLD which is not going to be on your SRM system itself then you can configure your SRM data suppliers to the central system's SLD itself.
However, if you want to configure the data suppliers to your SRM system itself then first check what is the result on the page http://<hostname>:<port>/sld
As SLD should be installed by default so you would just need to do the SLD configuration as per the post-installation guide available at System Landscape Directory (SLD)
This should help you out.
Regards,
Abhishek -
SLD Data Supplier Configuration in AS Java System
Hi All,
I am trying to configure my SLD manually in SAP Netweaver CE 7.1
1. Both SLD_DataSupplier and SLD_Client Destinations are created and are successfully.
2. All the security roles and groups are created and mapped in Identity Management (SAP NWA).
3. Also SLD is running.
4. CR_Content is imported from Browser.
When i click SLD_DATAsupplier_configuration in SAP NWA- configuration management - infrasturcture
Target_Url - undefined.
Both the Destionations are successfully when i ping those destinations.
Also when i click "collect and send data". I am getting this error.
Collect and Send Data Failed. Data transfer failed. Destination SLD_DataSupplier is undefined.
When i see the trace file in \usr\sap\CE1\j00\j2ee\cluster\server0\log\default.trace
i get the error
SLD#sld#02004C4F4F50009C0000000300000A6C#2915050000000004#sap.com/tclmitsamuimainframe~wd#com.sap.sldserv.itsam.SAP_ITSAMJ2eeSLDDataSupplier_Impl#Administrator#1##F27A6B20FBAC11DFA34902004C4F4F50#5adebd80fbba11dfa57102004c4f4f50#5adebd80fbba11dfa57102004c4f4f50#0#Thread[HTTP Worker [@33483362],5,Dedicated_Application_Thread]#Plain##
Data collection for SLD registration failed: Data transfer failed. Destination SLD_DataSupplier is undefined.
[EXCEPTION]
java.lang.RuntimeException: Data transfer failed. Destination SLD_DataSupplier is undefined.
at com.sap.sldserv.itsam.SAP_ITSAMJ2eeSLDDataSupplier_Impl.CollectAndSendData(SAP_ITSAMJ2eeSLDDataSupplier_Impl.java:80)
at com.sap.sldserv.itsam.SAP_ITSAMJ2eeSLDDataSupplierWrapper.invoke(SAP_ITSAMJ2eeSLDDataSupplierWrapper.java:156)
How can i resolve this error. What other configurations has to be done for this.
Thanks and Regards,
DivyaHi Mark,
SLD Configuration works fine with wizard based configurations. But manually when i try I fail in this automatic collect and send data.
Also while creating destinations, i tried using
http://localhost:50000
http://localhost:50000/sld
Ping is successful.
But During Destination creation when i give
http://localhost:50000/sld/ds. It says "bad Request. Parse error".
Also i am referring this pdf.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20b1adee-ce37-2c10-16a3-ef3e1ca948da?quicklink=index&overridelayout=true
Here at the picture where the target url is "Undefined". The automatic send property holds a value of true. In my case,
target url is undefined. But
automatic send = false.
Can i change this parameter value.
What other configuration is required.
Divya
Edited by: Divya V on Nov 29, 2010 5:09 PM -
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,
GiriHere 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 -
Register system to SLD with fully qualified name
Anybody know how to register the host name for an abap system to the SLD so it uses the fully qualified DNS name? According to the help files in the SLD, it say's: "By default, host names in SLD are written lower case without any network domain"
Our SAP servers are in:
ex.) abc.domain.com
Our desktops are in:
ex.) def.domain.com
So, when developers try to register their local NWDS to the SLD, they cannot reach it. The only solution is for them to add the SAP Server domain (dx.domain.com) into their local tcp/ip settings on their desktop.
Does anybody else have this same issue? Any suggestions on how we can use a FQ DNS name for SLD registration?
-DaveSorry for the confusion. I think I may have mis-worded my own question. It was a Friday!
Want I meant to say was, our developers' local JCo connections fail when they try to make a connection to an SAP system listed in the SLD. This is because the two machines (pc and SAP server) reside in different domains.
SAP Servers are in abc.domain.com
Desktop computers are in def.domain.com
The only way for the JCo connection to work from their desktop, is if the developer adds "abc.domain.com" into the tcp/ip settings on their desktop.
If we could register the SAP system in the SLD as a Fully Qualified Name, I think the problem would disappear. -
Cannot construct URL for runtime check using entries in SLD
Hi,
we are using high availability for PI 7.1 and are facing to the problem to construct the url for Communication channel monitoring etcv. in rwb.
In the exchange profile it looks good. Is there another place to check parameters for sld?
Thanks in advance
Frank
Message: Cannot construct URL for runtime check using entries in SLD for component af.rbi.s3p1028; correct the entries in SLD
Stacktrace:
com.sap.aii.rwb.exceptions.OperationFailedException: Cannot construct URL for runtime check using entries in SLD for component af.rbi.s3p1028; correct the entries in SLD
at com.sap.aii.rwb.core.XIJavaRTCComponent.getConnector(XIJavaRTCComponent.java:211)
at com.sap.aii.rwb.core.XIRTCComponent.ping(XIRTCComponent.java:209)
at com.sap.aii.rwb.web.componentmonitoring.model.CompTestModel.doPing(CompTestModel.java:623)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.doPing(CmDynPage.java:428)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.updateTests(CmDynPage.java:528)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.selectNode(CmDynPage.java:555)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.process_treeClick(CmDynPage.java:484)Hello
A combination of the notes below should resolve this error:
#764176 Error in XI due to inconsistent SLD contents
#1117249 Incomplete Registration of PI components in SLD
#1334053 No automatic PI 7.10 SLD Registration
#1278563 Specification of message server host in Exchange Profile
Regards
Mark -
[PI 7.11 SP3] PI components not correctly registering themselves after AS restart
Hi Experts,
We have planned a system backup shutdown and restart every night for our PI environment.
In a random manner, some PI components as XI AF or Integration Directory are not correctly registered to SLD after that restart : for example, Integration Directory registers but it is not assigned to a PI domain.
It is good to mention that PI instance is actually using its own SLD (local SLD) for registration.
When the problem occurs, I follow sap note 1117249 to manually register PI components within SLD and this solves the issue.
But the definitive solution will be to avoid incomplete SLD registration at restart … But I have not yet found any sap note for that kind of solution.
Il someone can help J
Thanks a lot
NadirHey Caio,
Thanks for the response but it doesn't actually answer my question. But to that point, for a "basic" PI post install, which of the NWA config tasks would you run other than the "initial config" ? And would you run them BEFORE you updated the SLD content (cimsap/CRDelta) ?
NW: PI - AS ABAP (Basic Configuration for Idoc, Proxy): Maintain
PI Adapter Engine in JPR Mode
PI Demo Client
PI Full Qualified Host Name
PI Self Test for NetWeaver
PI SLD Self Registration
Specifically, I did the SAPINST - ABAP/JAVA patches - Client copy - and THEN the initial config wizard (Setup a new local SLD, ). Also, during the initial config, I clicked the box marked "This SLD will be used as a name server for development" and my PI server hostname was already in the box marked "object server name". This config took about 30 minutes. I didn't see any errors or warnings. although I didn't view the log. I did go into Java JEE services and Filter for Services with name "XPI". All were green.
THEN I tried to update the SLD content.
any thoughts appreciated.
NICK -
PI 7.11 sp6 system copy Exchange Profile error code: 399
Experts,
We have a PI 7.1 (EHP1, sp6) PI system based on AIX 6.1 OS and Oracle 11g.
I recently did the standard PI system copy from a prod source (PIP) to a training target (PIT).
I used the most recenty PI system copy guide that is specific for PI 7.1 EHP1
I did not run into any major problems doing the steps of the copy itself.
I did the usual "post" steps, documented in the guide that really are done on any NW system.
Then I got into the specific "PI" post steps and that's where I now have a problem.
I followed all the steps, fixing my RFCs, JCos, Destinations, cleaning up SLD, SLDAPICUST, creating new business systems...etc.
My big problem is with the exchange profile. Yes, it's easy to change all the SIDs and hostnames using the search tool for all the parameters in the exchange profile, but the one I COULD NOT CHANGE was the "ABAP Connection". In there right after the copy was the hostname of the prod system, the client, and the user PILDUSER. I attempted to put the hostname of my target (PIT) system, but I would get the error:
com.sap.rprof.dbprofiles.DBException: RFC call returned an error code: 399
I'm certain the user is NOT locked and the password is correct for PILDUSER. It'll give me a different error if I put the wrong password in, so I know it's hitting my system.
Worse yet, If I left the hostname in there that was set to "prod", then when I changed all the other values in the "parameters" section of the XI profile, then it actually changed my PROD system!!
If I keep the ABAP connection to PIT, then the entire exchange profile disappears for PIT.
I see these errors in the default trace and application log:
Caused by: com.sap.lcr.api.cimclient.LcrException: CIM_ERR_NOT_FOUND:
No such instance: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",
Name="PIT.SystemHome.<traininghostname>"
Caused by: com.sap.lcr.api.cimclient.LcrException: CIM_ERR_NOT_FOUND: No such instance: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",Name="PIT.SystemHome.<traininghostname>"
at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.raiseExceptionOnError(SimpleResponseAnalyser.java:120)
#2.#2011 11 03 13:49:47:008#0-500#Error#com.sap.aii.af.service.sld.SLDRegistrationJob#
#BC-XI-CON-AFW#com.sap.aii.af.lib#7E3832DEA80F002B00000000008700C6#4804850000001902##com.sap.aii.af.service.sld.SLDRegistrationJob.SLDRegistrationJob.invoke()#J2EE_GUEST#0##0AFD01D4064C11E1CB5E7E3832DEA80F#0afd01d4064c11e1cb5e7e3832dea80f#0afd01d4064c11e1cb5e7e3832dea80f#0#Application [24]#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.#2011 11 03 14:51:18:096#0-500#Error#com.sap.esi.esp.service.server.ESPServiceInterfaceAbstract#
#BC-ESI-WS-JAV#tcesiespsrv#7E3832DEA80F001100000000009A004C#4804850000001385##com.sap.esi.esp.service.server.ESPServiceInterfaceAbstract####109F6812065511E1BF9C7E3832DEA80F#109f6812065511e1bf9c7e3832dea80f#109f6812065511e1bf9c7e3832dea80f#0#Service Runner [tcesiespsrv]#Plain##
+There is problem reading the hostname from the ClusterManager. This could lead to improper wsdl links.#
SLDCHECK shows this:
Function call returned exception code 3
Access to the XI Profile is currently disrupted.
I can't be the first person to run into this.
SO strange that I can actually plug in either my dev/QA or PROD hostname in the "ABAP connection" box and it WILL ACCEPT IT...but then, it registered my training system as a "non central adapter engine". I don't want that.
Any ideas?
Another issue is that the SLD PI information from the PIT system is missing the "Integration Directory". It has the other 5 entries...Adapter Engine, Domain, Integration Repository, Integration Server, RWB.
Thanks for reading this,
NICKHere is the error I get when I try to change the "abap connection" to the correct hostname:
RFC call returned an error code: 399
Stack Trace class com.sap.rprof.dbprofiles.DBException:<br><pre>at com.sap.rprof.dbprofiles.DBProfiles.checkReturn(DBProfiles.java:184) at com.sap.rprof.dbprofiles.DBProfiles.getProfile(DBProfiles.java:105) at com.sap.rprof.dbprofiles.RemoteProfile.readRemoteProfileFromMedia(RemoteProfile.java:1378) at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfileFromFactory(RemoteProfile.java:204) at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfile(RemoteProfile.java:154) at com.sap.rprof.dbprofiles.ExchangeProfile.getExchangeProfile(ExchangeProfile.java:46) at com.sap.rprof.remoteProfile.webui.ProfileWebTree.<init>(ProfileWebTree.java:24) at com.sap.rprof.remoteProfile.webui.Edit.getWebTree(Edit.java:322) at JEE_jsp_treeexprof_4804850_1319481176000_1319565151782._jspService(JEE_jsp_treeexprof_4804850_1319481176000_1319565151782.java:59) 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:140) at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:436) at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:493) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:399) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:388) at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:244) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) 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:78) 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:78) 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:78) at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428) at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247) at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327) </pre>
Maybe you are looking for
-
i recently purchased an in app purchase which is showing up on my itunes account as a purchased but has not shown up on my ipod touch 4th gen. (think it was due to losing my wifi connection during download). i went into problem solving on the itunes
-
No Solution Center on windows 8.1 to F4500 printer
My laptop was destroyed and I purchased an HP 21F7-100 laptop which has windows 8.1. I could not connect with my HP deskjet F4500 printer. I downloaded a driver for 8.1 and the printer works fine. My cd for the printer which has the solutions cent
-
i bought my iphone second hand , i have no contact with the owner and its linked to his icloud, please help
-
I am sure you have this covered in the forum. However, as i am not that confident about what i am doing, i feel i need to clarify what i am actually doing is correct!! I have bought a Sony HDD video camera for a forth coming holiday. However it seems
-
Dear experts, While doing GRN in MIGO, there is an option to capture excise by choosing "capture excise invoice". Here, how to bring up the pop box to show the Register where its going to get posted. What are the required settings to be done in SPRO.