Configure the scheduler on an alternate server - SmartPlant Foundation - IM Update 46 - Help - Hexagon

SmartPlant Foundation Help

Language
English
Product
SmartPlant Foundation
Search by Category
Help
SmartPlant Foundation / SDx Version
10
SmartPlant Markup Plus Version
10.0 (2019)
Smart Review Version
2020 (15.0)
  1. Install the software on the computer designated as the dedicated schedule server using SmartPlant Foundation Server Manager.

  2. Use SmartPlant Foundation Server Manager to set up a secondary site for the scheduler. During site creation, select the Secondary Site option and provide the values for the host name and primary site name.

    • The wizard determines the name of the Config Service for the primary site, but you must ensure the secondary scheduler server is set to use the same Config Service as the primary server. For example, SPFConfigService.

    • The application pool identity for the secondary site must be a valid user on the computer that hosts the Config Service. This could either be a domain account or a common local user. Use Internet Information Services (IIS) Manager to update the application pool identity, if necessary.

  3. On the client computer, configure a server site (SPFSite object) that contains the URL to the dedicated scheduler server secondary site and relate it to the scheduler object.

  4. On a client computer connected to the primary server, create a site object with the File > New > Administration > Server Site command. When you create the site object, select the Is Active option.

  5. Find the scheduler object you want to run on the secondary alternate server with the Find > Administration > Schedulers command. You can also create new scheduler objects.

  6. Drag and drop the site onto the scheduler to create the relationship. This relationship directs the scheduler tasks to the alternate server.

  7. If the scheduler is already started, stop and restart the scheduler to make the change.

    • Only ReportScheduler and PublishFileScheduler are supported on alternate servers.

    • When configuring ReportScheduler on an alternate server, ensure the SPFViewDir path is the same as the primary server SPFViewDir path.

    • When configuring PublishFileScheduler on an alternate server, ensure the Oracle client software has TNS connections to the primary site database.