Configuring Enterprise Services

The Enterprise Services Setup program installs all of the Enterprise Services files, but does not deploy the Enterprise Services Server.    This must be done separately using the Configuration tool.   Although this configuration is mostly pre-populated with defaults, there are some which need to be supplied.   The configuration application is used to adjust the settings of Enterprise Services both during installation and at times when the operating environment changes.   After the initial installation process, this application is automatically opened.  
 

 

ES Configuration Initial Opening Screen

 
 

Note_200

Enterprise Services comes automatically populated with the IIS Application Pools listed above.  Adding IIS Sites will automatically generate an associated IIS Application Pool unless otherwise selected from the drop down menu of Application Pools.  Custom IIS Application Pools may be added and referenced as required.

 

dropdown Toggle        Add New IIS Site

To add a new IIS web site, highlight the IIS Sites and click on the Add button or use the sub menu option Add Site.

ES Configuration Initial Reset Add New Site
 

Warning Red Button_200pix

The Reset IIS Server menu option should only be used when experiencing IIS Server issues.   Will temporarily shut down entire IIS website and all web sites that utilize the IIS Server.  

 
Site Information fields will be automatically populated with Enterprise Services protocol but can be changed to meet your organizational requirements.

ES Configuration Initial Reset Add New Site_2

 

Note_200

Enterprise Services contains a default application pool with all the necessary ES3 security settings.

 
ES Configuration Initial Reset Add New Site_3

 
dropdown Toggle        Add New Web Application

To add a new Application, highlight the Default Web Site and click on the Add button or use the sub menu option Add Application.

ES Configuration Initial Default Web Site Add App

 
dropdown Toggle        IIS Configuration

The next step in the installation process is to configure how administrators and users will access Enterprise Services via the new Default Web Application Site.    This is where you specify the method used for gaining access to Enterprise Services, not the connection to IBM® Cognos® TM1®.  How the user connects to IBM® Cognos® TM1® in specified in the TM1 Connection tab.  Enterprise Services currently supports two authentication methods:
 

Integrated - Use this setting if users will be connecting to IBM® Cognos® TM1® using integrated login.  Users must be logged in to the domain ( user must be logged into the domain (which should happen during normal windows log in) and those credentials are then used to access TM1.

Anonymous - Allows all users to access Enterprise Services that are currently in the IIS work pool.

 

Check_200

It is important to understand that configuring access to Enterprise Services does not enable users to access data in IBM® Cognos® TM1®.   This configuration method is an extra layer of security to enable specific users access to the Enterprise Services Manager.

 

Once the authentication method is selected, the Virtual Directory Name field should reflect the name of the new default web application site.  New IIS Configuration information will be automatically populated with Enterprise Service protocol.  Specify the path for the Physical Directory with your organization requirements. Enterprise Services automatically populates the Physical Directory field where the program was installed on the server.  

In the Application Pool field, specify the pool where IIS will pull security settings.  Adding new web application sites will automatically generate an associated IIS Application Pool unless another is otherwise selected from the drop down menu of Application Pools.  

ES Configuration ES3 App Pool
 

Check_200

The only time an Application Pool is added to IIS is when a new Web Application Site is created. Pools can be used by any number of Default Web Application Sites and will not be deleted when attached Web Application Site is removed.  

 
dropdown Toggle        Configuring TM1 Connection

The TM1 Connection tab provides the information necessary to connect with IBM® Cognos® TM1®.  You must supply the following information:

 

TM1 Configuration

oAdmin Host

oTM1 Server Name

oSSL Cert ID

TM1 Installation Directory

SSL Cert File Path

Connection Method

TM1 Administrative Credentials

oUsername

oPassword

 

ES Configuration TM1 Connection

 

Note_200

After the initial Default Web Application Site is created, Enterprise Services will remember the last credentials provided, and populate all fields in the new Web Application Site with the corresponding information.
 
 

Best_200

Double clicking on the name of the Web Application Site will bring up the edit mode in Enterprise Services.  From here all configuration settings can be changed except the Virtual and Physical Directory information.  Names are locked to help with tracking of Application Sites.

 
dropdown Toggle        Configuration Test

The Configuration Test tab is where you can run through the different validation steps to ensure the system is properly configured before performing the install.  It is not required to run this test; as the installation process will perform the configuration test automatically.   Press the Run button to test the system manually, or click on the Finish button to complete the configuration process.

 

ES Configuration Test

 

 

Note_200

If this is the first time installing (or re-installing) Enterprise Services, the Web Connection test may fail when running the test manually. Make sure the IBM® Cognos® TM1® Server has been installed and the service has been started.   Press the Finish button to complete installation.

 

dropdown Toggle        Sub Menu Options

Launch ES Application - Launches the full Enterprise Services application.

 

Explore Application - Opens Windows Explorer to the physical directory where individual ES (and Non-Conforming) Web Application Site ESWeb data is located.
 

Add ES Application - Same feature as the Add button on the toolbar.  Adds new IIS Site or Web Application Site to the application.
 

Edit ES Application - Opens Enterprise Services in Edit mode enabling changes to all configuration settings (except for the Virtual and Physical Directory information.)
 

Upgrade the ES Application -If a new version of Enterprise Services is downloaded and installed, there may be older Web Application sites that need to be updated.  Upgrading the ES Application option will only update DLLs or functional code.  Existing Web Application Site data, personalized views and/or reports within the application will remain.

 

ES3 - Upgrade ES Application

 
 

Remove Application - Same feature as Remove button on the toolbar.  Removes individual Web Application Sites from Enterprise Services.

 

Check_200

Removing individual Web Application Sites will not delete the corresponding Application Pool. Pools can be used by any number of Default Web Application Sites and can only be deleted by highlighting the Application Pools tree menu, clicking on the individual Application Pool name on the right panel, and pressing the Remove button in the menu.

 

dropdown Toggle        Adding Nested Web Application Sites and Non-Conforming ES3 Applications

Enterprise Services gives you the flexibility to add Nested Web Application Sites and Non-Conforming ES3 Applications.

 

Nested Web Application Sites

Nested Web Application Sites are sites located underneath Default Web Application Sites.  To add a Nested Web Application Site, highlight the parent-level Web Application Site and click on the Add button or use the sub menu option Add Site.

ES Configuration Nested Web Site 2

Follow the same configurations steps as when you added a new Default Web Application Site.

Note_200

NOTE:  The Virtual Directory Name field will reflect the name of the Default Web Application Site.  By changing the Virtual Directory Name, Enterprise Services will create a new Application Pool associated with the Nested Web Application Site unless another is selected from the drop down menu of Application Pools.

ES Configuration Nested Web Site
 

Notice that the Physical Directory is nested under the parent ES3 Web Application site.  By default Enterprise Services automatically populates the new Nested Web Application Site credentials underneath the parent Web Application site.  (i.e. IIS Sites show the new nested application as ES3/ES_Nested.)

ES Configuration Nested Web Site 3

 

Non-Conforming Web Application Sites

Companies with existing Web Applications that were not created using Enterprise Services, can manage and even nest ES Web Application Sites directly from Enterprise Services.  Non-Conforming Applications are notated with an Red ! Iconicon.  Configuration information is reflected in the right hand panel.  Note that Non-Conforming Web Application Sites do not contain Version information.

Non Conforming ES3 Site

To add a Nested Web Application Site, highlight the parent-level Web Application Site and click on the Add button or use the sub menu option Add Site.