SDM-remote access

[Former Member]

Hi ,

Is there any way of accessing SDM remotely

like visual administrator or log configurator.

will give points for helpful answers.

Thanks

Rocky

[Former Member · Accepted solution]

Hi,

Thanks for you replies..

To use remote SDM.GUI i still the remote server still needs

WAS installed on it right..?

Can the remote gui be installed seperately(without WAS) like visual admin,

logviewer etc.

Please reply..

will definitely reward points for helpful answers.

Thanks

Rocky

[praveenkumar_kadi · Accepted solution]

Hi,

SDM is just a java program, if you check what is required to use it as remotely, the following are the required confgiuration to run SDM from remote

1>If you open remoteGUI.bat you would find

-@set sdm_gui_options=-Dsun.java2d.noddraw=true -Duser.language=en

@call "C:\usr\sap\<SID>\JC<IID>\SDM\program\<b>sdm_prep_com.bat</b>"

%sdm_com% remotegui "sdmhome=C:\usr\sap\<SID>\JC<IID>\SDM\program"

@pause

2>if you check "sdm_prep_com.bat"

you find

@call "C:\usr\sap\<SID>\JC<IID>\SDM\program\<b>sdm_jdk.bat</b>"

set sdm_memory_switch=-Xmx%sdm_heap_size%M

set sdm_com="%sdm_java_home%\bin\java" %sdm_64bit_switch% %sdm_memory_switch% %sdm_gui_options% -jar "C:\usr\sap\<SID>\JC<IID>\SDM\program\bin\<b>SDM.jar</b>"

3>If you check "sdm_jdk.bat", It points to

set sdm_java_home=<b>C:/j2sdk1.4.2_12</b>

set sdm_64bit_switch=

set sdm_heap_size=256

So, In conclusion,

You need to have

1>sdm.jar

2>JDK installed

3>pointer to SAP ID home

4>batch files as shown in above

>some memory configurations

If you are able to configure accordingly, then you can use SDM remotely without actually installing WAS on remote machine

Hope that helps also reward if it....

[vijayakhanna_raman · Accepted solution]

Hi,

Think that will work if u have a copy of SDM folder. That would contain all the jars SDM GUI needs to load but don't know if u can do that. But I hope it can work fine.

Regards,

Vijai

[Former Member · Accepted solution]

Thanks a ton Praveen.

have rewarded points.

Thanks

Rocky

[Former Member]

Hi rocky,

<u><b>Starting the SDM GUI</b></u>

If you have started the SDM as a server (see Starting and Stopping the SDM Server above),

then you can call a remote GUI with which you can operate the server. The SDM Server and

the remote GUI can run on different hosts, however they must be connected by a network

connection. Use the command remotegui to start the remote GUI:

sdm remotegui

Since there is no current separate installation for the GUI, you must perform a complete SDM

installation even if you only want to start the remote GUI on the host.

Besides the remote GUI there is also a second SDM GUI variant. In this variant, the GUI and

the SDM Server run in the same process. This process must run on the host where the SDM

Repository is located. Use the command gui to start this GUI:

sdm gui sdmhome=<...>

During the SDM installation, several scripts are generated in the sdm_home directory. These

scripts can be used to call the GUI and the remote GUI.

• startSDM.bat (for GUI), RemoteGui.bat (for remote GUI) (Windows)

• startSDM.sh (for GUI), RemoteGui.sh (for remote GUI) (Unix)

Note:

We intend to separate the SDM Server functions from the GUI functions, which is why we

recommend that you use the remote GUI variant. In the long term, the second GUI variant

will become obsolete.

<u><b>Deploying SDAs and SCAs</b></u>

Unlike SDM 6.20, the deployment of SDAs or SCAs with the SDM <b>Command Line Interface</b> is

now a one-step process. You can deploy archives with a single command:

sdm deploy file=<...>|list=<...>|softwaretype=<...>

[updateversions=lower|samelower|all]

[onerror=stop|skipdepending|ignore]

where

• file: Name of an SDA/SCA that you want to deploy with the SDM. You cannot

specify the list or softwaretype parameter if you use the file parameter. This

means that the execution of the deploy command with this parameter can be used

to deploy precisely one SDA/SCA.

• list: Name of a text file that contains the names of the SDAs/SCAs that you want

to deploy. You cannot use the file or softwaretype parameter if you specify this

parameter. This means that the execution of the deploy command with this

parameter can be used to deploy multiple SDA/SCAs simultaneously.

• softwaretype (since 6.30 SP7): Name of a software type. All SDAs currently

deployed for the specified software type will be deployed again. If some of the SDAs

that are currently deployed cannot be accessed in the SDM root directory,

deployment aborts with an error message. You cannot specify the file or list

parameters if you use the softwaretype parameter.

• updateversions: Determines the comparison of versions between a deployed

SDA/SCA and the new SDA/SCA. lower indicates that a deployed SDA/SCA can be

updated only if its version is lower than the SDA/SCA specified in the command.

lower is the default value of this parameter, which means it is used automatically if

the parameter is not specified with the deploy command. samelower, however,

lets you deploy a version that has already been deployed. all permits an update

regardless of the version of the deployed SDA/SCA.

• onerror: Optional parameter that controls the responses to an error. stop (default)

stops the deployment after the first deployment error. Any missing SDAs/SCAs are

not deployed. skipdepending continues the deployment after a deployment error,

but only for any missing SDAs/SCAs that do not have dependencies on the

deployment with the error. ignore continues the deployment with any SDAs/SCAs

that are still missing. Only experts should select the last option, since this can cause

inconsistencies in the target systems. Currently, the parameter onerror is only used

for errors in the actual deployment. For example, if a specified SDA/SCA cannot be

found or read, or if dependencies between SDAs cannot be resolved, then the

deployment always stops with an error message.

If, for some reason, you cannot deploy the SDAs/SCAs (missing target system, incompletely

configured target system, unknown substitution variable, missing value for a substitution

variable, SDA/SCA version cannot be deployed) an error occurs – you can find details on the

cause of the error in logfile.

Thanks,

Tanuj

[praveenkumar_kadi]

Hi,

There are many ways to access SDM remotely..see below

1>Using NW Developer Studio

2>Deploy Tool

3>Using Script like Ant

4>Using a Java Program

...

Using batch files..

Through SDM in your machine (Giving IP address and port--port should be free and open)

......

Using Telenet..etc

......

...

You can refer following document on how exactly you are going to access SDM remotely(code examples)

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1ca44e78-0801-0010-fa9d-a76...

also look at this forum

Hope that ends your search here

[Former Member]

Hi rocky,

chk this link may help u

Thanks

Srinivas

[Former Member]

Hi

We can run the remotegui.bat batch file in SDM's location through a VNC.I can see only this option here....Is there anything else you are looking for?

[Former Member]

Remote Desktop or VNC to the server and run RemoteGui.bat I know its probably not the answer you were looking for!