Validate OpenDeploy Receiver

Hi All,

Am new to OpenDeploy, Can you please let us know how to validate that the OpenDeploy Receiver is installed successfully.. And i want publish sample application incommand prompt. Can any one guide us to do this..

Find more posts tagged with

Comments

nipper

run iwodserverstatus:

/opt/OpenDeployNG/bin/iwodserverstatus
OpenDeploy server host: localhost, RMI registry port: 9173
OpenDeploy server is alive.
1 deployment is currently active.

Works on the server and receiver

Adam Stoller

Personally, I usually create a copy of the OOTB test.xml on the Base Server - call it something like test_remote.xml - and modify it to use a replicationFarm that includes the new Receiver(s) and then initiate the deployment from the command line on the Base Server via:

iwodcmd start test_remote

If it says it succeed, and you can see some files in ODHOME/tmp/ on the Receiver(s) - you know they are set up correctly and working.

NareshT

Thanks for the reply guys..

I would likehave more iinfo... Please let us know we are on the right track..

1. We have installed OpenDeploy Base Server and validate by hitting the URL somethinglike

http://localhost:8081/iw-cc/opendeployservice/login Using OpenDeploy Admin UI.. We are able to login successfully..

2. Do we have any URL to validate the same for Receiver too apart from Command Prompt.. If so please let us know..

Thanks in Advance

NareshT

Thanks Mate..

Can you please give us more info on it if you dont mind.. As am very new to this tool...

Thanks in Advance

Naresh T

Adam Stoller

The OD Admin UI may be able to connect to the Receiver - but more often than not, it won't do so successfully, especially if there is a firewall between the two servers (there are settings one can use to tunnel through in this kind of environment but, quite frankly, I almost never use the OD Admin UI - I find telnet / RDP generally better)

If you want to just "ping" the receiver to make sure it's alive and accepting connections you can try:

telnet receiver-server 20014

Where 20014 is the default deployment port - if you've changed it use whatever you changed it to.

If telnet comes back with an error it means that there's a problem connecting to the OpenDeploy server (receiver or base server, though more often this is used to verify the receivers)

If you get no response - don't worry - that's expected - it means that you were able to connect. OpenDeploy uses its own proprietary connection protocol and does not provide any user-usable prompts. Just exit the connection (usually something like <escape>-[) and quit telnet.