Problem in transports EP with CTS+

[Former Member]

Hi gurus,

We installed Solution Manager 4.0 SPS13 and 2 Portals 7.0 SPS13.

Solution Manager is configured as Domain Controller and configured the

TMS with all the systems. The Transport Routes are Portal DEV --> Portal PRO.

We have the configuration indicated in:

http://help.sap.com/saphelp_nw70/helpdata/en/45/ec25370fdc3481e10000000a1553f6/content.htm

The transport strategy is:

WBO_GET_REQ_STRATEGY = Smart

WBO_REL_ REQ_STRATEGY = Auto

We created a transport order in the CTS+ Browser (Standard Request), but when we try to export a package in the Portal DEV shows the error: "<i>No valid transport request found</i>".

The same error is displayed if in the CTS+ Browser there isn't transport order created.

Kind Regards

[cdumont69]

Hello,

You can use this 2 docs to know if you forgot something :

<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0dbfe77-0423-2a10-e19a-e0d1963c7dac">How to Configure and Operate Enhanced CTS</a>

<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/90d3b550-b6fb-2910-0fa5-ece5d61fb9c3">How To Set Up and Use the CTS+ in a Portal Environment</a>

Hope this could help you.

Regards

Chris

[Former Member]

Hi Christophe,

We appreciate your interest.

Unfortunately these documents that you say I had seen, and the configuration of our systems is correct, as indicated.

Any more idea??

Kind Regards

[cdumont69]

You said: "The Transport Routes are Portal DEV --> Portal PRO."

But If I remember the documentation, the right configuration is: <b>Solman -> Portal PRO</b> and <b>not</b> Portal DEV -> Portal PRO

Is it what you did ?

Regards,

Chris

[Former Member]

Hi Chris,

We tried the configuration that you say and show the documentation (Solman -> Portal PRO); but we also tried the configuration that we say you (Portal DEV -> Portal PRO).

With <b>Solman -> Portal PRO</b> not even it exports the package. It doesn't do anything.

With <b>Portal DEV -> Portal PRO</b>, it exports the package but it fails in import.

With <b>Portal DEV -> Solman -> Portal PRO</b>, it exports the package but it fails in import.

Any idea more?

Kind regards.

[Former Member]

when you create the transport on SOL, can you see 20071115_120006.epa in the transport(SE09, SE01)? If you look inside the request, can you see 20071115_120006.epa. Also can you see 20071115_120006.epa on the file system of SOL inside the request in the directory of the transport request number?

When you create the Non abap transport request, add the object, then release, it will create a directory under \usr\sap\trans\data with the actual request number.

[Former Member]

Hi Derek

Yes, I can see the transport order and the package inside on SolMan. Both exist.

Yes, the package is inside the directory of the transport order in the filesystem of SolMan.

Yes, there is a new folder in the filesystem (/usr/sap/trans/data) with each transport order.

The export process is done correct and perfectly.

Kind Regards

[Former Member]

Check your webservice exists(DeployProxy) in webservice navigator, also check that your RFC destination for CTSDEPLOY works correctly AND has the correct logon details.

Derek

[Former Member]

Hi Derek,

The Web Service <i>DeployProxy</i> response "200 OK", the RFC <i>CTSDEPLOY</i> response "200 OK" and the user and password are corrects.

Thanks for you interest.

[Former Member]

Just one other thing perhaps, the attributes of the request, are they

Application - EP

Deployment - SDM

Type - EPA

When you do resolve this, please post your fix.

Derek

[Former Member]

Hello gurus,

We did the scenario again and now returns the following error:

######################################
 Deployment
 Transport request   : SID_DEVK90000G
 System              : SID_PRO
 tp path             : tp
 Version and release: 372.04.08 700
 
 CTS Deploy Service - Version 0.92 06.03.2007
 ========================================================================
 Deploy web service destination = CTSDEPLOY
 Directory = /usr/sap/trans/data
 SDM Deploy URL = http://hostname:50118
 SLD Deploy URL =
 XI Deploy URL =
 Non-ABAP system SID_PRO (communication system SID_CTS)
 Deploy for SDM
 Deploy File = com.company.package.my_package_20071115_120006
 Start of Web Service Log
 Deploy Service called with following parameters:
 CommunicationData-Type:0
 CommunicationData-Address:http://hostname:50118
 CommunicationData-Host:hostname
 CommunicationData-Port:50118
 CommunicationData-User:'filled'
 CommunicationData-Password:'filled'
 Deployable(0)
 Deployable-Type:0
 Deployable-Id:/usr/sap/trans/data/SID_DEVK90000G/com.company.package.my_package_20071115_120006.epa
 class java.rmi.RemoteException:The user 'SID_PROADM' could not be connected to the specified host 'hostname'
 and port '50118'.
 com.sap.cts.deployer.SdmDeployer.deploy (SdmDeployer.java:73)
 com.sap.cts.core.DeployManager.deploy (DeployManager.java:58)
 com.sap.cts.ejb.DeployBean.deploy (DeployBean.java:98)
 com.sap.cts.ejb.DeployLocalLocalObjectImpl0_0.deploy (DeployLocalLocalObjectImpl0_0.java:103)
 sun.reflect.NativeMethodAccessorImpl.invoke0 (NativeMethodAccessorImpl.java:-2)
 sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39)
 sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25)
 java.lang.reflect.Method.invoke (Method.java:324)
 com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod (EJBImplementat
 >>>ionContainer.java:126)
 com.sap.engine.services.webservices.runtime.RuntimeProcessor.process (RuntimeProcessor.java:157)
 com.sap.engine.services.webservices.runtime.RuntimeProcessor.process (RuntimeProcessor.java:79)
 com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost (ServletDispatcher
 >>>Impl.java:92)
 SoapServlet.doPost (SoapServlet.java:51)
 javax.servlet.http.HttpServlet.service (HttpServlet.java:760)
 javax.servlet.http.HttpServlet.service (HttpServlet.java:853)
 com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet (HttpHandlerImpl.java:401)
 com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest (HttpHandlerImpl.java:266
 >>>)
 com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet (RequestAnalizer.java:387)
 com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet (RequestAnalizer.java:365)
 com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer (RequestAnalizer.java:
 >>>944)
 com.sap.engine.services.httpserver.server.RequestAnalizer.handle (RequestAnalizer.java:266)
 com.sap.engine.services.httpserver.server.Client.handle (Client.java:95)
 com.sap.engine.services.httpserver.server.Processor.request (Processor.java:175)
 com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process (A
 >>>pplicationSessionMessageListener.java:33)
 com.sap.engine.core.cluster.impl6.session.MessageRunner.run (MessageRunner.java:41)
 com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 java.security.AccessController.doPrivileged (AccessController.java:-2)
 com.sap.engine.core.thread.impl3.SingleThread.execute (SingleThread.java:100)
 com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
 End of Web Service Log
 Return Code = 12
 Highest Return Code = 12
 Deployment
 End date and time : 20071203182641
 Ended with return code:  ===> 12 <===
 ######################################

The user SID_PROADM is the "sidadm" user and the password is correct. The port 50118 is available and is the SDM Port.

Any idea?? Why gives me other error now if the configuration is the same??

Thanks

[Former Member]

the user ID is SDM, the same user you use when accessing the SDM when depolying java packages(remotegui.bat in Windows install).

I dont know if you changed this value for the post, but

SDM Deploy URL = http://hostname:50118.....hostname must be the FQDN of the server you are delploying to, with user=SDM and password that you use on the target server,

Is your SDM set to interactive?

Derek

Message was edited by:

Derek Galt

[Former Member]

Hi Derek,

OK, perfect. I was wrong with this user, I had sidadm... but why is it running now if the configuration is the same??

Kind Regards

[Former Member]

Hi Javier,

The 2 errors are different. 1st one could not find the .epa in the request SID_DEVK900009, in the second one the .epa was there but under SID_DEVK90000G, except with the request in SID_DEVK90000G you had the wrong user specified for the SDM in the target to deploy.

Derek

[Former Member]

Hi,

If it’s not rude to ask.

Why is it running now if the configuration is the same??

- In the second error, the mistake is mine, I didn't specify the correct user but

- In the first... why did not it find the .epa if the file existed in the filesystem and the configuration was the same??

Thanks for you help.

[Former Member]

Of course,

I am assuming this, but here goes, if you think of this in ABAP terms in normal STMS, first check will be data and cofiles, that they exist in /usr/sap/trans and if they do, then a valid user id to perform the import, your import will go ahead. So I assume that these failed in your 1st one(could not find the .epa) and 2nd one(user id), one of these 2 failed in both cases. You can see from the log that they both failed in step "Deployable-Id". Maybe if you investigate what all happens sequentially in this step(all the checks) it might give you better resolution to this one.

If I look at an ABAP request, the steps are:

Selection for Import(Case1 - no .epa)

Copy File Between Transport Groups(could not deploy because SDM user)

Import

Check Versions

Regards,

[Akshay_G]

Hi Derek,

Its been fairly long to be replying on this. But I will take my chances.

Derek Galt wrote:
Check your webservice exists(DeployProxy) in webservice navigator, also check that your RFC destination for CTSDEPLOY works correctly AND has the correct logon details.
Derek

In my case, I am not able to Import to Target, Import ended with error "Deploy Proxy Server not running or Web Service not installed"

As i checked and understand that DeployProxy Web Service is available on Java Stack of Solution Manager, Logical Port CTSDEPLOY is active in LPCONFIG Client 000 along with the maintained path, HTTP Destination CTSDEPLOY works fine with Response 200 OK.

I am wondering, is something missing on target side? Is the WB DeployProxy needs to be available at target also?

I am transporting .ear file

-Akshay

[Former Member]

We restarted all servers and it seems that this problem has been solved.

Now, we have the following problem when we trying release the order:

 ######################################
 Deployment
 Transport request   : SID_DEVK900009
 System              : SID_PRO
 tp path             : tp
 Version and release: 372.04.08 700
 
 CTS Deploy Service - Version 0.92 06.03.2007
 ========================================================================
 Deploy web service destination = CTSDEPLOY
 Directory = /usr/sap/trans/data
 SDM Deploy URL = http://eSID_PROl705:50118
 SLD Deploy URL =
 XI Deploy URL =
 Non-ABAP system SID_PRO (communication system SID_DomainControler)
 Deploy for SDM
 Deploy File = com.company.package.my_package_20071115_120006
 Start of Web Service Log
 Deploy Service called with following parameters:
 CommunicationData-Type:0
 CommunicationData-Address:http://eSID_PROl705:50118
 CommunicationData-Host:eSID_PROl705
 CommunicationData-Port:50118
 CommunicationData-User:'filled'
 CommunicationData-Password:'filled'
 Deployable(0)
 Deployable-Type:0
 Deployable-Id:/usr/sap/trans/data/SID_DEVK900009/com.company.package.my_package_20071115_120006.epa
 class java.io.IOException:The file /usr/sap/trans/data/SID_DEVK900009/com.company.package.my_package
 >>>_20071115_120006.epa does not exist on the filesystem.
 com.sap.sdm.util.sduread.impl.SduReaderImpl.readFile (SduReaderImpl.java:56)
 com.sap.sdm.util.sduread.impl.SduReaderImpl.readFile (SduReaderImpl.java:45)
 com.sap.cts.converter.ConversionSelector.isArchiveAnSdu (ConversionSelector.java:83)
 com.sap.cts.converter.ConversionSelector.execute(ConversionSelector.java:31)
 com.sap.cts.core.Deployables.convert (Deployables.java:62)
 com.sap.cts.core.DeployManager.deploy (DeployManager.java:57)
 com.sap.cts.ejb.DeployBean.deploy (DeployBean.java:98)
 com.sap.cts.ejb.DeployLocalLocalObjectImpl0_0.deploy (DeployLocalLocalObjectImpl0_0.java:103)
 sun.reflect.NativeMethodAccessorImpl.invoke0 (NativeMethodAccessorImpl.java:-2)
 sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39)
 sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25)
 java.lang.reflect.Method.invoke (Method.java:324)
 com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod (EJBImplementat
 >>>ionContainer.java:126)
 com.sap.engine.services.webservices.runtime.RuntimeProcessor.process (RuntimeProcessor.java:157)
 com.sap.engine.services.webservices.runtime.RuntimeProcessor.process (RuntimeProcessor.java:79)
 com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost (ServletDispatcher
 >>>Impl.java:92)
 SoapServlet.doPost (SoapServlet.java:51)
 javax.servlet.http.HttpServlet.service (HttpServlet.java:760)
 javax.servlet.http.HttpServlet.service (HttpServlet.java:853)
 com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet (HttpHandlerImpl.java:401)
 com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest (HttpHandlerImpl.java:266
 >>>)
 com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet (RequestAnalizer.java:387)
 com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet (RequestAnalizer.java:365)
 com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer (RequestAnalizer.java:
 >>>944)
 com.sap.engine.services.httpserver.server.RequestAnalizer.handle (RequestAnalizer.java:266)
 com.sap.engine.services.httpserver.server.Client.handle (Client.java:95)
 com.sap.engine.services.httpserver.server.Processor.request (Processor.java:175)
 com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process (A
 >>>pplicationSessionMessageListener.java:33)
 com.sap.engine.core.cluster.impl6.session.MessageRunner.run (MessageRunner.java:41)
 com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 java.security.AccessController.doPrivileged (AccessController.java:-2)
 com.sap.engine.core.thread.impl3.SingleThread.execute (SingleThread.java:100)
 com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
 End of Web Service Log
 Return Code = 12
 Highest Return Code = 12
 Deployment
 End date and time : 20071116145206
 Ended with return code:  ===> 12 <===
 ######################################

Any idea??

Thanks

[Former Member]

Hi,

Please go thru the error message. It clearly says that the "epa" does not exist. Check whether the epa file exists, before releasing the transport request. If not, create it.

best regds,

Alagammai.

[Former Member]

Hi Alagammai,

The error occurs at the phase of import to the Production Portal.

The export is always correct.

Permissions for folders export/import are "every-one" (chmod 777), and

the package exists in the filesystem of Domain controler.

Thanks.