Differences
This shows you the differences between the selected revisions of the page.
| 2014-09-11 | 2014-09-11 | ||
| in-page anchored links without page name (martin) | fixing links to implementation section (martin) | ||
| Line 11: | Line 11: | ||
| WebJob is a package that contains your job executable (e.g. a batch file or a console application) along with all supporting files (script, WinSCP executable, WinSCP .NET assembly, etc). Azure platform automatically tries to detect what executable is the main one. To ease this, you should name the main executable ''run.*'', e.g. ''run.bat'' for a batch file. | WebJob is a package that contains your job executable (e.g. a batch file or a console application) along with all supporting files (script, WinSCP executable, WinSCP .NET assembly, etc). Azure platform automatically tries to detect what executable is the main one. To ease this, you should name the main executable ''run.*'', e.g. ''run.bat'' for a batch file. | ||
| - | See [[#powershell|implementation sections]] below for examples of the package contents. | + | See [[#implementation|implementation sections]] below for examples of the package contents. |
| ===== [[deploying]] Deploying WebJob ===== | ===== [[deploying]] Deploying WebJob ===== | ||
| Line 40: | Line 40: | ||
| | ''WEBSITE_SITE_NAME'' | Web site name | | | | ''WEBSITE_SITE_NAME'' | Web site name | | | ||
| - | When the WebJob is executed, its files are cloned to a temporary folder (see ''WEBJOBS_PATH'') and the job is run there. So it makes no sense to store any data to job's working directory, as that is not persistent and is not accessible remotely. Use ''WEBROOT_PATH'' to locate either job's master directory (''%WEBROOT_PATH%\App_Data\jobs\%WEBJOBS_TYPE%\%WEBJOBS_NAME%'') or ''WEBJOBS_DATA_PATH'' to locate job's data directory. See [[#powershell|implementation sections]] below for examples. | + | When the WebJob is executed, its files are cloned to a temporary folder (see ''WEBJOBS_PATH'') and the job is run there. So it makes no sense to store any data to job's working directory, as that is not persistent and is not accessible remotely. Use ''WEBROOT_PATH'' to locate either job's master directory (''%WEBROOT_PATH%\App_Data\jobs\%WEBJOBS_TYPE%\%WEBJOBS_NAME%'') or ''WEBJOBS_DATA_PATH'' to locate job's data directory. See [[#implementation|implementation sections]] below for examples. |
| ===== [[log]] Copying Session Log to Job Log ===== | ===== [[log]] Copying Session Log to Job Log ===== | ||
| Line 46: | Line 46: | ||
| The standard output of the job is redirected to a log file which you can display on Azure Management Portal. | The standard output of the job is redirected to a log file which you can display on Azure Management Portal. | ||
| - | It is useful to have WinSCP session log file included into the job's log. For that as the last step of the job, print the WinSCP session log to the standard output. See [[#powershell|implementation sections]] below for examples. | + | It is useful to have WinSCP session log file included into the job's log. For that as the last step of the job, print the WinSCP session log to the standard output. See [[#implementation|implementation sections]] below for examples. |
| To display the job log, go to //WebJobs// tab of your web site page on Azure Management Portal and click on a link in //Logs// column of the job. | To display the job log, go to //WebJobs// tab of your web site page on Azure Management Portal and click on a link in //Logs// column of the job. | ||