Batch Services Quick Start Guide

Intergraph Batch Services
Quick Start Guide
Version 6.1.9
Wednesday, November 16, 2016
Copyright
Copyright © 1994-2016 Intergraph® Corporation. All Rights Reserved. Intergraph is part of Hexagon.
Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains
confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade secret law, and
international treaty, and may not be provided or otherwise made available without proper authorization from Intergraph Corporation.
U.S. Government Restricted Rights Legend

Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was
developed at private expense and is "restricted computer software" submitted with restricted rights in accordance with
subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal
Acquisition Regulations ("FAR") and its successors, and is unpublished and all rights are reserved under the copyright laws of the
United States. For units of the Department of Defense ("DoD"): This is "commercial computer software" as defined at DFARS
252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3.
Unpublished - rights reserved under the copyright laws of the United States.
Intergraph Corporation
305 Intergraph Way
Madison, AL 35758
Documentation
Documentation shall mean, whether in electronic or printed form, User's Guides, Installation Guides, Reference Guides,
Administrator's Guides, Customization Guides, Programmer's Guides, Configuration Guides and Help Guides delivered with a
particular software product.
Other Documentation
Other Documentation shall mean, whether in electronic or printed form and delivered with software or on Intergraph Smart Support,
SharePoint, or box.net, any documentation related to work processes, workflows, and best practices that is provided by Intergraph
as guidance for using a software product.
Terms of Use
a. Use of a software product and Documentation is subject to the End User License Agreement ("EULA") delivered with the
software product unless the Licensee has a valid signed license for this software product with Intergraph Corporation. If the
Licensee has a valid signed license for this software product with Intergraph Corporation, the valid signed license shall take
precedence and govern the use of this software product and Documentation. Subject to the terms contained within the
applicable license agreement, Intergraph Corporation gives Licensee permission to print a reasonable number of copies of the
Documentation as defined in the applicable license agreement and delivered with the software product for Licensee's internal,
non-commercial use. The Documentation may not be printed for resale or redistribution.
b. For use of Documentation or Other Documentation where end user does not receive a EULA or does not have a valid license
agreement with Intergraph, Intergraph grants the Licensee a non-exclusive license to use the Documentation or Other
Documentation for Licensee’s internal non-commercial use. Intergraph Corporation gives Licensee permission to print a
reasonable number of copies of Other Documentation for Licensee’s internal, non-commercial use. The Other Documentation
may not be printed for resale or redistribution. This license contained in this subsection b) may be terminated at any time and
for any reason by Intergraph Corporation by giving written notice to Licensee.
Disclaimer of Warranties
Except for any express warranties as may be stated in the EULA or separate license or separate terms and conditions, Intergraph
Corporation disclaims any and all express or implied warranties including, but not limited to the implied warranties of merchantability
and fitness for a particular purpose and nothing stated in, or implied by, this document or its contents shall be considered or deemed
a modification or amendment of such disclaimer. Intergraph believes the information in this publication is accurate as of its
publication date.
The information and the software discussed in this document are subject to change without notice and are subject to applicable
technical product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document.
The software, Documentation and Other Documentation discussed in this document are furnished under a license and may be used
or copied only in accordance with the terms of this license. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL
EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.
Intergraph is not responsible for the accuracy of delivered data including, but not limited to, catalog, reference and symbol data.
Users should verify for themselves that the data is accurate and suitable for their project work.
Intergraph Batch Services Quick Start Guide 2

Limitation of Damages
IN NO EVENT WILL INTERGRAPH CORPORATION BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL INCIDENTAL,
SPECIAL, OR PUNITIVE DAMAGES, INCLUDING BUT NOT LIMITED TO, LOSS OF USE OR PRODUCTION, LOSS OF
REVENUE OR PROFIT, LOSS OF DATA, OR CLAIMS OF THIRD PARTIES, EVEN IF INTERGRAPH CORPORATION HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
UNDER NO CIRCUMSTANCES SHALL INTERGRAPH CORPORATION’S LIABILITY EXCEED THE AMOUNT THAT
INTERGRAPH CORPORATION HAS BEEN PAID BY LICENSEE UNDER THIS AGREEMENT AT THE TIME THE CLAIM IS
MADE. EXCEPT WHERE PROHIBITED BY APPLICABLE LAW, NO CLAIM, REGARDLESS OF FORM, ARISING OUT OF OR IN
CONNECTION WITH THE SUBJECT MATTER OF THIS DOCUMENT MAY BE BROUGHT BY LICENSEE MORE THAN TWO (2)
YEARS AFTER THE EVENT GIVING RISE TO THE CAUSE OF ACTION HAS OCCURRED.
IF UNDER THE LAW RULED APPLICABLE ANY PART OF THIS SECTION IS INVALID, THEN INTERGRAPH LIMITS ITS
LIABILITY TO THE MAXIMUM EXTENT ALLOWED BY SAID LAW.
Export Controls
Intergraph Corporation’s software products and any third-party Software Products obtained from Intergraph Corporation, its
subsidiaries, or distributors (including any Documentation, Other Documentation or technical data related to these products) are
subject to the export control laws and regulations of the United States. Diversion contrary to U.S. law is prohibited. These Software
Products, and the direct product thereof, must not be exported or re-exported, directly or indirectly (including via remote access)
under the following circumstances:
a. To Cuba, Iran, North Korea, Sudan, or Syria, or any national of these countries.
b. To any person or entity listed on any U.S. government denial list, including but not limited to, the U.S. Department of Commerce
Denied Persons, Entities, and Unverified Lists, http://www.bis.doc.gov/complianceandenforcement/liststocheck.htm, the U.S.
Department of Treasury Specially Designated Nationals List, http://www.treas.gov/offices/enforcement/ofac/, and the U.S.
Department of State Debarred List, http://www.pmddtc.state.gov/compliance/debar.html.
c. To any entity when Licensee knows, or has reason to know, the end use of the Software Product is related to the design,
development, production, or use of missiles, chemical, biological, or nuclear weapons, or other un-safeguarded or sensitive
nuclear uses.
d. To any entity when Licensee knows, or has reason to know, that an illegal reshipment will take place.
Any questions regarding export or re-export of these Software Products should be addressed to Intergraph Corporation’s Export
Compliance Department, Huntsville, Alabama 35894, USA.
Trademarks
Intergraph, the Intergraph logo, PDS, SmartPlant, FrameWorks, I-Convert, I-Export, I-Sketch, SmartMarine, IntelliShip, INtools,
ISOGEN, MARIAN, SmartSketch, SPOOLGEN, SupportManager, and SupportModeler are trademarks or registered trademarks of
Intergraph Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are registered trademarks
of Microsoft Corporation. Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle Corporation and/or its
affiliates. MicroStation is a registered trademark of Bentley Systems Inc, all rights reserved. Other brands and product names are
trademarks of their respective owners.

Contents
Preface .......................................................................................................................................................... 6
Batch Services Overview ............................................................................................................................ 8

Batch Services Defined ........................................................................................................................... 9
Batch Services Features ......................................................................................................................... 9
Batch Services Components................................................................................................................. 10
Getting Started ...................................................................................................................................... 10
Installing and Configuring Batch Services ............................................................................................. 11

Batch Services Hardware/Software Recommendations ....................................................................... 11
Installing Intergraph Batch Services ..................................................................................................... 12
Command Line Installation (Silent Install) ............................................................................................ 14
Starting and Stopping Batch Services .................................................................................................. 16
Removing the Batch Service ................................................................................................................. 16
Configuring the Batch Services Server for Drawings Tasks ................................................................. 17
Batch Processing - Intergraph Smart Batch Services .................................................................... 17
Using Batch Manager ................................................................................................................................ 22

Understanding the Batch Manager Interface ........................................................................................ 22
Granting Batch Service Privileges ........................................................................................................ 23
Configure Account Mappings ................................................................................................................ 25
Creating and Managing Queues .............................................................................................................. 27

Creating and Deleting Queues .............................................................................................................. 27
Creating a Batch Queue ................................................................................................................. 27
Create Batch Services Queues ...................................................................................................... 28
Creating a Pipe Queue ................................................................................................................... 29
Deleting a Queue............................................................................................................................ 29
Changing Queue Properties ................................................................................................................. 30
Setting the Default Queue ..................................................................................................................... 31
Configure Queues for Jobs ............................................................................................................ 32
Adding Shells to a Batch Queue ........................................................................................................... 33
Adding Destinations to a Pipe Queue ................................................................................................... 34
Enabling and Disabling a Queue .......................................................................................................... 34
Starting and Stopping a Queue............................................................................................................. 35
Displaying Queue Status ...................................................................................................................... 36
Submitting a Batch Job ............................................................................................................................ 37

Creating a Script ................................................................................................................................... 37
Submitting a Job ................................................................................................................................... 38
Setting Basic Job Information ......................................................................................................... 38
Setting Job Scheduling Information ................................................................................................ 39
Creating Recurring Jobs ................................................................................................................. 40

Contents
Specifying Job Notification Preferences ......................................................................................... 41

Specifying How to Handle Job Output ............................................................................................ 41
Specifying Job Resource Requirements ........................................................................................ 42
Saving and Restoring Named Batch Jobs ............................................................................................ 43
Creating a Named Job.................................................................................................................... 43
Submitting a Named Job ................................................................................................................ 44
Glossary ..................................................................................................................................................... 45
Index ........................................................................................................................................................... 49

Preface
The Intergraph Batch Services Quick Start Guide describes how to install, configure, and use
Intergraph Batch Services on a computer running the Microsoft Windows operating system.
About This Document

This document is organized as follows:
 Section 1, “Batch Services Overview,” provides an introduction to the basic concepts and
features of Intergraph Batch Services (also known as Batch Services).
 Section 2, “Installing and Configuring Batch Services,” describes how to install, configure,
and run Batch Services on your system.
 Section 3, “Using Batch Manager,” describes the Batch Manager graphical interface, and
describes how to use it to grant batch service privileges for your system, and handle
account mapping.
 Section 4, “Creating and Managing Queues,” describes how to use the Batch Manager
graphical interface to create, manage, and monitor queues.
 Section 5, “Submitting a Batch Job,” describes how to use the Batch Manager graphical
interface to submit a batch job.
 The Glossary defines terms used in this document.
This document assumes that you understand basic networking concepts, and that you have a
working familiarity with the Transmission Control Protocol/Internet Protocol (TCP/IP), Internet
addressing, and Windows services.
Finding Additional Batch Services Information

Additional Batch Services documentation is available online through Batch Services Help, which
is delivered when you install the Batch Services software. Intergraph Batch Services Help
provides detailed information on the following subjects:
 Batch Services terminology.
 Accomplishing tasks with Batch Services.
 Using the graphical user and command-line interfaces to Batch Services.
 Using the Batch Services application programming interface (API).
Finding Operating System Information

If you need more detailed information on an aspect of the Windows operating system, you can
refer to the documentation delivered with the Windows operating system software.
Getting Documentation and Training

 In the United States, contact your sales account representative, or call the Intergraph at 1-
800-766-7701.
 At international locations, contact the Intergraph subsidiary or distributor from which you
purchased your Intergraph software to place an order.

Preface
To find information on training for Intergraph products, or to enroll for an available class, go to
http://www.intergraph.com.
Getting Telephone Support

If you experience problems with your Intergraph system or software, or have questions about
the information in this document, you can contact Intergraph for help.
 In the United States, call the Customer Response Center at 1-800-766-7701.
 At international locations, contact the Intergraph subsidiary or distributor from which you
purchased your Intergraph system or software.
Have the following information readily available when you call:
 Your name and telephone number.
 The product’s name.
 A brief description of the problem.
Finding Intergraph on the Internet

You can find Intergraph on the Internet at http://www.intergraph.com.

SECTION 1
Batch Services Overview

Intergraph Batch Services (Batch Services) is a system service that provides tools for the
management and execution of non-interactive tasks. The batch system is fully networked, and
provides connectivity to other batch servers.
The batch system is useful to both system administrators and users. Delayed execution of tasks
allows maintenance- and compute-intensive tasks, such as backups or compilation of large
programs, to be scheduled for times when the system is not in use. The batch system also
allows several client computers to use a multiprocessor server as a "compute engine" for CPU
intensive tasks. A large task can be spread out among several systems available on the
network.
The Batch Server service requires System Account privileges on the system. Use the
Services icon in the Control Panel to configure the Batch Server service.
The complete batch system consists of several pieces, including a batch Server, pipe and batch
queues, and an API set, as shown in the following diagram:
In This Section
Batch Services Defined ................................................................. 9
Batch Services Features ............................................................... 9
Batch Services Components ......................................................... 10
Getting Started............................................................................... 10

Batch Services Defined

Batch Services is a Windows system service that allows you (or an application) to manage and
perform non-interactive tasks on your computer system. Batch Services gives users and
applications a means of submitting compute-intensive tasks as processes that will run in the
background (non-interactively), and provides notification when the tasks complete.
To perform tasks using Batch Services, you submit a batch job to the system running Batch
Services (the batch server). The batch job provides information to the batch server about the
tasks you want to accomplish and how you want the batch job to run. When a job is successfully
submitted, it gets a unique job ID, enters a queue (a waiting list for processing), and then runs
on the batch server system as if you were logged in to the system and executing the task
yourself.
Batch Services is useful to both system administrators and users. Delayed execution of tasks
allows maintenance- and compute-intensive tasks, such as system data backups or compilation
of large programs, to be scheduled for times when the system is not in use. Batch Services also
allows several client computers to use a multiprocessor server as a “compute engine” for
compute-intensive tasks. A large task can be spread out among several batch server systems
available on the network.
Batch Services can be used with several Intergraph products, including Intergraph Smart™ 3D,
Plant Design System® (PDS), and SmartPlant Interop Publisher.
Batch Services Features

With Batch Services, time-consuming, resource-consuming, and repetitive tasks can be run
automatically. By making these tasks execute automatically, you can spend your time and
resources on other tasks. Benefits of automating tasks with Batch Services include the following:
 You can submit compute-intensive jobs into the background, and then go on to other tasks
or exit the application or session, while the batch job continues to process.
 You can set up jobs to repeatedly execute at any interval you choose.
 You can set up a list of jobs to run in a specific order.
 You can set the times you want your jobs to run.
 You can specify that certain jobs have priority over other jobs awaiting execution.
 You can submit jobs directly to a remote queue if Batch Services is present on that system.
Batch Services can continue processing tasks even after a system interruption. Batch Services
manages the tasks so that you do not have to restart them yourself, providing the following
features:
 Batch Services resubmits jobs when the network is down, or the remote host is unavailable.
 Batch Services automatically restarts jobs if the system crashes while a job is running, or if
the system is down when a job is scheduled to run.
With Batch Services, you control the processing of tasks submitted as batch jobs. The following
features allow you to manage task processing:
 You can use Batch Manager for managing batch jobs.

 You can manage batch and pipe queues on remote computers from one location.
 You can determine which jobs run at a given time, and in what order.
 You do not have to monitor jobs. Batch Services supports SMTP mail or event log
notification when a batch job completes successfully or encounters errors.
Batch Services provides the following additional features:
 An application programming interface (API).
 Support for multiprocessor systems.
 A command-line interface that can be used with scripts.
 Job submission to or from Windows systems.
Batch Services Components

Batch Services software consists of the following components:
 A batch server program (BATSERV.EXE).
 Windows Batch Provider, including an API library (BATCHAPI.DLL).
 The Batch Manager graphical interface (BATCHMGR.EXE).
 A command-line interface (QSUB.EXE, QSTAT.EXE, QMGR.EXE, QDEL.EXE).
Getting Started
Begin by following the instructions in the next section to install and configure the Batch Services
software on your system. Then refer to the rest of the document as follows:
 To remove Batch Services software from your system, see Removing the batch service (on
page 16).
 To learn about the Batch Manager interface, see Understanding the Batch Manager
Interface (on page 22).
 To grant batch services privileges on your system, see Granting Batch Service Privileges
(on page 23).
 To create queues on your system, see Creating and Deleting Queues (on page 27).
 To manage and monitor queues on your system, see Specifying Job Notification
Preferences (on page 41).
 To learn about scripts, see Creating a Script (on page 37).
 To submit a batch job, see Submitting a Job (on page 38).
 To manage batch jobs, see Creating and Managing Queues (on page 27).

SECTION 2
Installing and Configuring Batch

Services
This section describes how to install and configure Batch Services on a system running the
Windows operating system.
In This Section
Batch Services Hardware/Software Recommendations ................ 11
Installing Intergraph Batch Services .............................................. 12
Command Line Installation (Silent Install) ..................................... 14
Starting and Stopping Batch Services ........................................... 16
Removing the Batch Service ......................................................... 16
Configuring the Batch Services Server for Drawings Tasks ......... 17
Batch Services Hardware/Software

Recommendations
Before installing Batch Services software, verify that the computer on which you want to use the
software has the following:
 Intel-compatible processor
 At least 4 GB of RAM
 At least 6 MB of free space on the system’s hard disk.
 A Windows-compatible network adapter.
Server Operating Systems

 Windows 2003 32-bit - Only as DB and file server SP2
 Windows 2003 64 bit - 64-bit Windows 2003 Server (Enterprise Edition) SP1 certified as a
data / file server and also certified with MSQL2005 and Oracle 11GR2 as the database
server.
 Windows 2008 R2 64-bit - 64-bit Windows 2008 Server R2 certified as a data / file server
and also certified with MSQL2008 and Oracle 11GR2 as the database server. (See Note 1)
 Windows Server 2012 R2 - Windows 2012 Server R2 certified as a data / file server and
also certified with MSQL2012 and Oracle 11.2.0.4.0 as the database server. (See Note 1)
Client Operating Systems

 Windows 7 32-bit
 Windows 7 64-bit

Installing and Configuring Batch Services
 Windows 8.1 64-bit
 If you want Batch Services to run batch jobs as 64-bit processes, the batch server computer
must run the 64-bit version of the operating system. It must also have the 64-bit version of
the designated Intergraph software installed.
 Batch Services software can work with any network adapter supported by Windows. The
network adapter you use must be properly installed and configured for your computer before
you install Batch Services software. Refer to your Windows documentation for a list of
compatible network adapters, and to the documentation for your network adapter for
installation and configuration instructions.
 Running batch jobs on the Citrix server is not supported. However, you can pipe queue the
batch processes from the Citrix server to a batch queue on another computer.
Installing Intergraph Batch Services

1. Open Control Panel > Administrative Tools > Services, and determine the current status
of the TCP/IP NetBIOS Helper service on your computer. Start that service if it is not already
running.
2. Insert the Intergraph Batch Services DVD into your computer.
3. To start setup, do one of the following:
 Press the Windows key + R to display the Run dialog box. Type drive:\setup, where
drive is the DVD drive letter.
 In Windows Explorer, select the DVD drive, and then double-click setup.exe.
4. Select Batch Services Installation.
5. Click Next on the Welcome page.

6. Type your name and organization name, and then click Next.
7. On the License Agreement page, select your country.
8. Click Display. Read the license agreement, and then click Yes.
9. Review the default installation folder ($WindowsDrive:\Win32App\Ingr\Batch\).
If you plan to use this installation of Intergraph Batch Services with Plant
Design System® (PDS), do not install Intergraph Batch Services to a folder path that
contains spaces, such as c:\Program Files (x86)\Batch. Although Intergraph Batch Services
supports spaces in folder paths, PDS does not.
10. Click Next.

11. Specify whether to run all jobs as the same user or use account mapping.
If you select Set up account mapping per user through Smart Batch Services, you must
configure account mapping before you can submit jobs. Use Batch Manager to configure
account mapping after setup is complete. For more information, see Configure Account
Mappings (on page 25).
If you select Run all jobs as same user to configure account mapping, define the user
name and user name password under which jobs should run.
12. Click Next.

13. Click Install.
Intergraph Batch Services is installed on your computer.
14. Click Finish.
15. Restart your computer.
You can find the batch job log files in the %temp%\SP3DBatchSvcTemp file on the
batch server computer.
Command Line Installation (Silent Install)

To install Batch Services from the command line, run Setup.exe in the BatchServices folder.
Setup.exe automatically runs the Windows Installer setup, Intergraph Batch Services.msi.
The following command-line arguments are available:
Required Arguments
SLAACCEPT=yes - Accepts the Software License Agreement.
/v"<arguments>" - Passes options to the Windows Installer setup, Intergraph Batch
Services.msi. There are no spaces after the v.
Optional Arguments
/s - Runs Setup.exe in silent mode.

/qn - Runs the Windows Installer setup, Intergraph Batch Services.msi, in silent mode.
INSTALLDIR=<path> - By default, the product is installed to
the<WindowsVolume>\Win32App\INGR\BATCH folder. To change the location, enter a different
path. For example, enter INSTALLDIR=D:\Intergraph\BatchServices. If spaces exist in the
path, you must add \" before and after the path. For example, enter
INSTALLDIR=\"D:\Intergraph\Batch Services\".
INTERACTIVE_DESKTOP=0 - By default, on Windows XP, the Batch Server service is setup
to interact with the desktop. To disable this behavior, include INTERACTIVE_DESKTOP=0. This
setting is not valid with Vista, Windows 7, or later operating systems, and is ignored.
ACCTMAP_USERNAME=domain\username - To run all jobs as the same user, enter an
existing domain\username.
ACCTMAP_PWD - Password for the username. Used in conjunction with
ACCTMAP_USERNAME.
/Lv*x <path>\Logfilename - Creates a Windows Installer installation log file. If the path or file
name contains spaces, you must put \" in front of the path and after the file name, for example:
/Lv*x \"C:\Installer Log Files\InstallLog.log\". The path must already exist.
Example Command-lines
C:\>"…\BatchServices\Setup.exe" /s /v"SLAACCEPT=yes /qn"
Installs the setup to the default location without account mapping. By default, on Windows XP,
the Batch Server service is set up to interact with the desktop.
C:\>"…\BatchServices\Setup.exe" /s /v"INSTALLDIR=\"C:\Batch Services\"
SLAACCEPT=yes INTERACTIVE_DESKTOP=0 /qn"
Installs the setup to C:\Batch Services without account mapping. On Windows XP, the Batch
Server service is not set up to interact with the desktop.
C:\>"…\BatchServices\Setup.exe" /s /v"INSTALLDIR=\"C:\Batch Services\"
SLAACCEPT=yes INTERACTIVE_DESKTOP=0 ACCTMAP_USERNAME=domain\username
ACCTMAP_PWD=password /qn"
Installs the setup to C:\Batch Services with account mapping. On Windows XP, the Batch Server
service is not set up to interact with the desktop.
C:\>"…\BatchServices\Setup.exe" /s /v"SLAACCEPT=yes INTERACTIVE_DESKTOP=0
ACCTMAP_USERNAME=domain\username ACCTMAP_PWD=password /Lv*x \"C:\Install
Log Files\install.log\" /qn"
Installs the setup to the default location with account mapping, and creates a Windows Installer
installation log file. On Windows XP, the Batch Server service is not set up to interact with the
desktop.
C:\>"…\BatchServices\Setup.exe" /s /x /v"/qn"
Uninstalls Batch Services in silent mode.

Starting and Stopping Batch Services

When you install Batch Services software, the batch server service is configured to start
automatically each time you restart your computer. No further configuration is required.
Intergraph recommends leaving the batch server service as configured. However, if you want to
configure Batch Services to start manually, do the following:
1. Open Control Panel > Administrative Tools > Services.
2. In Services, right-click Intergraph Batch Server, and select Properties.
3. Set Startup type to Manual, and then click OK.
4. Close the Services window.
Batch Services also delivers an Intergraph NQS Listener service that is
configured to start automatically. If your site is not using Intergraph NQS, you can configure
the NQS Listener service to start manually. Repeat steps 1-3, selecting Intergraph NQS
Listener from the Services list.
If you configure Batch Services to start manually, you must start the batch server each time you
restart your system, or each time you want to run Batch Services.
To start Batch Services manually:
2. In Services, select Intergraph Batch Server, and then click Start.
To stop Batch Services:
2. In Services, select Intergraph Batch Server, and then click Stop.
Removing the Batch Service

To remove the batch services:
1. As an administrator, go to the Control Panel and then Programs and Features.
2. Select Intergraph Batch Services.
3. Click Change/Remove or Uninstall depending on your version of Windows.
4. Click Yes.

Configuring the Batch Services Server for Drawings

Tasks
1. In the folder [Intergraph Batch Services Installation
folder]\Core\Container\Bin\Assemblies\Release, run ConfigureDrawingsBatch.exe.
2. Click Yes, and then click OK.
 The printer name on the client computer must match the printer name on the batch server.
 Every mapped account must open Microsoft Excel once on every batch server.
 Microsoft Excel must have the same security settings that are necessary for interactive
updates. Excel must be configured correctly for every IBS-mapped account on the batch
server.
 You must add the following entries to the system path for 3D model data documents to
update:
 [Product Folder]\Core\Runtime
 [Product Folder]\GeometryTopology\Runtime
 You must run the ConfigureDrawingsBatch utility each time you change mapped account
settings.
 If you are running 64-bit drawings batch services and Oracle, you must install the 64-bit
Oracle client on the computer running the batch services.
Batch Processing - Intergraph Smart Batch Services

With batch processing, you can update, print, or refresh your documents without dedicating your
computer to the operation.
Drawings Batch Dialog Box (on page 18)
What do you want to do?

 Add Actions to Queue (on page 19)
 Create a Template (on page 20)

Drawings Batch Dialog Box

Updates, prints, and refreshes document batch jobs without requiring a dedicated computer for
the operation.
Available Actions
Lists the actions that you can perform within a batch job. The actions available are based on
permissions and document type.
 Refresh - Refreshes documents on a batch queue.
 Full Update - Updates all drawings by rule documents, regardless of the current status
of the documents. This action is only available in the Marine mode.
 Update - Updates documents on a batch queue.
 Save As - Specifies the file format to which to save Intergraph Batch Services drawings.
 Print - Schedules a document to be printed from a batch queue.
Actions to Queue
Lists the actions that are performed in the batch job.
 Remove - Removes an action from the queue.

 Clear - Removes all actions from the queue.
Action Options
Defines the parameters of an action. The displayed options depend on the selected action.
Template Name
Saves print settings as a template. Type a name in the box, and click Save Settings as
Template. While optional, creating a new template is a quick method to submit a batch
job with the specified options.
Save Settings as Template
Creates a user-parameterized action.
Delete
Removes a template from Available Actions. This option is available only on user-
created templates.
Save As
For more information on the Save As action options, see Save As Dialog Box.
In the Output Folder field, select a shared folder through its UNC path. A
UNC path has the general form of \\server\share.
Print
 Printer – Displays all printers configured on the client computer. The name of the printer
on the batch queue must match for the print to be successful.
 Copies – Specifies the number of copies to print.
 Black and White – Prints a black and white drawing, if checked.
 Orientation – Indicates the orientation of the printed output. Select Portrait or
Landscape.

 Paper Size – Displays the paper sizes supported by the selected printer.
Use 64-bit if available
Updates drawings with 64-bit processes. This option is only available for Update actions
performed on composed drawings.
If you select Use 64-bit if available and run Update on a folder component
containing composed drawings and other drawing types, the composed drawings are
updated with 64-bit processes. All other drawings are updated with 32-bit processes.
Schedule
Creates the job and opens the Schedule Batch dialog box.
If you click Schedule with no actions in Actions to Queue, you receive a
message, and the dialog box remains open.
Add Actions to Queue

You can set up batch jobs for a single document or for multiple documents.
Single document:
1. Right-click on a single drawing either in the Detail View or in the Drawings Console, and
select Batch.
2. Select the action, and click Add to move it into Actions to Queue.
 You can add actions to the queue in any order, but the software processes the actions
in the following order: Refresh, Update, and then all other actions. If you add Update,
but you do not add Refresh, Update is the first action processed.
 You can only add one Save As action to the queue.
3. Define any action options. For more information, see Batch Processing - Intergraph Smart
Batch Services (on page 17).
4. Click Schedule to create the job and open the Schedule Batch dialog box.
Multiple documents:
1. Do one of the following:
a. Right-click a set of multi-selected documents or components in the Detail View, and
select Batch.
b. Right-click a component in the Management Console, Detail View, or Drawings
Console, and select Batch.
2. Select the action, and click Add to move it into Actions to Queue.
 You can add actions to the queue in any order, but the software processes the actions
in the following order: Refresh, Update, and then all other actions. If you add Update,
but you do not add Refresh, Update is the first action processed.
 You can only add one Save As action to the queue.

3. Define any action options. For more information, see Batch Processing - Intergraph Smart
Batch Services (on page 17).
4. Click Schedule to create the job and open the Schedule Batch dialog box.
Create a Template
Templates are user-parameterized actions that are saved in the session file and available for
future batch jobs. You can only create templates based on the Print action.
Create a new template:
1. Select the Print action, and click Add to move it to Actions to Queue.
2. In Action Options, make the necessary changes to the action.
3. Type a new Template Name for the action.
4. Click Save Settings As Template.
Delete a template:
1. Select the template to delete.
2. In Action Options, click Delete.
Schedule [Task] Dialog Box

Queue
Displays the name of the queues configured by an administrator for the job. For more
information on configuring the queues, see Configure Queues for Jobs in the Project
Management User's Guide.
Run job
Sets the frequency with which the job runs. Jobs can be scheduled to run once or on a
regular interval (daily, weekly, or monthly). Depending on the job frequency selected,
additional controls display. These controls allow you to define more specific scheduling
information. The scheduling controls can be changed only at job submission.
Run on
Sets the time to start running the job.
Options
Opens the Optional Schedule Properties Dialog Box (on page 21) that you can use to define
a start and end date.
Run on box
Contains a calendar from which you can select the run date. This option is available when
you select Once from Run job.
Every X days
Specifies how many days pass between job runs. This option is available when you select
Daily from Run job.
Every X weeks

Specifies how many weeks pass between job runs. In addition, you can select on which
days the job runs. This option is available when you select Weekly from Run job.
Day X of the month
Specifies on which day of the month the job runs. This option is available when you select
Monthly from Run job.
The X Y of the month
Specifies on which day of the month the job runs. For example, you can select the last
Monday of the month. This option is available when you select Monthly from Run job.
Job Start
Notifies you when the job starts, if Outlook is set up.
Job Completion
Notifies when the job completes, if Outlook is set up.
Job Abort
Notifies you if the job aborts, if Outlook is set up.
Address Book
Selects the name of the person to be notified by e-mail of the job status, if Outlook is set up.
If Outlook is not available, this option does not work. You can also type the address
manually. The person you define here receives an email with the job log files after the job
finishes.
 The Batch Services SMTP option must be configured on the batch server for this to work.
For more information, see the Intergraph Smart Batch Services documentation.
 The WinZip application is no longer required on the batch server to compress any emailed
attachments. Compression is now done with functionality included in Intergraph Batch
Services.
Optional Schedule Properties Dialog Box

Provides more options on the Schedule Backup dialog box. This dialog box opens when you
click Options.
Start date
Sets an optional start date.
End date
Sets an optional end date, if checked.

SECTION 3
Using Batch Manager

This section briefly describes the Intergraph Batch Manager and how to use it to grant batch
service privileges on your computer. This section also briefly describes how Batch Services
handles account mapping. For more detailed information on the Batch Manager interface, or for
information on using the command-line interface, refer to Batch Services Help or the Batch
Services User's Guide.
In This Section
Understanding the Batch Manager Interface ................................. 22
Granting Batch Service Privileges ................................................. 23
Configure Account Mappings ........................................................ 25
Understanding the Batch Manager Interface

Intergraph Batch Manager provides a graphical interface for viewing and managing batch
services. Batch Manager allows you to create queues and connect to remote queues, and to
submit and manipulate jobs within queues. Connection to remote servers allows you to manage
other Windows batch servers on the network.
Click Start > All Programs > Intergraph Batch Services > Intergraph Batch Manager.
Figure 1: Batch Manager
The Batch Manager toolbar, located below the Batch Manager menus, provides shortcuts to the
following tasks. Position the cursor over a toolbar button to display a tip describing the command
associated with that button. Buttons are provided for the following tasks:
 Submitting and deleting jobs
 Holding and releasing jobs
 Creating and deleting queues

Using Batch Manager
 Enabling and disabling queues

 Starting and stopping queues
Batch Manager provides two types of views in the main window:
 The server view displays information about the server and its queues. Information on each
queue in the server view includes its name and type, its priority, its inflow and outflow state,
and the number of jobs currently in the queue. When the server view is active, you can
create, delete, and manage queues. Double-clicking on a queue listed in a server view
displays the queue view of that queue.
 The queue view displays information about the jobs contained in a specific queue.
Information on each job in a queue includes its ID and status, its priority, its name, and the
username of the job’s submitter. When the queue view is active, you can manipulate specific
jobs in that queue. Double-clicking on a job listed in a queue view displays the properties
of that job.
The status bar, at the bottom of the main window, displays information about the active view.
For an active server view, the status bar displays the server name. For an active queue view,
the status bar displays the queue’s name and type, its description, and its inflow and outflow
states.
Granting Batch Service Privileges

Before you begin using Batch Services, you should use Intergraph Batch Manager to ensure
that users on your system (and users on other systems, if appropriate) are granted the proper
privileges for access to Batch Services.
A user with manager privileges can use all the commands that affect batch server configuration
and operation, including granting and removing privileges, and creating and deleting queues. A
user with operator privileges can manage jobs, including those belonging to other users, and
can start and stop batch server queues. Users or groups without privileges can only submit
requests to queues to which they have been granted access. Most users or user groups are
non-privileged users.
Using User Account Control turned on to level 3, the Administrators group on your system has
manager privileges. From an account belonging to the Administrators group, you can add users
and groups of users, on your system or other systems, to the manager and operator privilege
lists.
1. Open Start > All Programs > Intergraph Smart Batch Services > Intergraph Batch
Manager.
2. Select your computer name in the tree view on the left.
3. Click Server > Properties.
4. Select the Security tab.
Users and groups, and their Batch Service privileges, display in the Managers and

Using Batch Manager
Operators list.
5. Click Add, and then type the username of a user into the Add Names box, or the group
name of a group, to which you want to grant privileges.
6. Specify local users and groups (on your computer) by username or group name only. Use
one of the following formats when keying in a username or group name:
domain_name\username or system_name\username
domain_name\group_name or system_name\group_name
Separate multiple users or groups with a semicolon (;).
7. Select the type of privilege you want to grant the user or group (Manager or Operator).
8. Click OK.
9. Repeat steps 5 through 8 for each user or group to which you want to grant privileges.
10. When you have finished assigning privileges to users or groups, click OK on the Server
Properties dialog box.
To remove privileges from a user or group:

1. Open Start > All Programs > Intergraph Smart Batch Services > Intergraph Batch
Manager.
2. Select your computer name in the tree view on the left.
3. Click Server > Properties.
4. Select the Security tab.
The current users and groups with Batch Service privileges are displayed in the Managers
and Operators list.

Using Batch Manager
5. In the Managers and Operators list, select the user or group for which you want to remove
privileges.
6. Click Remove.
7. Repeat steps 5 and 6 for each user or group from which you want to remove privileges.
8. When you have finished removing privileges from users and groups, click OK.
To change a user’s or group’s privileges, first remove the current privileges from the
user or group; then re-add the user or group to the privilege list with the new privilege.
Configure Account Mappings

Batch Services requires an account name and password to use when running jobs. The process
of determining the account name to use is called account mapping. You can use Batch Manager
to enter and modify account-mapping information for your system. An account mapping entry
comprises two parts: the user information to match (the “from” user), and whom that user maps
to (the “to” user). Account mapping entries allow users submitting a job to assume the
environment and permissions of the user to whom they are mapped.
To perform account mapping, the batch server tries to match the job owner with an account
mapping entry, using the following order (items are listed on the account mapping dialog box in
the order in which they are applied):
1. The batch server first tries to find an exact match, matching the job owner’s domain or
computer name and username with the “from” user in the account mapping entries.
2. If the batch server cannot find an exact match, the batch server then searches the account
mapping entries using the job owner’s domain or computer name, with “*” (meaning any
user) as the username.
3. If no match is found, the batch server then searches the account mapping entries using “*”
(meaning any computer or domain) as the domain name, with the job owner’s username.
4. Finally, if a match still has not been found, the batch server searches with “*” as the domain
name and “*” as the username.
How you configure account mapping depends on the security needs and configuration of your
site. For more information on configuring account mapping, see Configure Account Mappings in
the Installation Guide.
Configure Default Account Mappings

The map-to-account user must have access to the Intergraph Smart 3D site,
catalog, and model databases because it is under this user name that the batch jobs will run.
Give this user those access rights using Intergraph Smart 3D Project Management.
1. Click Start > All Programs > Intergraph Smart Batch Services > Intergraph Batch
Manager.
2. Select the computer name in the tree view.
3. Select Server > Account Mapping.
4. Type * for the Map From Account Domain/Host and the User.
5. In the Map To Account Domain Controller box, type the name of the domain controller.
The primary domain controller name displays as the default.

Using Batch Manager
6. In the Map To Account Domain/Host box, select the domain of the Windows user account
you want to run jobs as.
7. In the Map To Account User box, type the user name to use.
8. Click Add.
9. Type and confirm the password for the "to account" user name.
10. Click OK.
The ConfigureDrawingsBatch utility must be run each time mapped account
settings are changed. For more information, see Configuring the Batch Services Server for
Drawings Tasks (on page 17).

SECTION 4
Creating and Managing Queues

This section describes how to use the Intergraph Batch Manager graphical interface to create
and manage queues on a system running Batch Services. For more information on the Batch
Manager interface, or for information on using the command-line interface, refer to Batch
Services Help.
In This Section
Creating and Deleting Queues ...................................................... 27
Changing Queue Properties .......................................................... 30
Setting the Default Queue ............................................................. 31
Adding Shells to a Batch Queue .................................................... 33
Adding Destinations to a Pipe Queue............................................ 34
Enabling and Disabling a Queue ................................................... 34
Starting and Stopping a Queue ..................................................... 35
Displaying Queue Status ............................................................... 36
Creating and Deleting Queues

Before you can submit a batch job, you must create and enable a batch queue. The batch
queue accepts requests to execute shell scripts, commands, or executables non-interactively.
You might also want to create one or more pipe queues on your system. A pipe queue accepts
requests to send batch jobs to another queue. Typically, you create a pipe queue when you
need access to a batch queue on another system.
Note the following limitations on creating queues:
 You must have manager privileges to create a queue.
 When naming a queue, you can use any alphanumeric and punctuation characters, except
for the punctuation characters [@ \ ( ) = ,]. The first character cannot be - or /.
Creating a Batch Queue

To create a batch queue on your system, take the following steps:
1. Open Intergraph Batch Manager.
2. Select the server on which you want to create the queue.
3. Select Queue > Create, or click Create Queue on the toolbar.

4. Type the queue name into the Queue Name box.
5. Optionally, type a description of the batch queue into the Description box.
6. Under Queue Type, select Batch.
7. Click OK.

Refer to Adding Shells to a Batch Queue (on page 33) for more information on batch queues.
Create Batch Services Queues

You must create the Intergraph Batch Services queues that Intergraph Smart 3D will use.
1. Open Windows Explorer on the computer on which Intergraph Batch Services is installed.
2. Navigate to and double-click C:\Program Files
(x86)\Smart3D\ProjectMgmt\Tools\bin\ConfigureSP3DBatchQueue.exe.
The Custom Configuration of NT batch for Smart Plant 3D dialog box displays.
3. Click OK in the confirmation box to stop and restart the Intergraph Batch Services.
Run this tool at least once on the computer on which the job needs to be submitted,
or on the computer where the job needs to be run. This tool sets some environment
variables as well as creating the batch queues.
5. In Services, select Intergraph Batch Server from the list, and then click Stop.
6. With Intergraph Batch Server service still selected, click Start.
7. To verify that the batch queues were created, open Intergraph Batch Manager and then
select your server in the tree view.
 The WinZip application is no longer required on the batch server to compress any emailed
attachments. Compression is now done with functionality included in the Intergraph Smart
3D delivery.
 This tool cannot create pipe queues. Use Intergraph Batch Services to create pipe queues.
 Verify that the C:\Windows\SysWOW64\config\systemprofile\Desktop folder exists if you are
using a 64-bit or Windows Server operating system. Ask your system administrator create
the Desktop folder with full permissions if it does not exist.

Creating a Pipe Queue

To create a pipe queue on your system, take the following steps:
2. Select the server on which you want to create the queue.
3. Select Queue > Create, or click Create Queue from the toolbar.
4. Key the queue name into the Queue Name box.
5. Optionally, key a description of the batch queue into the Description box.
6. Under Queue Type, select Pipe.
7. Click OK.
Refer to Adding Destinations to a Pipe Queue (on page 34) for more information about pipe
queues.
Making Other Batch Servers Available

You can run batch jobs on other computers that are running Intergraph Smart Batch Services by
using pipe queues:
1. Create Pipe Queues in Intergraph Batch Manager. For details, see Batch Manager help.
2. Define different server destinations in piped queue destination tab. The format for giving
destinations is “\\ServerName\BatchQueueName”.
3. In Project Management, configure queues for jobs with pipe queues. For more information,
see Configure Queues for Jobs in the Intergraph Smart 3D Installation Guide.
4. When a user submits a job to a pipe queue, the job is automatically routed to and run on the
destination batch server.
Make sure you install Smart 3D on the computer with Batch Services, and that
destination batch queues are available on batch server.
Deleting a Queue
Before you can delete a queue, the queue cannot contain any jobs and must be disabled and
stopped. You must have manager privileges to delete a queue. You can delete queues on
remote Windows computers. To delete a queue from your system:
2. Click on the queue listed in the server view, or select the queue view for that queue.
3. Select Queue > Delete, or click Delete Queue from the toolbar.
4. When prompted, click Yes to confirm that you want to delete the queue.

Changing Queue Properties

A queue is created with its operational parameters set at default values. You can change these
default values by selecting a queue listed in the server view and pressing ALT+ENTER, or by
selecting the queue view for that queue, and then selecting Properties from the Queue menu.
Select the tabs in the Queue Properties dialog to display the current values for a queue’s
parameters. The following are basic operational parameters found in the Queue Properties
dialog, along with their default values and brief descriptions of changes you can make.
Tab Parameter Default Comments
General Description None Optional.
Scheduling Run Limit 1 Determines the maximum number of jobs

that can run in the queue at the same time.
Specify a number of jobs from 1 to 60.
Job Defaults Scheduling Priority 31 Determines the default priority of execution

of a job relative to other jobs in the queue.
Raise (as high as 1023) to increase the
priority; lower (as low as -1024) to lower the
priority.
Security Queue Access Unrestricted Determines who can gain access to the
queue. To restrict access to specific users or
groups of users, select Restricted. To open
access to the queue to all users, select
Unrestricted.
Authorized Groups None Lists users or groups of users that can gain
and Users access to the queue if it is restricted. Select
Add to add users or groups to the access
list. Select a user or group, and then select
Remove, to remove that user or group from
the access list.
When keying in a username or group name,
use the format for usernames and group
names described in Granting Batch Service
Privileges (on page 23).
Shells For a complete description, see Adding

Shells to a Batch Queue (on page 33).
Destinations Order dependent. For a complete

description, see Adding Destinations to a
Pipe Queue (on page 34).

Setting the Default Queue

The default queue on a server is the queue to which batch jobs are submitted when the user
does not explicitly request a queue. The default queue cannot be a remote queue; it must exist
on the server.
Manager privileges are required to set a default queue.
Using Project Management:

1. In Project Management, right-click the model and select Configure Queues for Jobs.
The Configure Queues for Jobs (on page 32) dialog box displays.
2. Type a queue name into the Default Queue box, or select a queue from the dropdown list.
3. Click OK.
Using Batch Manager:

1. Select the server.
2. Select Server > Properties.
The Server Properties Dialog Box displays.
3. Type a queue name into the Default Queue box, or select a queue from the dropdown list.
4. Click OK.
Using the command line:

1. Start qmgr.
2. Use the set default batch_request queue command to set the default queue for the server.
You can use the qmgr utility to create a batch file with a series of commands to
manage the queues. This reduces the administrative workload across all client machines. For
example, when you run the below command lines on a batch file that exists on all client
machines, you create the same piped queues on each client:
create pipe_queue <Pipe queue Name> priority = queue-priority [
destination =dest-name ] [ run_limit = run-limit ]
enable queue <Pipe queue Name>
start queue <Pipe queue Name>
Using the Batch API:

1. Use the BatchGetServerInfo function to obtain the current BATCH_SERVER_INFO
structure.
2. Modify the BATCH_SERVER_INFO defaultqueue field.
3. Use the BatchSetServerInfo function with the modified BATCH_SERVER_INFO structure to
set the default queue.

Configure Queues for Jobs

Tools > Configure Queues for Jobs displays the Configure Queue For Jobs dialog box
where you can configure batch queues for Intergraph Batch Services jobs. You must have
administrator privileges to access this tool.
For the site, you must have the following privileges:
 In Oracle, you must have the SP3DProjectAdministrator role.
 In SQL Server, you must be a system administrator on the server. If you are working in a
multiple domain environment, you must run SQL Server with a network service account, and
not with a domain account.
For a model, you must have full access or write permissions on the selected model database.
Time displayed in
Specifies the unit of measurement for Maximum Allowed Time. The available units of
measurement are sec (seconds), min (minutes), hr (hours), and day. The default unit is hr.
Job Type
Displays the name of the job. The jobs listed are specific to the site or model.
Job Description
Displays a brief description of the job.
Default Queue
Displays the default queue for a specific job, which can be a batch queue or a pipe queue.
When this dialog box displays for the first time, it shows the first queue in the list of available
queues on the local server. You can type a new default queue into this box, or you can
select any queue from the list of available queues on the local server.
 Ensure that the default queue is configured for a job in Project Management, and that
the configured queue exists on all client computers.
 For pipe queues, you need to add the required destinations to the queue. For more
information, see Creating and Configuring Pipe Queues in the Smart 3D Intergraph
Batch Services User’s Guide.
Optional Queues
Displays the Configure Optional Queues dialog box.
Configure Optional Queues Dialog Box
Maximum Allowed Time
Specifies the maximum allowed time to process a job type in the queue. If the job is not
completed in the allowed time, it terminates and the software sends a time-out notification to
the mailing list specified at the time that you submitted the job. By default, the Maximum
Allowed Time is not specified, and the job runs without any time limit. To specify a
Maximum Allowed Time, you must first select Is TimeOut Supported.
When queue times are defined on the Configure Optional Queues dialog box, Maximum
Allowed Time displays the total of those times.

 Set a value for Maximum Allowed Time that allows enough time for each job to
execute.
 If a job is submitted on a pipe queue but is executed on a different queue, the
Maximum Allowed Time for the job is read from the submitted pipe queue.
Is TimeOut Supported
Enables Maximum Allowed Time functionality. This option is not selected by default.
You can create custom batch jobs. For more information, see Creating and
Scheduling Custom Batch Jobs in the Smart 3D Reference Data Guide.
Adding Shells to a Batch Queue

A shell is a program that can run a specific type of script; for example, cmd.exe is a shell that
can run .bat scripts. You can associate a list of shells with each batch queue. The shell list
allows you to specify a shell from the list without knowing where the actual shell resides on the
computer.
When you associate a list of shells with a batch queue, users can choose one of
these shells from the list, specify a full path to another shell, or use a shell in the PATH
environment variable for the user to whom the job is mapped.
To add a shell to a batch queue:
2. Click on the batch queue listed in the server view, or select the queue view for that queue.
3. Select Queue > Properties.
The Queue Properties dialog box displays.
4. Select the Shells tab.
5. Under Shell Configuration, type the name of the shell into the Name box, then type the
path to the shell into the Location box.
6. Click Add.
The name and location of the shell display in the Shell dialog box. If you want to set a
default shell for the queue, proceed to the next step. Otherwise, skip to step 8.
You may want to specify the default shell for a batch queue on your system. The
default shell is the one run when a user submits a job, but does not explicitly request a shell.
When you set a default shell for a batch queue, you must explicitly select another shell if you
want to submit a job to run a script that uses another shell. If you want to submit
executable programs (.EXE files) to a batch queue, do not set a default shell for that queue,
or set the default shell to be CMD.EXE.
7. Select the shell in the Shell List box; then select Default.
The name of the shell displays in the Default Shell box.
8. Click OK.
You must have manager privileges on the batch server to set the default shell for a
batch queue.

Adding Destinations to a Pipe Queue

Destinations are used with pipe queues. Pipe queues are normally used to create a connection
to a remote batch queue. A pipe queue interprets a batch job request, and pipes it to the first
available queue in its destination list that will accept the request. The destination list may contain
any queue type.
To add a destination to a pipe queue:
2. Click on the pipe queue listed in the server view, or select the queue view for that queue.
3. Select Queue > Properties.
The Queue Properties dialog displays.
4. Select the Destinations tab.
5. Key the new destination queue into the Destination edit box; then click Add.
The destination displays in the List box.
6. A destination can be a local queue (on your system) or a remote queue (on other systems).
Specify a local queue by its queue name. To specify a remote queue, use one of the
following format: \\system_name\queue_name
If you list more than one destination for a pipe queue, the pipe queue will send a
job to the first available queue in its destination list that will accept the job.
7. Repeat step 5 for each destination you want to add to the pipe queue.
8. When you have finished adding destinations to the pipe queue, click OK.
You must have manager privileges on the batch server to add a destination to a pipe
queue.
Enabling and Disabling a Queue

A newly created queue has a disabled inflow state; it will not accept new jobs that are submitted
or transferred to it. A queue must be enabled to accept new jobs.
You must have at least operator privileges on the batch server to enable or disable a queue.
To enable a queue:
3. Select Queue > Enable, or click Enable Queue from the toolbar.
The queue should now show as ENABLED in its listing in the server view.
The availability of the Enable and Disable menu and toolbar commands toggles,
depending on the current inflow state of the queue.

To disable a queue:
3. Select Queue > Disable, or click Disable Queue from the toolbar.
The queue should now show as DISABLED in its listing in the server view.
Starting and Stopping a Queue

A newly created queue has a stopped outflow state; it will not run any jobs it contains. A queue
must be started to run jobs.
You must have at least operator privileges on the batch server to start or stop a queue.
To start a queue:
3. Select Queue > Start, or click Start Queue from the toolbar.
The queue should now show as STARTED in its listing in the server view.
The availability of the Start and Stop menu and toolbar commands toggles, depending on the
current outflow state of the queue.
To stop a queue:
3. Select Queue > Stop, or click Stop Queue from the toolbar.
The queue should now show as STOPPED in its listing in the server view.
The availability of the Start and Stop menu and toolbar commands toggles, depending on the
current outflow state of the queue.

Displaying Queue Status

You can display the status of any queue on the batch server on your computer, and of any
queues on any batch servers on remote computers. Queue status information includes queue
type, queue priority, inflow state, outflow state, and a count of the jobs currently in the queue.
To display the status of a queue on your computer, double-click on the queue listed in the server
view, or select the queue view for that queue in the Intergraph Batch Manager window.
To display the status of a queue on another system:
2. Select Server > Connect.
3. Key in the name of the server (\\system_name) on which the queue resides; then click OK.
Batch Manager displays a server view for the selected server, listing the queues currently
available on that server.
You can also use Queue > Connect To to display a queue view for a particular
queue on a remote computer.

SECTION 5
Submitting a Batch Job

This section describes how to submit a batch job, and monitor the status of submitted jobs, on a
system running Batch Services. For more information on the Batch Manager interface, or for
information on using the command-line interface, refer to Batch Services Help.
You can use Batch Services to run an executable program on your system, or to perform a set
of tasks on your system. To perform a set of tasks, you can create a script, a file containing
instructions that can be interpreted by a shell. The following section describes scripts; the rest of
the chapter describes how to submit and monitor batch jobs.
In This Section
Creating a Script ............................................................................ 37
Submitting a Job ............................................................................ 38
Saving and Restoring Named Batch Jobs ..................................... 43
Creating a Script
A batch job reads a script and performs the instructions in it, using the appropriate shell (the
program that runs the instructions in the script). Scripts can take many forms, including .bat files
and Perl scripts. A script can also be an executable program (.EXE file) if the queue has no
default shell, or if the shell is set to CMD.EXE.
The following example is a .bat script that backs up a directory on the batch server to a shared
drive that has been locally mounted from a remote system. To use the script, ensure that a local
batch queue has been created, enabled, and started, and that the queue’s default shell is the
cmd.exe program.
REM This script will do the following:
REM
REM 1. Mount the shared drive \\machine\share
REM 2. Copy everything in c:\users\default to the shared drive.
REM 3. Unmount the shared drive.
REM
net use p: \\machine\share
xcopy c:\users\default p: /e /i
net use /delete p:
The following example is a .bat script that prints all PostScript files in the c:\temp directory on
the batch server to a printer on a remote Windows system. To use the script, ensure that a local
batch queue has been created, enabled, and started; that the queue’s default shell is the
cmd.exe program; and that your system has access to the printer on the remote Windows
system.
REM This script will do the following:
REM
REM 1. Associate a remote printer on a Windows system
REM (\\machine\printer) with a local printer port.
REM 2. Copy files in c:\temp that end in .ps to the local printer

REM port.
REM 3. Remove the printer association.
REM
net use lpt1: \\machine\printer
cd c:\temp
for %%I in (*.ps) do copy %%I lpt1:
net use /delete lpt1:
Submitting a Job
To submit a job to be run on the batch server on your system:
2. Select a queue listed in the server view, or select the queue view for that queue.
3. Ensure that the selected queue is enabled and started.
4. Select Job > Submit, or click Submit Job on the toolbar.

Intergraph Batch Manager provides tabbed pages in the Job Submit dialog for the following job
parameter categories:
General Sets basic information about the job.
Scheduling Sets the parameters associated with scheduling the job for execution.
Notification Sets the notification preferences for the job.
Output Specifies how output should be handled for the job.
Resources Configures job resources needed for the batch job.
File Staging Describes how necessary files for the job are handled.
Advanced Sets advanced job parameters.
The following sections describe basic operational parameters found in the Job Submit dialog,
along with brief instructions for using them when submitting a job.
Setting Basic Job Information

Displays the following basic information about the job.
Job ID
Shows the ID of the job.
Owner
Specifies the user who has submitted the job.
State
Shows the status of the job.

Queue
Specifies the queue to which the job is submitted.
Job Name
Specifies the drawing name for the job. It also displays the model name and the Drawing
Console path, up to 250 characters. If the name surpasses the character limit, it is
truncated. For example, the full path for the drawing name JUB_ATP, 3D Model
Data\Piping Drawings Metric\3D Model Data Piping\3D Model Data Piping-1-0001 can
be shortened to its drawing name, 3D Model Data Piping-1-0001, then to its model name
and drawing name, 3D Model Data Piping\3D Model Data Piping-1-0001.
Script File
Specifies the shell script submitted for execution.
Account Name
Specifies a user-defined string describing the account.
Size
Shows the size of the shell file.
Shell
Displays the currently selected shell for the job. A blank value indicates the default shell for
the queue. This value can be set only at job submission.
Restartable
Controls whether the job is restarted after a system crash, system shutdown, or batch
service shutdown while the job is running.
Setting Job Scheduling Information

Describes the various parameters associated with scheduling the job for execution.
Job Occurs
Sets the execution frequency of a job. Jobs can be scheduled to run once or at regular
intervals. If you choose to run jobs at regular intervals, additional recurring job frequency
controls (Minutes, Hourly, Daily, Weekly, Monthly, or Yearly) appear to the right of this
field. These controls allow you to enter more specific scheduling information. The scheduling
controls can be changed at job submission, and the recurring jobs frequency controls can be
modified for recurring jobs already submitted.
Time Ranges / Range Times
Sets a period of time within a day for the recurring job to run. This option is available only
with Minute(s) and Hourly settings. The Range Times controls are shown after you click
Time Ranges. For example, if you want to schedule an hourly recurring job to run from
15:30 to 22:00, specify 15 Hours, 30 Minutes for the From field and 22 Hours, 00 Minutes
for the To field.
Start Date
Specifies the date when a one-time job should be run or when the execution series of a
recurring job should begin. This setting can be changed at any time before the end date.
End After

Specifies how many times the job is run before its execution series ends
No End Date
Sets the recurring job to run indefinitely.
End By
Specifies an end date for the execution series of the job.
Start Time
Specifies the time the job is allowed to start. These fields can be changed at job submission
and at any time before the end date for submitted recurring jobs.
Current Time
Uses the submission time of the job as its start time. This field can be changed at job
submission and at any time before the end date for submitted recurring jobs.
Next Occurrence
Shows the date and time of the next occurrence of the recurring job. This read-only field
appears only for recurring jobs (on page 47). It is calculated by Batch Services.
Creating Recurring Jobs

If you have a task that recurs on a regular basis, such as a nightly backup, you can schedule it
as a recurring job. You only schedule recurring jobs once, and then Batch Services
automatically runs all future occurrences of the job for you.
As an example, we will schedule a system backup to run every Tuesday and Thursday at 7:00
PM, starting on the first of September 2014. To do this:
1. Open Intergraph Batch Manager and select the queue to which you want to submit the
recurring job.
2. Select Job > Submit.
3. Browse for and select the backup script that you want to run.
4. Select the Scheduling tab.
5. Select weekly job frequency by choosing the Weekly radio button.
6. Select a weekly frequency of every 1 week.
7. Select the Tuesday and Thursday checkboxes, making sure that no other checkboxes are
selected.
8. Set the effective date to September 1, 2014.
9. Set the start time to 19:00 (7:00 PM). The Next Occurrence field will note that the first
occurrence of the backup job will be run on Thursday, September 1, 2014 at 7:00 PM.

Specifying Job Notification Preferences

Describes the notification preferences for the job. Notification preferences can be set only at job
submission.
Job Start / Job Completion / Job Abort
Specifies the notification option. You can be notified for the following events:
 The job begins execution (Job Start).
 The job completes execution (Job Completion).
 The job is aborted (Job Abort).
By default, Job Abort is selected.
Output File / Error File
Sets whether output files and error files are included with the notification.
Address
Lists mail addresses in the form \\host (event log notification) or user@host (see
Configuring SMTP Mail). Mail will be sent to each recipient. To add an address to the list,
type in the mail address and click Add. You can specify more than one recipient by typing in
addresses separately, and clicking Add after each address. By default, job notification
messages are placed in the event log of the batch server where the job is run.
Address Book
Opens the address book for you to select mail addresses.
Add
Adds the specified recipient to the list box.
Move Up
Moves the selected recipient up in the list of mail addresses.
Remove
Removes the highlighted recipient from the list of mail addresses.
Remove All
Removes all existing recipients from the list of mail addresses.
Specifying How to Handle Job Output

Specifies how the output is handled for the job. This information can be changed only at job
submission.
Output Pathname
Specifies a path and file name indicating where the standard output files are stored. For
local files, type in the complete pathname. You can specify a network pathname using the
\\host\pathname\filename format.
Error Pathname
Specifies a path and file name indicating where the standard error files are stored. For local
files, type in the complete pathname. You can specify a network pathname using the

\\host\pathname\filename format.
Keep Output on Execution Host
Specifies whether the output is kept on the execution host.
No Spooling
Specifies whether output is to be created directly in the specified pathname, rather than
spooling (on page 48) the output and waiting until the job is completed. Spooling is not
supported on remote computers.
Join Output in One File
Disables the Standard Error group box and sends all output to the standard output.
Specifying Job Resource Requirements

Configures the various job resources needed for the batch job.
Execution Priority
Sets the run time priority. The default run time priority is set by the queue. This value cannot
be greater than the execution priority for the queue.
Environment
Enters and updates environment variables. These values can be specified only at job
submission.
Variable
Specifies the environment variable name.
Value
Specifies the environment variable value.
Set
Adds the selected environment variable name to the batch environment of the job.
Remove
Deletes the selected environment variable from the batch environment of the job.
Remove All
Deletes all environment variables from the batch environment of the job.
Add Current Environment Variables
Adds all environment variables in the current environment to the name list. This option is
available only at job submission.

Saving and Restoring Named Batch Jobs

A batch job can be saved to a file for later recall, modification, and submission. This is especially
useful if you want to set up certain job parameters to be used again and again.
For example, you might have a certain set of people you want to notify whenever a backup runs.
You could create a named job that contains the name of your backup script, the queue in which
it should run, and the notification list and save it as BACKUP.NJOB. To run a backup job, you
would then open the named job using the Job Submit dialog, make any necessary changes
(perhaps the start time of the job), and then submit the job. Using this method, you do not have
to re-enter the job's parameters each time you want to run the job.
After you have created a named job, you can access it in a variety of ways. Any of the following
methods open the named job and fill in the Job Submit dialog with all of its parameters:
1. Click Open on the Job Submit dialog box, browse for the named job, and click OK.
2. Drag the named job file from Windows Explorer into the Batch Manager window.
3. Enter the command batchmgr named_job.NJOB at the command prompt, where
named_job is the name of the job file.
4. Double-click on the named job file in Windows Explorer.
The last two methods will not work if Batch Manager is already active since only one
Batch Manager session at a time is allowed.
To create a named job:

The Job Submit dialog displays.
2. Enter the job parameters that you want to save as a named job.
3. Click Save As to name and save your job.
To recall and submit a previously saved named job:

The Job Submit dialog displays.
2. Click Open to browse for previously saved named jobs.
3. Choose the named job you want to recall, and click OK.
Batch Manager loads the saved job parameters into the Job Submit dialog and displays the
name of the job in the title of the Job Submit dialog box.
4. You can submit the job exactly as it was stored in the named job file, or you can make
modifications. If you want to save changes you make, click Save to overwrite the existing
named job, or click Save As to choose a new name for the modified job.
5. Click Submit to submit the job.
Creating a Named Job

To create a named job:

1. Select Submit from the Job menu to display the Submit dialog box. See Submitting a Job
(on page 38) for more information about the Submit dialog box.
2. Enter the job parameters that you wish to save as a named job.
3. Select Save As to name and save your job.
Submitting a Named Job

To recall and submit a previously saved named job:
1. Select Submit from the Job menu to display the Submit dialog box.
2. Select Open to browse for previously saved named jobs.
3. Choose the named job you wish to recall, and select OK. Batch Manager loads the saved
job parameters into the Job Submit dialog, and displays the name of the job in the title of the
Job Submit dialog box.
4. You may submit the job exactly as it was stored in the named job file, or you can make
modifications. If you wish to save changes you make, select Save to overwrite the existing
named job, or select Save As to choose a new name for the modified job.
5. Select Submit to submit the job.

Glossary
account mapping
The process of determining the account name to use when running jobs. Batch Services
requires an account name and password to use when running jobs. To perform account
mapping, the server tries to match the job owner with an account mapping entry.
batch job
A batch job is the full set of instructions to Batch Services to perform a given task or set of tasks
on a computer system. The job itself is identified with a script, or a file that can be interpreted by
some program to perform a set of instructions. An example of a script is a .BAT file, which is
interpreted by the CMD.EXE program.
A unique job identifier or jobid identifies each job. No two jobs will have the same jobid. See also
job and shell.
batch queue
A batch queue accepts requests to execute scripts or commands from the keyboard as if the
user submitting the request were logged in to the system. Jobs are executed in a batch queue.
The resulting output returns to the directory from which the original requestor submitted the job.
You can request the output to remain on the executing node or return to a remote node.
Batch queues can also have a list of shells associated with them, allowing an administrator to
configure a queue to run certain types of scripts. For example, a batch queue may be set up to
run scripts for the Perl program. See also queue.
batch server
A Windows service that processes batch jobs, and maintains queue and job information. A
Batch Server is also the system on which Batch Services runs. The SmartPlant Batch Server is
a system service that may be controlled using the Services icon on the Control Panel.
default queue
The queue to which a job is assigned when a user does not specify a queue.
default shell
The shell that is used to run a job submitted to a queue when a user does not specify a shell for
that job.
disabled
A queue state in which the queue will not accept new jobs.
enabled
A queue state in which the queue will accept new jobs.
execution host
The computer where a batch job is run.

Glossary
hold
A delay in running a job submitted to a queue. A held job will not run until the hold is released, or
the job is deleted from the queue.
A user hold may be placed on a job submitted by that user when the job is submitted. A user
hold can be released either by the submitting user, or by a user with operator or manager
privileges on the server.
A user with operator or manager privileges may place an operator hold on a job, after the job is
submitted but before it runs. Only a user with operator or manager privileges can release an
operator hold.
When a job is being held, the job will remain in the queue until it is deleted or released. It will not
run while the hold is in place. See also privilege.
inflow state
The state of a queue with regard to accepting jobs. See also queue state, enable, disable.
job
A set of instructions needed to perform a given task or set of tasks on a computer system. See
also batch job and shell.
job identifier (job ID)
A unique alphanumeric string that identifies a job. A batch job ID is in the form jobid.orighost,
where jobid is a sequentially assigned number up to 5 digits in length, and orighost is the name
of the system from which the batch job originated.
When a job is successfully submitted, it is assigned a unique job-id. The job-id can be used to
reference the job. No two jobs will have the same job-id.
manager
See privilege.
operator
See privilege.
outflow state
The state of a queue with regard to processing jobs. See also queue state, started, stopped.
per-process file size limit
The file size limit indicates the maximum total file size used by a request. This value is not used
in Windows.
pipe queue
A pipe queue routes requests to another queue. Pipe queues can accept either a batch request,
or a request from another pipe queue. A pipe queue receives the request and sends it to the first
available queue in its destination list that will accept the request. The destination list may contain
any queue type. Pipe queues are normally used to create a connection to a remote batch
queue.

Glossary
privilege
An operational permission level assigned to every Batch Services user. Non-privileged users
can submit jobs to queues to which they have been granted access; operators can issue
commands that directly affect queue management; and managers can control all aspects of
Batch Service operation.
queue
A queue is a waiting line in which job requests reside until they are processed. A queue can
control the number of jobs submitted to it, the number of simultaneous jobs, and the execution
priority of those jobs. A queue can also restrict the users and groups that have access to it. The
batch system supports batch queue and pipe queue.
queue state
A queue has two states: the inflow state and the outflow state.
Inflow State - The inflow state is either enabled or disabled. An enabled queue will accept new
jobs that are submitted or transferred to it; a disabled queue will not.
Outflow State - The outflow state is either stopped, started, or stopping. A stopped queue will
not run the jobs it contains. A queue must be started in order to run jobs.
Example
An "enabled/stopped queue" is a queue that will accept jobs but not run them.
See also enabled, disabled, started, stopped.
queue view
The view in Batch Manager that shows information on the jobs in a queue.
recurring jobs
Jobs scheduled to run more than once at a regular interval. Use the Job Submit\Scheduling tab
in Batch Manager to submit recurring jobs. Hourly, daily, weekly, monthly, and yearly intervals
are available.
scheduling priority
The scheduling priority, or "intra-queue priority," is used for scheduling the order of job execution
within the queue. The priority value must be in the range of [-1024..1023].
script
A file that contains instructions for the execution of a batch job.
server view
The view in Batch Manager that shows information about the operation of one or more queues.
shell
An executable program that can be used to run a script. For example, cmd.exe is a shell that
can be used to run .bat scripts. See also script.

Glossary
spooling
The process of storing a file internally by Batch Services until a batch job ends, and then
returning the files to the intended directories. Spooling is not supported on remote computers.
started
A queue state in which the queue will run jobs submitted to it.
stdin, stderr, stdout
These are standard streams for input, output, and error output.
By default, standard input (stdin) is read from the keyboard, while standard output (stdout) and
standard error output (stderr) are printed to the screen.
stopped
A queue state in which the queue will not run jobs submitted to it.

Index
starting • 35
A status • 36
access to desktop • 12 stopping • 35
account mapping • 12, 45, 48 Batch Manager
basic information • 38 account mapping • 12, 48
job output • 41 adding destinations • 34
notification • 41 adding shells • 33
resources • 42 default shell • 33
scheduling • 39, 40 disabling • 34
submitting • 38 enabling • 34
Add Actions to Queue • 19 modifying • 30
adding destinations • 34 starting • 35
batch • 27 status • 36
pipe • 29 stopping • 35
Adding Destinations to a Pipe Queue • 34 adding destinations • 34
adding shells • 33 adding shells • 33
basic information • 38 batch job • 45
job output • 41 creating queues • 27
notification • 41 default shell • 33
resources • 42 deleting queues • 29
scheduling • 39, 40 disabling queues • 34
submitting • 38 enabling queues • 34
Adding Shells to a Batch Queue • 33 granting privileges • 23
named batch job • 43
B overview • 22
queue status • 36
batch job • 45
queue view • 48
basic information • 38
queues • 27
batch • 27
removing privileges • 23
creating named • 44
server view • 48
job output • 41
setting default queue • 31
named • 43, 44
starting queues • 35
notification • 41
status bar • 22
pipe • 29
stopping queues • 35
resources • 42
submitting named batch job • 44
creating • 27, 44
using • 22
submitting • 44
views • 22
scheduling • 39, 40
Batch Processing - Intergraph Smart Batch
script • 37
Services • 17
default • 31
batch queue • 45, 48
submitting • 38
batch server • 45, 48
adding destinations • 34
Batch Services
adding shells • 33
account mapping • 12, 48
creating • 27
batch job • 45
default shell • 33
compatibility with network adapters • 11
deleting • 29
components • 10
disabling • 34
destination directory for product files • 12
enabling • 34
getting started using • 10
modifying • 30
installation requirements • 11

Index
installing • 12 enabling queues • 34

named batch job • 43 execution host • 45, 48
privileges • 23
queues • 27 G
removing • 22
setting default queue • 31 Getting Started • 10
starting • 12, 16 Getting started using Batch Services • 10
stopping • 16 Granting Batch Service Privileges • 23
using Batch Manager • 22
Batch Services Components • 10 H
Batch Services Defined • 9 hold • 46
Batch Services Features • 9
Batch Services Hardware/Software
Recommendations • 11
I
Batch Services Help • 6 inflow state • 46, 48
Batch Services Overview • 8 disabled • 48
enabled • 48
installation requirements • 11
C Installing and Configuring Batch Services •
Changing Queue Properties • 30 11
Command Line Installation (Silent Install) • installing Batch Services • 12
14 Installing Intergraph Batch Services • 12
Configure Account Mappings • 25 Intergraph
Configure Queues for Jobs • 32 finding on the Internet • 8
Configuring the Batch Services Server for Internet
Drawings Tasks • 17 finding Intergraph • 8
Create a Template • 20
Create Batch Services Queues • 28
Creating a Batch Queue • 27
J
creating a named batch job • 44 job • 46, 48
Creating a Named Job • 44 job hold • 48
Creating a Pipe Queue • 29 job ID • 48
Creating a Script • 37 job identifier (job ID) • 46
Creating and Deleting Queues • 27
Creating and Managing Queues • 27 M
Creating Recurring Jobs • 40 Making Other Batch Servers Available • 29
creating script • 37 manager • 46
D N
default queue • 45, 48 named batch job • 43
default shell • 33, 45, 48 creating • 27
Deleting a Queue • 29 submitting • 44
desktop access • 12 network adapters and Batch Services • 11
disabled • 45
disabling queues • 34
Displaying Queue Status • 36 O
DNS • 11 online documentation • 6
Drawings Batch Dialog Box • 18 operator • 46
Optional Schedule Properties Dialog Box •
E 21
outflow state • 46, 48
enabled • 45 started • 48
Enabling and Disabling a Queue • 34

Index
stopped • 48 Specifying Job Notification Preferences • 41

Specifying Job Resource Requirements •
P 42
spooling • 48
per-process file size limit • 46 started • 48
pipe queue • 46, 48 Starting and Stopping a Queue • 35
Preface • 6 Starting and Stopping Batch Services • 16
privilege • 47, 48 starting Batch Services • 12, 16
privileges starting queues • 35
granting • 23 status bar • 22
removing • 23 stdin, stderr, stdout • 48
product directory for Batch Services • 12 stopped • 48
stopping Batch Services • 16
Q stopping queues • 35
queue • 47, 48 submitting a batch job • 38
inflow state • 48 Submitting a Batch Job • 37
outflow state • 48 Submitting a Job • 38
queue state • 47, 48 submitting a named batch job • 44
queue status • 36 Submitting a Named Job • 44
queue view • 47, 48 support • 6
queues • 27
adding destinations • 34 T
adding shells • 33 TCP/IP • 11
creating • 27 training • 6
default shell • 33
deleting • 29
disabling • 34, 36 U
enabling • 34 Understanding the Batch Manager Interface
modifying • 30 • 22
properties • 30 Using Batch Manager • 22
setting default • 31
starting • 35 V
stopping • 35
views • 22
R
recurring jobs • 47
removing Batch Services • 22
Removing the Batch Service • 16
S
Saving and Restoring Named Batch Jobs •
43
Schedule [Task] Dialog Box • 20
scheduling priority • 47
script • 47, 48
server view • 47, 48
Setting Basic Job Information • 38
Setting Job Scheduling Information • 39
Setting the Default Queue • 31
shell • 47, 48
Specifying How to Handle Job Output • 41

Batch Services Quick Start Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Batch Services Quick Start Guide

Uploaded by

Copyright:

Available Formats

Intergraph Batch Services

Quick Start Guide

U.S. Government Restricted Rights Legend

Intergraph Batch Services Quick Start Guide 2

Intergraph Batch Services Quick Start Guide 3

Batch Services Overview ............................................................................................................................ 8

Installing and Configuring Batch Services ............................................................................................. 11

Using Batch Manager ................................................................................................................................ 22

Creating and Managing Queues .............................................................................................................. 27

Submitting a Batch Job ............................................................................................................................ 37

Intergraph Batch Services Quick Start Guide 4

Specifying Job Notification Preferences ......................................................................................... 41

Intergraph Batch Services Quick Start Guide 5

About This Document

Finding Additional Batch Services Information

Finding Operating System Information

Getting Documentation and Training

Intergraph Batch Services Quick Start Guide 6

Getting Telephone Support

Finding Intergraph on the Internet

Intergraph Batch Services Quick Start Guide 7

Batch Services Overview

Intergraph Batch Services Quick Start Guide 8

Batch Services Defined

Batch Services Features

Intergraph Batch Services Quick Start Guide 9

Batch Services Components

Intergraph Batch Services Quick Start Guide 10

Installing and Configuring Batch

Batch Services Hardware/Software

Server Operating Systems

Client Operating Systems

Intergraph Batch Services Quick Start Guide 11

 Windows 8.1 64-bit

Installing Intergraph Batch Services

Intergraph Batch Services Quick Start Guide 12

7. On the License Agreement page, select your country.

10. Click Next.

Intergraph Batch Services Quick Start Guide 13

12. Click Next.

Command Line Installation (Silent Install)

Intergraph Batch Services Quick Start Guide 14

Intergraph Batch Services Quick Start Guide 15

Starting and Stopping Batch Services

Removing the Batch Service

Intergraph Batch Services Quick Start Guide 16

Configuring the Batch Services Server for Drawings

Batch Processing - Intergraph Smart Batch Services

Drawings Batch Dialog Box (on page 18)

What do you want to do?

Intergraph Batch Services Quick Start Guide 17

Drawings Batch Dialog Box

 Remove - Removes an action from the queue.

Intergraph Batch Services Quick Start Guide 18

Add Actions to Queue

Intergraph Batch Services Quick Start Guide 19

Schedule [Task] Dialog Box

Intergraph Batch Services Quick Start Guide 20

Optional Schedule Properties Dialog Box

Intergraph Batch Services Quick Start Guide 21

Using Batch Manager

Understanding the Batch Manager Interface

Figure 1: Batch Manager

Intergraph Batch Services Quick Start Guide 22