Navigation:  IM Sequencer >

Requirements

Previous pageReturn to chapter overviewNext page

System requirements

 

The IM Sequencer has the following system requirements:

 

.NET 3.5 Framework or higher
Windows 2003 server, Windows 2008 server + R2, Windows XP, Vista or Windows 7
Microsoft Identity Integration Server 2003 (MIIS), Enterprise Edition & Service Pack 1 or higher or Identity Lifecyle Manager 2007 (ILM) or higher or FIM 2010 or higher
Windows Management Instrumentation (WMI)

 

Security requirements client

 

Using the IM Sequencer requires some privileges.

 

If you are using the IM Sequencer locally on the FIM/MIM system the currently logged on accounts needs to be member from the MIISAdmins group or FIMSyncAdmins in case of FIM 2010.

 

Note: The MIISAdmins/FIMSyncAdmins group is a local security group created during the installation off the FIM/MIM server.

 

When you are using the IM Sequencer for a remote FIM/MIM system you can provided the appropriate username & password combination. The account name that you have provided needs to be member from the MIISAdmins/FIMSyncAdmins group

 

If you are member off the "domain admins" group you do not need to specify a username & password combination when connecting to remote FIM/MIM systems, the administrators is always member from the MIISAdmins/FIMSyncAdmins group.

 

Security requirements service

 

The IM Sequencer Service is installed default using the LOCAL_SYSTEM account. It is advised to change this account to a special service account, this service account needs to meet the following requirements:

       

The IM Sequencer Service needs to have access to the Event Log to write his own events.
 
The service account needs to have the special right logon as a service, this right is provided during installation (if question is answered with "yes")
 
Optional If ILM is installed locally, the service account needs to be added to the MIISAdmins/FIMSyncAdmins group. If FIM/MIM is not installed locally and the IM Sequencer only remotely controls FIM/MIM machines this requirement does not apply.
 
Optional: Write access to the log directory if logging is configured outside the installation directory.
 

Adding the service account to the MIISAdmins/FIMSyncAdmins group makes sure the IM Sequencer Service can start the IM Sequencer Client and this does not require any passwords in configuration files and thus is more secure.
 

Local communication
 

The IM Sequencer client uses a TCP connection to communicate with the IM Sequencer service. You will need to allow the IM Sequencer Client to communicate to the network.
 
The default port is 8228. If you want to change the default port you will need to make the following change the following changes
 

In the file IM Sequencer Client.exe.config change the following line:

 

<system.runtime.remoting>

  <application>

    <client>

      <wellknown type="Traxion.IM.Scheduler.RemoteServices.SchedulerEngineService,Traxion.IM.Scheduler"

                url="tcp://localhost:8228/SchedulerEngineService"/>

    </client>

 

To:
 

    <system.runtime.remoting>

  <application>

    <client>

      <wellknown type="Traxion.IM.Scheduler.RemoteServices.SchedulerEngineService,Traxion.IM.Scheduler"

                url="tcp://localhost:<YOUR NEW PORT>/SchedulerEngineService"/>

    </client>

 

 

In the file IM Sequencer Service.exe.config change the following line:

 

<system.runtime.remoting>

  <application>

    <channels>

      <channel ref="tcp" port="8228"/>

 

To:

 

<system.runtime.remoting>

  <application>

    <channels>

      <channel ref="tcp" port="<YOUR NEW PORT>"/>

 

Note: Set the same port in both files, and restart both the service and client, do not change anything else within the <remoting> tag.

 

Note1: When Custom Filtering is used also check this topic

 

IM Sequencer Automation - Webservices

 

From version 5.0 the IM Sequencer service can be contacted via web services. There is a specific setup called IM Sequencer Automation Setup. This installation package contains several ways to communicate with the IM Sequencer service using:
 

- Omada workflow (code method)        - start or stop tasks via workflow, event or custom code methods

- Powershell                                - start or stop tasks via powershell scripts

- Regular webservice (WCF)                - start or stop tasks via the webservice

 

The webservice is registered at default on port 8000. You can change this port if you reconfigure this port within the configuration file IM Sequencer Service.exe.config, specifically this line:

 

<!-- This section contains the WCF configuration, do no manually change these settings -->

<system.serviceModel>

  <services>

    <service name="Traxion.IM.Scheduler.RemoteServices.SchedulerEngineService"

            behaviorConfiguration="SchedulerEngineServiceBehavior">

      <host>

        <baseAddresses>

          <add baseAddress="http://localhost:8000/IMSequencer"/>

        </baseAddresses>

 

The webservice is hosted at default at this url: http://localhost:8000/IMSequencer/SchedulerEngineService

 

Note: For windows 2008 this url is registered (urlacl) for the specific service account, when you change the url you need to manually register the url for the service account before it can be used

 

Note1: You can disable this feature via de IM Sequencer.config file, locate the setting enableWCFService="true" below the ApplicationSettings/service tag (if not found add it) and set the value to true, restart the service to disable the webservice.

 

You can download the IM Sequencer Automation Setup directly from the website www.imsequencer.com/download

 

For more information how to use and configure the IM Sequencer Automation consult the IM Sequencer Installation Guide or read this

 


Page url: http://www.traxionsolutions.com/imsequencer/help/index.html?imsequencerrequirements.htm