Informatica - Access Unix server from Windows client - informatica

In Informatica, What are the different ways to connect Unix server from Informatica Windows client?

If informatica server is sitting on Unix, you can create a command task with the following:
set >/tmp/informatica.task.out
And then check the output in your Unix file.
Also, you can run an ssh command from that machine to reach additional servers.
This is just a couple of thoughts from the top of the head.

Related

Authenticate remote host to run ms-mpi process

I want to distribute some tasks over machines over a local network.
I tried to run mpi on remote machine but it can't connect although i make sure they can talk with each other by ping.
I use MS-MPI v9 and windows 10
I solved it by setting the same user name and password on the remote machine.
Another way i found is making all the machines in the same domain.

C++: Remotely hibernate a PC

How can I hibernate a Windows machine that runs Windows 7 or 8 over my LAN from another PC?
Is there a WinAPI function for that? Or do I have to send special magic packets or something like this?
All I know is that PsShutdown.exe is able to do it (allegedly. I haven't tried it).
I don't want to use third party libraries and I also don't want to run a service on the computer that is supposed to get hibernated. I want to use the existing mechanism.
I'd also like to know if I need to change specific settings on the target computer.
I'm not sure if that's important, but shutdown /s /m \\ComputerName did not work on my target PC.
The TechNet document Restart or Shut Down a Remote Computer and Document the Reason describes the requirements to use the shutdown.exe command against a remote computer.
In order to use this feature, the Remote Registry service must be enabled on the remote computer.
Access to the Remote Registry or membership in the Administrators group on the remote computer is the minimum required to complete this procedure
To the best of my knowledge, the only way to remotely hibernate a machine is to use the same method that psshutdown does: copy an executable to the remote machine and install it as a system service.
The OpenSCManager API allows you to specify a target computer, and you can use the handle it returns to call CreateService and then StartService. The service can delete itself once it has done its work.

Starting sas job from remote computer

I have a scheduling program running on Server A running Windows 2008 RS. Server B is my SAS server under Windows 2008 R2. How do I kick-off a job on SAS server from my scheduling server? I can either use the sas.exe or a batch file to start my job. Owners of the SAS server tell me that I cannot add an application or Windows service to the SAS server. Is this even possible?
Below is a copy of my answer to a slightly different question (source: http://www.runsubmit.com/questions/260/hide-sas-batch-jobs-winxp). I'm copy/pasting it here for perpetuity and also because it's more likely to help people searching:
You can use PsExec which is part of Microsoft/Sysinternals list of utility programs. This file will go on the scheduling server. Grab it from here:
http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
The tool is designed to allow you to execute jobs on remote machines. For example, if you want to launch a SAS program from the command line you could run:
psexec \\machinename sas.exe -sysin remotedrivename:\remotefolder\myprogram.sas
This would launch SAS.EXE on the remote machine and run the supplied program that exists on the remote machine. When it launches SAS it appears to launch it within a PsServ service. Because it's running within a service no interface will be displayed. I'm not even sure if you would see it appear as it's own process or application in windows task manager. If you use SysInternals other program, ProcessExplorer, instead of Task Manager you can see this happening.
Note that the REMOTE MACHINE and the LOCAL machine can be the same machine.
PROS: Many other uses for this technique. It's free. PsExec is only required on the machine that is making the call, not both machines.
CONS: Its a bit of a roundabout way to do things. Need to install a third party program (although it is now a MS tool). Some antivirus programs/network admins may not allow it.
Note that if your SAS jobs access network resources then you will probably need to make the network resource available first using the net map command. I suggest running your sas job in a batch file like so (or use the 'x' command from within your SAS file to call the 'net use' commands):
Command executed from local machine:
psexec \\machinename -sysin remotedrivename:\remotefolder\myprogram.BAT
Contents of batch file on remote machine:
net use m: \\fileserver\sharedfolder /USER:mynetworkdomainname\myusername mypassword
sas.exe -sysin remotedrivename:\remotefolder\myprogram.sas
net use m: /delete

How to transfer and execute .exe(py2exe) file in remote windows machines in a network using python

I have a set of python files which takes the information from windows registry,I have converted these files in to a .exe using py2exe.Now I need to scan the network and detect the active endpoints in it, after detecting the endpoint/machines in the network I need to send this .exe to to the machines and make it execute.How to do this in python.I have a code for transfer of files,My problem is how to execute the .exe file in remote windows machine (I have the credentials of the machine)& get back the results to the server?
I need to accomplish this task using python.
Any help or suggestions please.
Thanks in advance

How to run .exe binary of a remote server on the remote server from a c++ application in windows platform

What are the ways to run .exe binary of a remote server on the remote server from a c++ application in windows platform??
Open a telnet session to the server, start binary.
open a telnet session (like MSalters suggests), or write a small server app that will run on the remote server, and listen for your its mother application's request to run that ".exe binary".
What you are doing sounds exactly like what psexec already does. So you could either shell out to that or re-implement how it works. There are some descriptions of what it actually does:
http://windowsitpro.com/article/articleid/42919/psexec.html (I believe I read this in the past, but it's behind a paywall now)
http://www.ntkernel.com/w&p.php?id=15