• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

Web service programming

Collapse
X
  •  
  • Filter
  • Time
  • Show
Clear All
new posts

    Web service programming

    I need to run a .bat file on a remote windows server. I can do it, I think, from unix using e.g. rsh -l user_name windows_host_name "C:\blah\trigger.bat". However, I'd get this all to work by consuming a webservice on the windows server.

    I guess I'd have a program (a dll?) running on the windows server that when it receives the request, runs the bat file.

    Is there any language that would be particularly suited to this task?
    Down with racism. Long live miscegenation!

    #2
    Does it need to run from a user action or can you schedule it under the 'at' command?

    Comment


      #3
      Can you not set up a scheduled task? Or if it needs to be run adhoc try psexec
      Originally posted by Stevie Wonder Boy
      I can't see any way to do it can you please advise?

      I want my account deleted and all of my information removed, I want to invoke my right to be forgotten.

      Comment


        #4
        Also you can't rsh to a windows box unless it's running rshd.

        Comment


          #5
          Originally posted by stek View Post
          Does it need to run from a user action or can you schedule it under the 'at' command?
          It can't be scheduled. It'll be triggered from the remote system.

          The full process is:

          Two servers - one Windows running a bespoke legacy windows application, one Unix running SAP. The windows app generates data which is passed to the unix server's directories. SAP detects the arrival of the file, and does some processing. At the end of that processing, the .bat file must run on the the Windows server. It's the last step I want to automate. (at the moment, some chaps in India monitor the SAP process and send an email when it's finished).

          I want to use a web service as it is an easy way for one system to call another, without having to worry unduly about technologies in between.
          Down with racism. Long live miscegenation!

          Comment


            #6
            This can easily be consumed within a WCF service. Are you in control of permissions on the windows box? as the account the app pool runs under will need access to the bat file.

            Comment


              #7
              I can get admin access to the windows box.
              Down with racism. Long live miscegenation!

              Comment


                #8
                Originally posted by stek View Post
                Also you can't rsh to a windows box unless it's running rshd.
                I believe rsh is being phased out as it's insecure. Installing sshd on Windows is trivial.
                <Insert idea here> will never be adopted because the politicians are in the pockets of the banks!

                Comment


                  #9
                  It's been decided that a web service is the best way forward - allow access to all sorts of other applications. WCF looks promising.
                  Down with racism. Long live miscegenation!

                  Comment


                    #10
                    Originally posted by petergriffin View Post
                    I believe rsh is being phased out as it's insecure. Installing sshd on Windows is trivial.
                    Feck me.

                    It was banned for being insecure at the place I was in 15 years ago.

                    Passwords in the clear, among other sins, if I remember correctly.

                    Warning from a decade ago

                    RSH is convenient, but it has some serious security shortcomings. Like Telnet and FTP, RSH traffic is passed as clear text. If you connect to a server via rlogin and su to the root account, you're sharing that root password with anyone who happens to be listening in on your traffic.
                    Behold the warranty -- the bold print giveth and the fine print taketh away.

                    Comment

                    Working...
                    X