Open Mobile can be configured to automatically launch other applications or scripts, before, during or after the Open Mobile connection process. Examples of event actions could include launching an anti-virus definition update, running a script to change firewall rules, or opening a browser window to a company Intranet. Most actions will launch a single application, but complex actions can be constructed by configuring multiple event actions to run a succession of applications.
You configure Event Actions in the Open Mobile Portal.
Event action type indicates when it will be triggered.
Event actions come in these types:
| Type | Action Will Run… |
|---|---|
| On Startup of User Interface | When the client’s graphic user interface is opened. |
| Before Establishing an Internet Connection | Before Open Mobile establishes a connection to the Internet. |
| Before Detecting the Internet on a New Connection | After the Internet connection has been initiated but before the Internet connection is complete. |
| After Establishing an Internet Connection | After Open Mobile establishes a connection to the Internet. |
| Before Establishing a VPN Connection | After the VPN connection has been initiated but before the VPN connection is complete. |
| After Establishing a VPN Connection | After the VPN is connected. |
| After Establishing a Corporate Network Connection | After connecting to a Corporate Network. |
| Before Disconnecting a VPN Connection | After the VPN has been disconnected but before the VPN disconnection is complete. |
| After Disconnecting a VPN Connection | After the VPN has been disconnected. |
| Before Disconnecting an Internet Connection | After an Internet connection has been disconnected but before the Internet disconnection is complete. |
| After Disconnecting an Internet Connection | After Open Mobile disconnects from the Internet. Note: Only supported by Windows 1.4.1 and later clients for non-DSL connections. |
| When the User Cancels a Connection Attempt | After the user cancels a connection attempt. (Not yet implemented.) |
| When User Exits the User Interface | After Open Mobile is exited. |
Event actions include the following settings:
| Settings | Description |
|---|---|
| Application Path | Path of the selected application, script, or URL. Path supports Windows environmental variables, but these must be specified in the format $$ENV:<VARIABLE NAME>$$, where <VARIABLE NAME> is the name of the environmental variable. Examples, $$ENV:systemroot$$\system32, $$ENV:USERPROFILE$$, $$ENV:PROGRAMDATA$$ (on Windows Vista or Windows 7). |
| Executable File Name | Name of the executable to be launched. |
| Arguments | Applicable command-line arguments, if any. |
| Frequency | Decide on the frequency at which the action should be executed: every time Open Mobile connects, once per day, or each time Open Mobile is started. |
| Run Context | Specify system or user context for the action to run in. |
| Run Mode | Wait: wait for the configured application to exit before establishing the connection. |
| Don’t Wait: don’t wait for the configured application to exit before establishing the connection. | |
| Connection Type | Event actions can be triggered on specified connection types. |
For more information on configuring Event Actions in a profile, see Event Actions.
Go to: Open Mobile for Windows Help