Using scripts in app v

You can run scripts in app-v so as to have some functions which cannot be achieved otherwise . Scripts can be also used to set up particular configurations that a program may require to run correctly.

For troubleshooting purposes, copy the osd-file from the content folder for example the local drive of the computer. Make changes in the OSD-file only in this copy!!

You can add a script from the .osd file of a SoftGrid-enabled program to a client that has the necessary interpreter installed.
To include a script in an .osd file, you must determine the following:
• When the script runs
• Where the script runs
• How the script runs

All scripts must be added between the tags in an .osd file. You can refer to an existing script by its file name. Or, you can enter the exact syntax of the commands in the script section.

When the script runs
You can use the .osd file to run scripts at various times during the startup of SoftGrid-enabled programs. The "SCRIPT TIMING and EVENT" setting in the script comes first. Under this setting, the following attributes determine when the script runs:
• PRE STREAM
This attribute runs the script before the program starts streaming. For example, use this attribute when you have to open a virtual private network (VPN) connection to the SoftGrid server before you run the program.
• POST STREAM
This attribute runs the script after authorization and after the program starts streaming but before the Virtual Environment is set up.
• PRE LAUNCH
This attribute runs the script inside the virtual environment before the program runs.
• POST LAUNCH
This attribute runs the script after the program is started.
• POST SHUTDOWN
This attribute runs the script after the program is shut down. For example, use this attribute to clean up configuration settings or to delete configuration files.

Where the script runs
The script can run in the following two locations:
• In the Virtual Environment
• Outside the Virtual Environment
Set the PROTECT attribute as follows:
• PROTECT=True
This setting configures the script to run in the Virtual Environment. You can use this setting to run scripts that are used to troubleshoot issues.
• PROTECT=False
This attribute configures the script to run outside the Virtual Environment. For example, you can use this setting to run scripts that copy files locally to the client.

How the script runs
The TIMEOUT attribute determines the following:
• Whether the SoftGrid client waits for the script to finish
• The period that the SoftGrid client will wait for the script to finish
Set these attributes as follows:
• TIMEOUT=x
The client will wait x seconds for the script to finish before the client returns an error.
• TIMEOUT=0
The client will wait indefinitely for the script to finish.

• Wait=False
The client will continue without waiting for the script to finish.
• Wait=True
The client will not start the next step until the script finishes.

Comments

  1. Very useful. It's provide better corporate deployment and provides a standard format for component management to customers. msi application packaging

    ReplyDelete
  2. they should get rid of harell becuz he is a major bust that was one of the worst picks ive ever seen. then in free agency or later in the draft get some good o-linemen to get some depth and to develope.

    movers geneva il

    ReplyDelete

Post a Comment

Popular posts from this blog

App v for Java Runtime Environment

app v for mindjet mindmanager

Structure of MSI package