Once you’ve built a new com.sap.aii.adapter.lib.sda file ready for deployment into the SAP AS Java, you have two options for deployment in a NW 731 system:
– Deploy using SUM
– Deploy using Telnet
The SUM method can be arduous, taking anywhere from 20 minutes to over a couple of hours if you don’t already have the software.
Using Telnet is the lowest common denominator, uses existing software already installed and can take as little as 5-10 minutes.
As the <sid>adm user on the AS Java application server, use Telnet (must be installed on the Unix, Linux or Windows O/S, to perform the deployment:
sidadm>
telnet 127.0.0.1 5<##>08Administrator
<pw>
Once connected, you can query the version of the SDA:
explore name=com.sap.aii.adapter.lib
Development Component:
name: [com.sap.aii.adapter.lib], vendor: [sap.com], location: [SAP AG], version: [7.3113.20140808110905.0000], software type: [primary-library], csn component: [BC-XI-CON-AFW], dependencies: [[name: ‘engine.j2ee14.facade’, vendor: ‘sap.com’]], archive type: [DC]
Then deploy your new SDA file:
deploy /tmp/sap.com_com.sap.aii.adapter.lib on_deploy_error=stop version_rule=all
Notice that you are disconnected from Telnet at this point.
You should wait around 5-10mins, then re-connect into Telnet as Administrator, then run get_result:
>
get_resultThe status of the deployed SDUs is Success.
Additional information:
[sdu id: [sap.com_com.sap.aii.adapter.lib]
sdu file path:
/usr/sap/<SID>/J##/j2ee/cluster/server1/temp/tc~bl~deploy_controller/archives/124/1416245030759972000/com.sap.aii.adapter.lib.sda]
version status: [SAME]
deployment status: [Success]
description: []
That’s it.
