Remote execute sapevt

[former_member204618]

Hi All,

We would like to use sapevt to raise an event to trigger our process chains in BI from a remote system.

We only want our process chains triggered once we know the remote system has completed it's load so the above program was chosen.

My question is simply this, what port/s do we need to open on our firewall between the 2 systems in order for this to work?

Thanks

Craig.

[Former Member]

That depends on what OS your remote hosts run. sapevt has to run on one of your app servers. It is a standalone executable program.

If youre using Unix hosts your could use ssh user@hostname /usr/sap/<SID>exe/run/sapevt <SID> <EVENT>

For windows hosts youre gonna need some other way of kicking the program off remotely ( ssh for windows comes to mind )

So to answer your question.... It depends, if youre using ssh, then u need to open port 22 and create a public/private keypair for passwordless authentication.

[former_member204618]

Thanks for the reply.

What we were trying to achieve was to run the sapevt program directly from the remote machine (in our case OS is AIX) which we know we can do. What we don't know is what port does this program send it's communication on.

The option to login to our system remotely unfortunately is not an option but opening up the required port was.

This is now no longer needed but an answer nonetheless would be nice.

Thanks

Craig.

[Former Member]

Requirements for Using SAPEVT
To use SAPEVT to trigger an event, the following requirements must be met: 
An R/3 instance that offers background processing must be running or the start of jobs waiting on the event will be delayed. 
If no instance in an R/3 System is active when an external program triggers an event, than the event is ignored, the R/3 System will not know that the event has occurred. 
If a job that was scheduled to run when an event occurs cannot be started immediately, it is rescheduled as an immediate-start job. It will then be run at the earliest possible opportunity. 
If SAPEVT is started with a profile name as an argument, then the program must have access to the shared profile directory of the R/3 System. SAPEVT needs to read the profile of the system to which it is sending the event. 
If access to the directory is not possible, then you can create a local profile for SAPEVT. This profile need only contain values for the parameters rdisp/mshost and rdisp/msserv. Take the values from the profiles of the target R/3 System. Specify the local profile in the SAPEVT command line. 
Network connection: SAPEVT must be able to establish a TCP connection to the R/3 instance. 
SAPEVT reports problems in establishing a connection to the R/3 System in its log file. 
User search path: The R/3 executables and profile directories must lie in the search path of the user who starts the program that calls SAPEVT. 
UNIX: /usr/sap/<R/3 System ID>/SYS/exe/run and SYS/profile 
Windows NT: 
<Host Name>\sapmnt\<R/3 System ID>\SYS\exe\run and SYS\profile 

It would guess its a gateway connection so it would 33<instance number>/tcp