Deploy script is no executed after configuring CTS+

[Former Member]

Hi Export,

I am trying to follow the guide 'How to implement CTS+ ... for your application' to config the CTS+ for the system using script based deployment.

after configuration, i found the deploy script is not executed after import tr, and the deploy has rc = 4 :

the import looks successfully finished, but the deployment, i can't get useful log message:

i don't know where i do wrong, could your please help with it ? if there are any other information i should provide?

Thanks in advance.

[former_member189220]

"... As for the setting of deployment port, do you mean the configuration of sm59 http destination 'CTSDEPLOY' ? I set the service no to 50200, i tried to reset to 50208 but it didn't work. ..."

The deployment port of the AS Java is 5xx04 (for releases 7.1 and above) .

It does not matter whether you do run dual stack or the AS ABAP and AS JAVA are on the different server boxes.

When the P4 port is not configured correctly, no deployment might be done.

[Former Member]

Hi Milen,

I tried to set the service no. of 'CTSDEPLOY' to 50204, but it didn't work.

there is a 'connection closed' message when i click 'test connection':

if this means the P4 port is not configured correctly or something else wrong?

and i have checked the java system details:

there has already a P4 port with value 50204, is this means the P4 port has been configured correctly ?

and i check the document 'Configuring the CTS Deploy Web Service' , in 'Configuring the HTTP Connection' part, it asked to created a http destination 'CTSDEPLOY' with service no. 5<SAPSystem Number>00, but not 5XX04, which is correct ?

then i found an error message 'There are no batch filters specified' in deploy.0.log in /usr/sap/SLJ/J02/work, don't know if deployment script is not triggered is because of this erorr:

#2.0#2017 08 04 07:37:47:421#+00#Info#/System/Server/Deployment#
com.sap.ASJ.dpl_dc.000563#BC-JAS-DPL#tc~bl~deploy_controller#C0000AAD0F49BCD00000000000009981#25189750000000003##com.sap.engine.services.dc.cm.deploy.impl#I321386#40456##94A76657A0F11005A2C192C798E73128#94a76657a0f11005a2c192c798e73128##0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain#com.sap.engine.services.monitor.mbeans.MonitorResourceBundle#
 [Server 00 02_251897] (61) :Operation deploy is triggered from user [I321386] and host [10.173.15.73]#


#2.0#2017 08 04 07:37:47:436#+00#Info#/System/Server/Deployment#
com.sap.ASJ.dpl_dc.001053#BC-JAS-DPL#tc~bl~deploy_controller#C0000AAD0F49BCD00000000100009981#25189750000000003##com.sap.engine.services.dc.cm.deploy.impl#I321386#40456##94A76657A0F11005A2C192C798E73128#94a76657a0f11005a2c192c798e73128##0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain#com.sap.engine.services.monitor.mbeans.MonitorResourceBundle#
 [Server 00 02_251897] (61) :Archives specified for deployment are: #


#2.0#2017 08 04 07:37:47:436#+00#Info#/System/Server/Deployment#
com.sap.ASJ.dpl_dc.001054#BC-JAS-DPL#tc~bl~deploy_controller#C0000AAD0F49BCD00000000200009981#25189750000000003##com.sap.engine.services.dc.cm.deploy.impl#I321386#40456##94A76657A0F11005A2C192C798E73128#94a76657a0f11005a2c192c798e73128##0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain#com.sap.engine.services.monitor.mbeans.MonitorResourceBundle#
 [Server 00 02_251897] (61) :[/usr/sap/SLJ/J02/j2ee/deployment/SDA/Hello.jar]#


#2.0#2017 08 04 07:37:47:902#+00#Info#/System/Server/Deployment#
com.sap.ASJ.dpl_dc.001107#BC-JAS-DPL#tc~bl~deploy_controller#C0000AAD0F49BCD00000000300009981#25189750000000003##com.sap.engine.services.dc.cm.deploy.impl#I321386#40456##94A76657A0F11005A2C192C798E73128#94a76657a0f11005a2c192c798e73128##0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain#com.sap.engine.services.monitor.mbeans.MonitorResourceBundle#
 [Server 00 02_251897] (61) :sda [JavaEE_Hello] was loaded from location [/usr/sap/SLJ/J02/j2ee/deployment/SDA/Hello.jar].#


#2.0#2017 08 04 07:37:47:977#+00#Info#/System/Server/Deployment#
com.sap.ASJ.dpl_dc.001055#BC-JAS-DPL#tc~bl~deploy_controller#C0000AAD0F49BCD00000000400009981#25189750000000003##com.sap.engine.services.dc.cm.deploy.impl#I321386#40456##94A76657A0F11005A2C192C798E73128#94a76657a0f11005a2c192c798e73128##0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain#com.sap.engine.services.monitor.mbeans.MonitorResourceBundle#
 [Server 00 02_251897] (61) :Deployment settings are:
<strong>Error Handling Action: [PrerequisitesCheckAction], Error Handling Strategy: [OnErrorStop]
Error Handling Action: [DeploymentAction], Error Handling Strategy: [OnErrorStop]
Error Handling Action: [UndeploymentAction], Error Handling Strategy: [OnErrorStop]{0} Version Handling Rule: [UpdateAllVersions]{0} Deployment Strategy: [normal deploy strategy]{0} Life Cycle Deployment Strategy: [disable LCM deploy strategy]{0}[There are no batch filters specified]#
</strong>

#2.0#2017 08 04 07:37:53:670#+00#Info#/System/Server/Deployment#
com.sap.ASJ.dpl_dc.001048#BC-JAS-DPL#tc~bl~deploy_controller#C0000AAD0F49BCD00000000500009981#25189750000000003##com.sap.engine.services.dc.cm.deploy.impl#I321386#40456##94A76657A0F11005A2C192C798E73128#94a76657a0f11005a2c192c798e73128##0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain#com.sap.engine.services.monitor.mbeans.MonitorResourceBundle#
 [Server 00 02_251897] (61) :Deployment finished with result: [The status of the deployed SDUs is Success. 
Additional information: 
]#


#2.0#2017 08 04 07:37:53:675#+00#Info#/System/Server/Deployment#
com.sap.ASJ.dpl_dc.000001#BC-JAS-DPL#tc~bl~deploy_controller#C0000AAD0F49BCD00000000600009981#25189750000000003##com.sap.engine.services.dc.cm.deploy.impl#I321386#40456##94A76657A0F11005A2C192C798E73128#94a76657a0f11005a2c192c798e73128##0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain#com.sap.engine.services.monitor.mbeans.MonitorResourceBundle#
 [Server 00 02_251897] (61) :===== Summary - Deploy Result - Start =====
------------------------
Type | Status  : Count
------------------------
 > SCA(s)
 > SDA(s)
   - [Success] : [1]
------------------------
------------------------
Type | Status  : Id
------------------------
 > SCA(s)
 > SDA(s)
   - [Success] : JavaEE_Hello, 
------------------------
===== Summary - Deploy Result - End =====
#
<br>

Very appreciate for your help.

[former_member189220]

Is this 50204 open on the AS Java? Check in the SAP MMC.

If yes, are there any network devices on the way of the deployment call?

Have you tried to deploy with TELNET? Was it successful?

[Former Member]

Hi Milen,

I have checked the SAP MCC, I think 50204 is already open, please see picture below:

and I think there is no network devices on the way of the deployment call, as both abap and java system are in same server, is there any way i can check it ?

I tried to deploy a test file 'Hello.jar' with telnet, and it successfully deployed:

>deploy /tmp/Hello.jar version_rule=same_lower
Converting /tmp/Hello.jar to sda
/tmp/Hello.jar has been successfully converted to sda


Deploy settings:
   life_cycle=bulk
   on_deploy_error=stop
   on_prerequisite_error=stop
   version_rule=same_lower
   workflow=normal


If there is an offline deployment, Telnet connection to host may be lost, but the result can be seen using [get_result] command


Processing deployment operation, wait...


===== PROGRESS START =====


Deploying [JavaEE_Hello (sda)] ...
Deployment of [JavaEE_Hello (sda)] finished.


===== PROGRESS END =====


===== DEPLOY RESULT =====


 sdu id: [JavaEE_Hello]
sdu file path: [/usr/sap/SLJ/J02/j2ee/cluster/server0/temp/tc~bl~deploy_controller/archives/64/2009124922173177/SDA/Hello.jar]
version status: [SAME]
deployment status: [Success]
description: []




===== END DEPLOY RESULT =====


===== Summary - Deploy Result - Start =====
------------------------
Type | Status  : Count
------------------------
 > SCA(s)
 > SDA(s)
   - [Success] : [1]
------------------------
------------------------
Type | Status  : Id
------------------------
 > SCA(s)
 > SDA(s)
   - [Success] : JavaEE_Hello,
------------------------
===== Summary - Deploy Result - End =====

Sorry for these questions, as i am new to it.

Thanks

[former_member189220]

This means that the deployment is possible.

If this is correct

"... I tried the guided in Using Shell Scripts to Work with SDAs using test file Hello.jar (it has been converted and contains SAP_MANIFEST.MF), it failed at first time due to authorizaton issue:

then i tried another user with correct authorization and it works this time and deployed successfully:

and new deployment.0.log and deployment.0.trc is generated in path ..."

then the impediment is in the deployment script or in the format of the file that is necessary to be deployed. (it should be in supported by AS Java formats)

[former_member189220]

Hello Seth,

If this question is answered from your perspective, then please clicked on the “Accept” link to complete this question.

Otherwise, please post the resolution in a separate answer and close the thread.

Thank you.

[former_member189220]

In order to be on the same page, I hope you have created the deployment script as it is explained here:

https://assets.cdn.sap.com/sapcom/docs/2016/06/3e08f751-767c-0010-82c7-eda71af511fa.pdf

Chapter 7.3

If this is so, then you need to cross check whether the deployment call is received by the target deployment AS Java. For this have a look on the deployment.x.trc and deployment.log files in the work directory (\usr\sap\<AS-JAVA-SystemID>\<central instance>\work).

Provided there is reported a deployment error in these logs please post the relevant exceptions to have a closer look.

Else, the call does not get to the AS Java for some reason.

1. Please cross check the deployment settings - f.e. is the deployment call goes to the the correct deployment port. For AS Java 7.0x (and lower) the P4 port is 5xx18, while for AS Java 7.1 (and higher) it is 5xx04 .

2. It is possible that some networking device (firewall, router and etc.) does not allow the call to get to the AS Java. Please make sure the deployment call might be made.

3. If this is fine than the problem might be in the deployment script. For this you will observe more details in the deployment traces and logs on the AS Java and the relevant exceptions in particular. You might cross check this by extracting the non-ABAP archive, create it in format acceptable for deployment and deploy it with TELNET directly. If there is a problem only with the deployment script - the deployment with TELNET should be successful (and you do have a temporary workaround to meet the urgency, when it is at hand)

Please revise this SAP note "1833230 - deployment of j2ee archive which is no SDA is not supported"

and these documents:

http://help.sap.com/saphelp_nw73/helpdata/en/4a/f06fb255332475e10000000a42189c/frameset.htm

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4a/f06fb255332475e10000000a42189c/frameset.htm

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/1e/2c813ed9d23e44e10000000a114084/content.htm?frame...

[Former Member]

Hi Milen,

Thanks for your reply.

• Yes, i have created the deployment script getting from the note 2418818 , i placed the script into /usr/sap/SLJ/SYS/global/CtsScripts with full authorization of read and execution for all user:

  

  the path /usr/sap/SLJ/SYS/global links to the /sapmnt/SLJ/global, hope it's no influence, and here is the value of 'sys.global.dir' property:

  

• I checked the deployment.x.trc and deployment.log files under /usr/sap/SLJ/J02/work:

  
  the final changed time stamp of deploy.0.log and deploy.0.trc is 2017-02-18 , which is not the time i test the deployment, so there is no useful log.

1. As for the setting of deployment port, do you mean the configuration of sm59 http destination 'CTSDEPLOY' ? I set the service no to 50200, i tried to reset to 50208 but it didn't work. here is the details of the instance:
   
2. In my case, both AS abap and AS java are in same server, have same ip address, i think in this situation, the call to get to the AS Java will not be influenced, is it correct ? or there are any place i can check it ?
3. I tried the guided in Using Shell Scripts to Work with SDAs using test file Hello.jar (it has been converted and contains SAP_MANIFEST.MF), it failed at first time due to authorizaton issue:

   then i tried another user with correct authorization and it works this time and deployed successfully:

   and new deployment.0.log and deployment.0.trc is generated in path /usr/sap/SLJ/J02/j2ee/deployment/log
   
   Deployment script is still not executed (i add some code to the script, a new log.txt file should be created when it is executed ), Do you have any idea how to fix it ?
   
   Thank you very much for your help.

4. <Content of deployment.0.log :
   
   
   <!--HELP[Manual modification of the header may cause parsing problem!]/-->
   <!--LOGGINGVERSION[2.0.7.1006]/-->
   <!--NAME[..//./log/deployment.log]/-->
   <!--PATTERN[deployment.log]/-->
   <!--FORMATTER[com.sap.tc.logging.ListFormatter]/-->
   <!--ENCODING[UTF8]/-->
   <!--FILESET[0, 5, 10000000]/-->
   <!--PREVIOUSFILE[deployment.4.log]/-->
   <!--NEXTFILE[deployment.1.log]/-->
   <!--LOGHEADER[END]/-->
   #2.0#2017 08 04 07:23:50:647#+00#Error#/System/Server/Deployment#
   ###C0000AAD0F490000000000003B81A1BC###com.sap.engine.lib.deploy.sda.SDAProducer########Thread[main,5,main]#Plain##
   Incorrect arguments passed#
   
   
   #2.0#2017 08 04 07:25:01:993#+00#Info#/System/Server/Deployment#
   ###C0000AAD0F49000000000000783E6358###com.sap.engine.lib.deploy.sda.SDAProducer########Thread[main,5,main]#Plain##
   Generating SDA file for /tmp/Hello.jar#
   
   
   #2.0#2017 08 04 07:25:02:711#+00#Info#/System/Server/Deployment#
   ###C0000AAD0F49000000000001783E6358###com.sap.engine.lib.deploy.sda.SDAProducer########Thread[main,5,main]#Plain##
   SDA /tmp/SDA/Hello.jar generated successfully#
   
   
   #2.0#2017 08 04 07:29:58:588#+00#Info#/System/Server/Deployment#
   ###C0000AAD0F49000000000000614C5515###com.sap.engine.deployment.DMClient########Thread[main,5,main]#Plain##
   Obtaining Deployment Manager#
   
   
   #2.0#2017 08 04 07:29:59:884#+00#Error#/System/Server/Deployment#
   ###C0000AAD0F49000000000001614C5515###com.sap.engine.deployment.proxy.ConnectionManagerImpl#####aaeb7d71a08410059c57a4ab36b3059d###Thread[main,5,main]#Plain##
   Could not establish connection to AS Java on [localhost:50204]. Cannot authenticate the user. Wrong or missing security credentials (password) for principal [sljadm], or the specified principal has no permissions to perform JNDI related operations.#
   
   
   #2.0#2017 08 04 07:29:59:889#+00#Error#/System/Server/Deployment#
   ###C0000AAD0F49000000000003614C5515###com.sap.engine.deployment.DMClient#####aaeb7d71a08410059c57a4ab36b3059d###Thread[main,5,main]#Plain##
   Error occurred while obtaining Deployment Manager#
   
   
   #2.0#2017 08 04 07:37:44:217#+00#Info#/System/Server/Deployment#
   ###C0000AAD0F49000000000000614C5515###com.sap.engine.deployment.DMClient########Thread[main,5,main]#Plain##
   Obtaining Deployment Manager#
   
   
   #2.0#2017 08 04 07:37:45:409#+00#Info#/System/Server/Deployment#
   ###C0000AAD0F49000000000001614C5515###com.sap.engine.deployment.proxy.ConnectionManagerImpl#####1c0ba546a0f11005cd02a30dc3517bbc###Thread[main,5,main]#Plain##
   Connected to localhost:50204 as i321386#
   
   
   #2.0#2017 08 04 07:37:45:707#+00#Info#/System/Server/Deployment#
   ###C0000AAD0F49000000000002614C5515###com.sap.engine.deployment.proxy.DeploymentProxyImpl#####322bcffda0f11005a9d7d982c9fe7dc6###Thread[main,5,main]#Plain##
   Disconnected from localhost:50204#
   
   
   #2.0#2017 08 04 07:37:46:076#+00#Info#/System/Server/Deployment#
   ###C0000AAD0F49000000000003614C5515###com.sap.engine.deployment.proxy.ConnectionManagerImpl#####4639de02a0f110059abdf226ca4e45b6###Thread[main,5,main]#Plain##
   Connected to localhost:50204 as i321386#
   
   
   #2.0#2017 08 04 07:37:46:409#+00#Info#/System/Server/Deployment#
   ###C0000AAD0F49000000000004614C5515###com.sap.engine.deployment.DMClient#####5a7f38caa0f11005bc0ed078ae54cff8###Thread[main,5,main]#Plain##
   Deploying /tmp/Hello.jar with plan null#
   
   
   #2.0#2017 08 04 07:37:46:434#+00#Info#/System/Server/Deployment#
   ###C0000AAD0F49000100000000614C5515###com.sap.engine.lib.deploy.sda.SDAProducer#####5cc4742ea0f11005816cd1ecd58cf211###Thread[Thread-11,5,main]#Plain##
   Generating SDA file for /usr/sap/SLJ/J02/j2ee/deployment/scripts/../SAP_DM/1501832266389_Hello.jar/Hello.jar#
   
   
   #2.0#2017 08 04 07:37:46:580#+00#Info#/System/Server/Deployment#
   ###C0000AAD0F49000100000001614C5515###com.sap.engine.lib.deploy.sda.SDAProducer#####5cc4742ea0f11005816cd1ecd58cf211###Thread[Thread-11,5,main]#Plain##
   SDA ..//SDA/Hello.jar generated successfully#
   
   
   #2.0#2017 08 04 07:37:53:623#+00#Info#/System/Server/Deployment#
   ###C0000AAD0F49000200000000614C5515###com.sap.engine.deployment.proxy.dc.DCLogger#####94a76657a0f11005a2c192c798e73128###Thread[DC_API-ClientSideAsyncNotification\#1,5,main]#Plain##
   Deployment of [name: 'Hello', vendor: 'JavaEE' (sda)] finished.#
   
   
   #2.0#2017 08 04 07:37:53:719#+00#Info#/System/Server/Deployment#
   ###C0000AAD0F49000100000002614C5515###com.sap.engine.deployment.proxy.dc.DCLogger#####0f9a3d31a0f31005c096eebe29b15da8###Thread[Thread-11,5,main]#Plain##
   +++ Deployment of session ID [61] finished with status [Success] +++. [[ deployerId=1 ]] [[\#4: 6.589 sec]] [
   ===== Summary - Deploy Result - Start =====
   ------------------------
   Type | Status  : Count
   ------------------------
    > SCA(s)
    > SDA(s)
      - [Success] : [1]
   ------------------------
   ------------------------
   Type | Status  : Id
   ------------------------
    > SCA(s)
    > SDA(s)
      - [Success] : name: 'Hello', vendor: 'JavaEE', 
   ------------------------
   ===== Summary - Deploy Result - End =====
   ]#
   
   
   #2.0#2017 08 04 07:37:53:843#+00#Info#/System/Server/Deployment#
   ###C0000AAD0F49000100000003614C5515###com.sap.engine.deployment.DMClient#####106da96ba0f310059f359badd8b3b846###Thread[Thread-11,5,main]#Plain##
   Received progress event for operation distribute#
   
   
   #2.0#2017 08 04 07:37:53:844#+00#Info#/System/Server/Deployment#
   ###C0000AAD0F49000100000004614C5515###com.sap.engine.deployment.DMClient#####106da96ba0f310059f359badd8b3b846###Thread[Thread-11,5,main]#Plain##
   Progress event state running#
   
   
   #2.0#2017 08 04 07:37:53:906#+00#Info#/System/Server/Deployment#
   ###C0000AAD0F49000100000005614C5515###com.sap.engine.deployment.operations.DistributeOperation#####17a3bd8fa0f3100593c9d56b394c80c0###Thread[Thread-11,5,main]#Plain##
   Target module JavaEE/Hello @ Server 00 02_251897 - 25189750 distributed successfully#
   
   
   #2.0#2017 08 04 07:37:53:906#+00#Info#/System/Server/Deployment#
   ###C0000AAD0F49000100000006614C5515###com.sap.engine.deployment.DMClient#####17a3bd8fa0f3100593c9d56b394c80c0###Thread[Thread-11,5,main]#Plain##
   Received progress event for operation distribute#
   
   
   #2.0#2017 08 04 07:37:53:906#+00#Info#/System/Server/Deployment#
   ###C0000AAD0F49000100000007614C5515###com.sap.engine.deployment.DMClient#####17a3bd8fa0f3100593c9d56b394c80c0###Thread[Thread-11,5,main]#Plain##
   Progress event state completed#
   
   
   #2.0#2017 08 04 07:37:53:907#+00#Info#/System/Server/Deployment#
   ###C0000AAD0F49000000000005614C5515###com.sap.engine.deployment.DMClient#####5a7f38caa0f11005bc0ed078ae54cff8###Thread[main,5,main]#Plain##
   Deployed modules#
   
   
   #2.0#2017 08 04 07:37:53:907#+00#Info#/System/Server/Deployment#
   ###C0000AAD0F49000000000006614C5515###com.sap.engine.deployment.DMClient#####5a7f38caa0f11005bc0ed078ae54cff8###Thread[main,5,main]#Plain##
   	JavaEE/Hello @ Server 00 02_251897 - 25189750#
   
   
   #2.0#2017 08 04 07:37:53:907#+00#Info#/System/Server/Deployment#
   ###C0000AAD0F49000000000007614C5515###com.sap.engine.deployment.DMClient#####5a7f38caa0f11005bc0ed078ae54cff8###Thread[main,5,main]#Plain##
   Modules will not be started#
   
   
   #2.0#2017 08 04 07:37:54:022#+00#Info#/System/Server/Deployment#
   ###C0000AAD0F49000000000008614C5515###com.sap.engine.deployment.proxy.DeploymentProxyImpl#####1e5a91c5a0f31005c4c59e6b07c01ea5###Thread[main,5,main]#Plain##
   Disconnected from localhost:50204#<strong>
   
   </strong>