As of SAP Process Integration 7.1 we cannot use *SDM *anymore to deploy our java packages,
instead we need to use either JSPM (*Java Support Package Manager*) or deploy them from Netweaver Developer Studio. However sometimes we don't have access to NWDS and JSPM may also be unavailable for some reasons. Is there any help for us in this case? It turns out there is another possibility - we can use telnet service from *J2EE engine* and deploy the files with it's use. by using *man -h* as shown in the screenshot below: {code:html}
{code} As you can see only some of them are activated by default (you can activate all if you need them) but DEPLOY is among the activated by default. 4. In order to check how DEPLOY command works use *DEPLOY -h* {code:html}
{code} 5. Finally you can deploy the java archive (for example JMS/JDBC driver)
instead we need to use either JSPM (*Java Support Package Manager*) or deploy them from Netweaver Developer Studio. However sometimes we don't have access to NWDS and JSPM may also be unavailable for some reasons. Is there any help for us in this case? It turns out there is another possibility - we can use telnet service from *J2EE engine* and deploy the files with it's use. by using *man -h* as shown in the screenshot below: {code:html}
{code} As you can see only some of them are activated by default (you can activate all if you need them) but DEPLOY is among the activated by default. 4. In order to check how DEPLOY command works use *DEPLOY -h* {code:html}{code} 5. Finally you can deploy the java archive (for example JMS/JDBC driver)
7 Comments
