Multiple runtime systems

Hello All,
Is there a way to define two runtime production systems in NWDI for a track?
Thanks,
Kiran

Hi Kiran,
May be this thread will come in handy. I explained clearly the procedure to deploy to multiple systems
transport to mulitple systems
thanks

Similar Messages

Track Connections to support Multiple QA & Production Runtime Systems

Hi,
I've read the SAP Help and various other threads in this forum that describe how to configure track connections that will support deployment into multiple production runtime systems. Can the track design therefore support the following scenario :-
Dev --> Consolidation ---> Multiple Pre-Production Runtime Systems --> Multiple Production Runtime Systems.
If this scenario can be implemented in the NWDI Landscape Configurator what would be the best approach to define this ?.
The reason I'm asking is our customer is planning multiple Portals in Production & Pre-Production due to the number of LDAP's currently being used to roll-out to the full user community.
Regards,
Brian.

Hi Kiran,
May be this thread will come in handy. I explained clearly the procedure to deploy to multiple systems
transport to mulitple systems
thanks

How can I handle deploying multiple test systems on the same PC that have been developed using different versions of LabVIEW, TestStand, and/or Switch Executive?

The major issue here is that the test systems must be documented and validated before being released to the production floor. Given this if a test station has multiple test systems deployed on it that have been developed on various versions of LV, TS, and Switch exec how can I force the test system selected to use the correct versions of TS, LV, and Switch exec.? I understand that the solution would be to recomplie everything and bring them up to the latest version but that would then require re-validation according to the QA department. Any advice would be greatly appreciated.
It would be nice if theTS deployment was more like an LV executable... meaning when a LV executable is launched it always knows what LV runtime engine to use when there are multiple engines installed on a PC.

Hi,
Multiply versions of teststand can reside on the same system, but only one version can run at a time. They is a utility that has to be run to set the active version.
The SequenceFiles have a version number, and you will find an error will be generate if you try to Load the sequencefile in the wrong version of TestStand.
The labview VIs will only work providing the correct version of the RTE is also installed on your system, even a labview executabe requires the correct RTE to be installed, either as part of the executable installation or as a seperate installation, before the labview exe will work correctly.
I'm not fimilar with the Switch exec but I would expect that it will also require the correct lower level device drivers to be available for the version you are using.
Therefore, as you are indicating that some of your system are at a older version, its difficult to image how you could achive this, considering if you say you have different versions of the software(s). For a start, you may have the problem that newer code/ sequencefiles using additional functionatily not available in the older versions.
I would think your only solution would be to have different deployments covering the different versions you have, or at least bring all your test systems up to the same version of teststand.
Regards
Ray Farmer
Regards
Ray Farmer

Multiple Logical Systems in Partner Profile for one instance

Can we create multiple Logical Systems in Partner Profile (WE20) for one instance or one System? If it is possible, can we create Logical System with respect to Plant/Country?

I am not quite sure if I understood your problem completley. But let's see...
Usually you use on on MSCS Cluster Group per SAP instance. So you have your already existing NW 7.0 ABAP stack in a separated Cluster Group, and you create a new Cluster Group for your new Java system.
You can find more information about it in this guide here on SDN:
Link: [High Availability;
More information about High Availability Setups for SAP System can be found here on SDN:
Link: [High Availability]
If you want to use the same database for your clustered ABAP stack and your new Java stack you can do a MCOD installation.
Please see Link: [SAP Note 388866 - Multiple Components on One Database - Installation|https://service.sap.com/sap/support/notes/388866]
Hope this helps.
Best regards,
Mathias

Please help me get my laptop back someone has cracked the master password and is running multiple operating systems which I have no access to

Okay so I am not a computer expert by any means and have no clue how to fix my system. My father worked for intel for over 20 years as an engineer I asked him to restore my laptop to its original factory state and instead he cracked the master password
installed multiple operating systems and made himself the administrator or domain controller. Many features and options I do not have access to so reading the trouble shooting and going through the steps always leads me to a dead end. The laptop is TOSHIBA
SATELLITE L875D-S7332 a6 VISION AMD WINDOWS 8. As far as I can see my profile is actual running a version of windows 7. I do see reference to a windows 8RT windows 2003 windows vista wow64 and 32 I don't know what all that means I would just like to know how
wipe everything and get back to the factory condition I bought it in. If anyone can help it would be much appreciated

Do you have Win 7 installation disk? If yes, then go ahead and format the laptop if you don't need any data. If you need the data it it, then copy the same to USB disk and format it. Removing OS and deleting these things will anyhow keep some remains on
HDD. TO get the speed and performance back, you might need a fresh installation.
Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread.

Runtime system and weird types

When many of objective-c's unique features and 2.0 additions are discussed, it is often said that they depend on the "runtime system" in order to function. What is it? It almost sounds like a virtual machine, but somehow I doubt that.
Also, what is the difference between both Null, nill, and nil, and Bool and BOOL?
Any help is greatly appreciated.

palms831 wrote:
First of all, what is meant by linking against something, and what does linking in general mean? I know it's part of the compilation process, but my knowledge is pretty fuzzy beyond that.
Actually, it is not part of the compilation process. It is part of the building process, but that is different. Compiling takes a symbolic language and converts it into its equivalent machine language. Linking goes through all of the compiled object code and connects functions with their associated function calls. It will then construct some sort of "runtime object" (such as an application or shared library) that can actually be used.
Also, I know that when I instantiate an object I am sending a message to a class object. What I'd like to know is when that class object is created, and what determines which classes get instantiated and which don't.
Any class that you create will get instantiated. (Though one normally doesn't refer to classes being instantiated. Objective-C just happens to have a powerful runtime language that allows you to treat classes almost as if they were objects). A good linker will take any instantiated classes or functions that are never used and remove them from the executable. GCC and other UNIX linkers usually cannot do this. They can only remove unused object files that contain nothing but unused functions. That is why the Linux kernel contains so many tiny files with only one function. Microsoft, Borland, and Codewarrior Linkers were much better at this.

Questions on Runtime systems

Hi to all
I have two questions:
1)
SAP says do not use the system where the JDI s installed as runtime system, I suppose in order to avoid the CMS deadlock described in note 754143. Right ?
Suppose we have three system D (develop), T (test) and P (Pro). Teh JDI is instaleld in D. We define the track Development with the runtime systems T as "test" and P as "production".
As I understood the deploy on the D system happen automatically as soon the activation is triggered into the Dev Studio IF the system D is used as runtime system.
Please could you clarify how we can keep aligned the D environment with the system T and P from the point of view of he deployment if we cannot use the D system as runtime environment ?
2) Suppose we have three system D (develop), T (test) and P (Pro). Teh JDI is instaleld in D.
We defined the tracks DEVELOP and MAINTENANCE, connected by a 'repair' connection.
If I understood weel the DEVELOP track and the MAINTENANCE track should have the Development and the Test runtime system in exchanged order:
the system indicated as Test for the DEVELOP track has to be indicated as Develop for the Maintenance track.
Then the runtime Production system has to be defined for the DEVELOP track only ?
Regards

Hi, thanks H. for the info.
I understood the MAINTAIN track and the DEVELOP track MUST to have different runtime systems.
We need at least, (minimun), 3 different systems (development1 and test on the DEVELOP track and development2 on the MAINTEN track) in order to maintain an old relese of SC while a new release is in progress, right ?
It's then responsability of the 'connection repair' defined between the tracks to move the software from the DEVELOP track to the MAINTEN track.
Please, in which moment of the DEVELOP track the software will be copied also to the MAINTEN track ?
New question about the Consolidation phase.
At the beginning we configured ONLY the runtime development for the DEVELOP track. So the work o teh developers was deployed automatically on that system as they activate their activities into the Developer studio.
As traiing we released the activities and we saw them into teh Consolidation tab queue ready for transport (NO Consolidation runtime system was in place).
Anyway we selected them and run the import. The CMS said it gone well.
After that the activities of the developers were into the Assebly tab queue.
My dubt is that after the import we saw our application working fine on the envirnment indicated as runtime develop system.
I need to clarify if this is the correct behaviour:
A) In this case using only the development runtime system into a track it does not have sense to relase the activities.
The development activity then end at that point and there is nothing else to do into the CMS.
If you need at that point the SCA of your work, to import them elewhere you can find it under the ../Jtrans directory (on condition that you reeased them)
Right?
B) It's an bug of the CMS to allow to run the import from the Consolidation tab while there is no consolidation runtime registered ?
Or it do not represents a real, physical import of software but only a logical step needed to move ahead the sw ?
we suppose when we run the import from the Consolidation tab queue we overwritten again the application on the development runtime system, but I'm not sure of that.

Multiple runtime users for the same runtime

Hi,
Is there any GUI method to create multiple runtime users to access the same runtime repository ? Currently, we are running this script:
=============
grant WB_U_UII_OWB_REP9204 to &&rep_user;
grant WB_R_UII_OWB_REP9204 to &&rep_user;
grant WB_D_UII_OWB_REP9204 to &&rep_user;
grant WB_A_UII_OWB_REP9204 to &&rep_user;
==============
Is this the correct way of doing it ?
Thanks and regards,
Biswa.

Biswa,
No way to do this in UI other than the first time the runtime repository is created by the Runtime Assistant. However, as you correctly point out, granting the following 4 roles to any user is all it takes: WB_RT_X, where RT is the name of your Runtime Repository and X is A, D, R or U:
- The User role (U) gives select access to the public views in the runtime repository.
- The Developer role (D) gives execute access to the PL/SQL packages in the runtime repository required to perform deployment operations.
- The Runtime role (R) gives execute access to the PL/SQL packages in the runtime repository required to perform execution operations.
- The Admin role (A) gives execute access to the PL/SQL packages in the runtime repository required to perform administrative operations.
So you actually have some flexibility as to what exactly you want to allow the user to do.
Nikolai Rochnik

How to use a Web Template with queries from multiple BW Systems?

Hi all,
can anybody help me how to use a Web Template with queries (DATA PROVIDER)in it from multiple BW Systems?
Thanks in advance, best regards
Frank

Great! Thanks for the quick response.
Have you tried this for XMLA datasources created within the EP system also?
i.e use Web Analyzer to create a view from the XMLA source and use that view within WAD?
Thanks.

Error While Creating Runtime Systems on an Existing Track in NWDI

Hi,
There is already a track in NWDI with No runtime Systems.
I have to create the RunTime Systems to do development on this track.
When I try to select the Development checkbox in Runtime systems,
select configure without wizard, Gave   Deploy Host name: **********.com
            Deploy Port :50018 (SDM port)
           Deploy PSWD: SDM Pswd
It gives me a warning..
Synchronization of Runtime System triggered for system dev. Log can be found at
http://*****************************LogViewer?LogName=%2Fsapmnt%2FEPQ%2Fglobal%2FTCS%2FLOG%2FEPQ_WHRBD_D2010081322030045.log&Bsname=EPQ_WHRBD_D
When i go to the log file
I see this Error Message
20100813180502 Info   :cannot create a connection for the buildspace: EPQ_WHRBD_D //connect to deploy tool failed:Server <Host Name> did not accept login request as admin on port 50018. Details: ERROR: Could not establish connection to <Host name> at port 50018: Connection timed out:could be due to invalid address
Can you please tell me what could be the Reason.
Basis has already opened the Ports : http port and SDM Port.
I am able to ping the server from cmd prompt.
Points will be allocated for the answer.
Thanks.
Venkat

Hi,
There's no need to update CMS or to check whether the buildspace is open, do not click on JSPM flag (unless you need nwdi control at upgrade)...
The error message means only that from the host where you configure the RTS the SDM cannot be reached or logon request cannot be accepted.
This can be either , because the
- SDM password is wrong (you checked it already)
- the port is wrong (you also checked it. If this is really a 700 RTS, i.e. it has SDM, and the instance number is 00, then the port is really 50018, so this should be fine as well. Only mention, because as of 71X we use the P4 port 5<xx>04 for the deploy controller, as there's no more SDM). Still you can use "netstat -a" to see the status of the ports.
- The host is wrong. I agree with Dao, check not only FQDN, but also IP address.
Using this guide you can always check whether the entered data is correct:
http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29%28CMS%29Q0002
Best regards,
Ervin (http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29Home)

ERROR while saving the runtime systems(read time out exception)

Hi e xperts
I am configuring NWDI and assigned asll the permissions and roles to the CMS user.I created Domain,in landscape configurater
created track and saved.
while saving the rumtime systems the error thrown is
com.sap.cms.util.exception.conf.CMSCCBSCommunicationException: CBS (URL http://dtlepdev:54400/tc.CBS.Appl/archiveapi2/) communication exception: Read timed out (Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out)
at com.sap.cms.pcs.conf.communicator.CBSConfCommunicator.removeBuildspace(CBSConfCommunicator.java:382)
at com.sap.cms.pcs.conf.communicator.CBSConfCommunicator.deleteCreateBuildspace(CBSConfCommunicator.java:338)
at com.sap.cms.pcs.conf.communicator.CBSConfCommunicator.editBuildspace(CBSConfCommunicator.java:277)
at com.sap.cms.pcs.conf.communicator.CBSConfCommunicator.createBuildspace(CBSConfCommunicator.java:168)
at com.sap.cms.pcs.conf.core.services.SystemManagerObject.saveSystem(SystemManagerObject.java:261)
at com.sap.cms.pcs.conf.core.plugin.DefaultTrack.newTrack(DefaultTrack.java:292)
at com.sap.cms.pcs.conf.core.TrackManager.editTrack(TrackManager.java:208)
at com.sap.cms.pcs.conf.manager.CmsConfManager.editTrackConfiguration(CmsConfManager.java:1002)
at com.sap.cms.pcs.conf.manager.proxy.CmsConfProxyBean.editTrackConfiguration(CmsConfProxyBean.java:489)
at com.sap.cms.pcs.conf.manager.proxy.LocalCmsConfProxyLocalObjectImpl0_0.editTrackConfigurationand also ..
Unable to instantiate a Build Space administrator!
Build Space "DTL_ETRACK_C" [bsID: 27, version: 0] [in-queue: on (privileged), out-queue: "on", processing: off]
<null>
[EXCEPTION]
Buildspace DTL_ETRACK_C does not own the workspace ws/ETRACK/dtl.com_DEFAULTIME/cons/inactive/ . It is currently not owned by any other buildspace
at com.sap.tc.cbs.server.rt.bs._BuildSpaceValidator.checkWorkspace(_BuildSpaceValidator.java:120)
at com.sap.tc.cbs.server.rt.bs._BuildSpaceValidator.validateWSs(_BuildSpaceValidator.java:74)
at com.sap.tc.cbs.server.rt.bs.BSAdmin.validate(BSAdmin.java:192)
at com.sap.tc.cbs.server.rt.bs.BSAdmin.updateState(BSAdmin.java:260)
at com.sap.tc.cbs.server.rt.bs.BSAdminOrc.determineChanges(BSAdminOrc.java:439)
at com.sap.tc.cbs.server.rt.bs.BSAdminOrc.validateBuildSpaceData(BSAdminOrc.java:219)
at com.sap.tc.cbs.server.rt.bs.BSAdminOrc.act(BSAdminOrc.java:341)
at com.sap.tc.cbs.server.rt.impl.CourteousTimer.run(CourteousTimer.java:139)
at java.lang.Thread.run(Thread.java:534
In cbs i checked the parametrs they are open and on..
please suggest me on this ASAP..since 2 days i have been struggling and searched in forums..no perfect solution
help me out
perfect soln is immediately awarded...
I
THanks
Mayu

Hi Mayu,
here apparently the CMS cannot communicate to CBS properly and then when CMS tries to talk to CBS using a webservice, it times out due to various reasons, see below.
Strange, I always had this error when the CMS was on a different release like CBS and this caused the communication problem.
Don't you have an entry in your cms log like this?
com.sap.cms.util.exception.CMSUnexpectedException
at com.sap.cms.pcs.conf.manager.CmsConfManager.newTrackConfiguration(CmsConfManager.java:666)
Caused by: java.lang.IncompatibleClassChangeError
at com.sap.cms.pcs.conf.communicator.CBSConfCommunicator.openConnection(CBSConfCommunicator.java:84)
Please provide me the version of the DI_CMS, DI_CBS (and DI_DTR for the sake of completeness).
You can find this info on the ComponentInfo page.
On 640/700 this is http://<host>:<port>/sap/monitoring/ComponentInfo
as of 710 you find this on the "Components" tab of http://<host>:<port>/nwa/sysinfo
I also think that this is not due to the runtime systems. I guess you have the same problem if you try to create the track without runtime systems, right?
(The "Unable to instantiate a Build Space administrator!" is not necessarily an error, see the note:
#1175019 - Unable to instantiate a Build Space administrator!)
Thank you!
Best Regards,
Ervin

NWDI does not reach runtime systems ... sometimes

Hi all,
we have a strange problem with our new NWDI (7.40 SP5). Globally the NWDI works fine. Until now we have migrated 60 of our 180 tracks to the new environment and beside some smaller errors everything works fine.
Now the first track users try to deploy their developments to the runtime systems. Until now there are about 30 runtime systems connected, from 7.00 up to 7.40 systems. 7.00 systems work fine, all above it is a question of luck whether a deployment/import works or not.
The error message (severity = fatal) is always the same:
Exc=com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'DeployerNWDI' could not be connected to the specified host 'xxx' and port '5xxx4'
At the same time there are these four error messages at the logfiles:
1. Import failed
2. User cannot connect (the one above)
3. User cannot connect with stacktrace
4. Connection lost (the one below)
I have written a small WebDynpro-application at the NWDI-server which tries to open a connection to the runtime systems at a specific port and it is always OK (no firewall problem). I have tried to connect to the runtime systems with the connection user and it is OK too.
What we have figured out so far is that the application server has a problem in its default configuration when the OS has several network adapters and thus several IP addresses. This problem is solved already (there is a SAP note for that). Also we have increased the maximum number of connection the server is able to keep open at the same time.
The strangest part is that it works sometimes if you hit import just a second time after a failed import ...
Does anyone knows the problem or even better a solution? Thanks in advance!
Here is the full stacktrace:
Could not establish connection to AS Java on [P4://xxx:5xxx4]. Connection lost. Check if the host and port specified are correct and AS Java is up and running.
[EXCEPTION]
javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338)
at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:64)
at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:45)
at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.<init>(SessionImpl.java:150)
at com.sap.engine.services.dc.api.session.impl.SessionFactoryImpl.newSession(SessionFactoryImpl.java:36)
at com.sap.engine.services.dc.api.impl.ClientFactoryImpl.createClient(ClientFactoryImpl.java:127)
at com.sap.sdm.apiimpl.remote.client.P4APIClientSessionImpl.getDeployControllerClient(P4APIClientSessionImpl.java:166)
at com.sap.sdm.apiimpl.remote.client.P4APIClientSessionImpl.initClient(P4APIClientSessionImpl.java:137)
at com.sap.sdm.apiimpl.remote.client.P4APIClientSessionImpl.<init>(P4APIClientSessionImpl.java:60)
at com.sap.sdm.apiimpl.remote.client.P4APIClientSessionImpl.newInstance(P4APIClientSessionImpl.java:47)
at com.sap.sdm.apiimpl.remote.client.APIClientSessionFactoryImpl.createAPIClientSession(APIClientSessionFactoryImpl.java:53)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.sdm.api.remote.ClientSessionFactory.createRemoteClientSession(ClientSessionFactory.java:299)
at com.sap.sdm.api.remote.ClientSessionFactory.createRemoteClientSession(ClientSessionFactory.java:249)
at com.sap.cms.tcs.beans.deployer.DeployConnector.openConnection(DeployConnector.java:148)
at com.sap.cms.tcs.beans.TCSDeployBean.performDirectDeployment(TCSDeployBean.java:188)
at sun.reflect.GeneratedMethodAccessor1040.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
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:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at com.sun.proxy.$Proxy407.performDirectDeployment(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.engine.services.rmi_p4.reflect.LocalInvocationHandler.invokeInternal(LocalInvocationHandler.java:101)
at com.sap.engine.services.rmi_p4.reflect.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:52)
at com.sun.proxy.$Proxy412.performDirectDeployment(Unknown Source)
at sun.reflect.GeneratedMethodAccessor1039.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.engine.services.ejb3.runtime.impl.StatelessRemoteStubInvocationHandler.invoke(StatelessRemoteStubInvocationHandler.java:89)
at com.sun.proxy.$Proxy413.performDirectDeployment(Unknown Source)
at com.sap.cms.tcs.core.SDMDeployTask.processImport(SDMDeployTask.java:292)
at com.sap.cms.tcs.core.SDMDeployTask.process(SDMDeployTask.java:356)
at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:448)
at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:175)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:499)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:112)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:638)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:610)
at sun.reflect.GeneratedMethodAccessor690.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
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:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at com.sun.proxy.$Proxy514.startImport(Unknown Source)
at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1760)
at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2809)
at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:1158)
at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2856)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:94)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:908)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:880)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:326)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:367)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:490)
at com.sap.tc.webdynpro.serverimpl.wdc.ForwardServlet.doPost(ForwardServlet.java:73)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
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.SessionSizeFilter.process(SessionSizeFilter.java:26)
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:57)
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: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.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
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:328)
Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164)
at com.sap.engine.services.security.login.RemoteLoginContextFactoryImpl.getRemoteLoginContext(RemoteLoginContextFactoryImpl.java:95)
at com.sap.engine.services.jndi.implclient.LoginHelper.serverSideLogin(LoginHelper.java:114)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:312)
... 163 more
Caused by: java.io.IOException: Reading reply for initial call failed. Check remote side state
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.resolveInitialReference(P4ObjectBrokerServerImpl.java:1486)
at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41)
at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153)
... 166 more
Caused by: com.sap.engine.services.rmi_p4.exception.P4BaseConnectionException: Connection lost
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.getException(P4ObjectBrokerServerImpl.java:1320)
at com.sap.engine.services.rmi_p4.server.P4ObjectBrokerServerImpl.getException(P4ObjectBrokerServerImpl.java:1309)
at com.sap.engine.services.rmi_p4.P4Call.fail(P4Call.java:143)
at com.sap.engine.services.cross.fca.ConnectionImpl.notifyCalls(ConnectionImpl.java:150)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.notifyConnectionClosed(FCAConnectorImpl.java:253)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.clientConnectionClosed(FCAConnectorImpl.java:238)
at com.sap.engine.services.cross.fca.SystemMessageProcessor.parseMessage(SystemMessageProcessor.java:94)
at com.sap.engine.services.cross.fca.SystemMessage.process(SystemMessage.java:22)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
... 3 more

Hi Richard,
could you please check whether this note helps?
1492974 - Deployment to a AS Java does not work
Regards,
Ervin

Creation of sales order in CRM and replicating it to Multiple ECC system.

We have a requirement for creation of sales order in CRM and replicating it to Multiple ECC system.
We have checked the following standard Adapter objects in transaction R3AC1.
BUS_TRANS_MSG
The initial flow contexts does not support target site type as R/3(SMOF_ ERPSITE). So we are not able to replicate the sales order from CRM
to ECC.
2. SALESDOCUMENT
Here the initial flow contexts does not support flow from CRM -> R/3 as we don’t see the target site as CRM.
Please let us know if the standard sap middleware objects don’t support the sales order flow from CRM to multiple ECC or is there any
other adapter object we need to use for this.

Hey Vijay Duvvada,
I hope you are already referred below sap note and which explains scope & how to do -
1084315 - Consulting: Information about the multiple backend scenario
1763516 - How-to: Basic Setup of MEP
As explained by Rohit Sharma data should be start flowing to multiple sites.
please let me know if it does help.
Regards,
Arjun

Multiple SRM Systems One SRM-MDM Catalog?

Hi
I'm currently upgrading our SRM 5.0 to SRM 7.01 with SRM-MDM Catalog 7.01. Is it possible to use one SRM-MDM Catalog in our non-production environment and connect multiple SRM systems to it?
For example our sandbox, development and QA SRM 7.01 systems would all connect to the same SRM-MDM Catalog 7.01.
Thanks.
Neil

Hi,
for non-production use and if it is just a catalog without custom coding running I see no problem in using one MDM server for multiple SRM systems (especially sharing one for sandboxes and dev). It is a setup I have seen multiple times and it worked always without problems.
You should set up different repositories for each SRM system so that you don't interfere with each others data (i.e. suppliers or other lookups tied to SRM).
You have to keep in mind that you have to upgrade all systems together. But you can always use separate MDM servers during the upgrade process and then consolidate onto one server when the upgrade is done.
If you are running custom coding with your MDM catalog I would recommend having a separate MDM system for the QA SRM in order to be closer to the production set-up when testing your custom solution.
Regards,
Martin

Find exact RFC Destination for Multiple backend Systems In SAP Gateway

Hi Gateway developers,
I have requirement,if gateway hub system has multiple backend systems( for example two backend systems: ECC and SRM ) then how hub system can get the suitable backend alias for exact entity collection..
Here i have developed two entities one entity regards: ECC and second one regards SRM system..within this when I run the service it is always taking any of the same alias for both the collections..
Can you please suggest me..
Thanks
Sreenivas Pachva

Hi Srinivas,
You can add the respective system Alias Name: Like logical system name in your URI also.
Example:
/sap/Service Name;mo=ECCCLNT210/zentity1?Customer1='0001'
/sap/Service Name;mo=SRMCLNT400/zentity2?Customer2='ABCD'
May this help you.
Thanks,
Saurabh Gupta

Multiple runtime systems

Similar Messages

Maybe you are looking for