cancel
Showing results for 
Search instead for 
Did you mean: 

Information Steward clustering question?

Former Member
0 Kudos

Hi All,

We planned the below architecture for the Information Steward/DS/IPS environment.

1)     Server 1       -      IPS + DS MC/APS/Server Manager + IS Full product

2)     Server 2       -      IPS + DS MC/APS/Server Manager + IS Full product

3)     Server 3        -     DS Job Server 1

3)     Server 4        -     DS Job Server 2

3)     Server 5        -     DS Job Server 3

3)     Server 6        -     DS Job Server 4

All the DS Job servers will point to same repository

All the IS Job servers will point to same repository

All the IPS CMS will point to same repository

To make the DS job servers in clustered mode I will create DS Server Group and include the 4 job servers from 4 servers and 4 job servers will share the same cache space.

IPS by default provides Clustering/Load Balancing when primary and secondary pointing to same CMS DB.

Now my question how the information steward clustering works?

Do we have to perform any configuration to enable IS clustering?

Does IS job servers have any default load balancing algorithm?

If IS has auto load balance mechanism how it will route the requests to DS server group instead of single job server on any server?

-- Gopal

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Gopal and the wider community,

I am also looking for the answer to this question. If I create 2 Info Steward Job Servers on different physical servers I can place them in a Job Server Group, but I can't see how Info Steward is ever aware of this group name so how can any sort of load balancing occur?

Many thanks

Mike

aasavaribhave
Advisor
Advisor
0 Kudos

Please refer to IS master guide for more details but in short:

You can add a DS job server using DS server manager\ svrcfg and add IS repo to it. You do not create a server group of DS job servers associated with IS repos manually,

Server group for DS job servers associated with IS repo is created by default  when 1st job server is added to IS repo - Look at AL_MACHINE_INFO table in IS repo. When a new DS job server is added to landscape and associated with IS repo - that job server gets added to existing IS server group.

task scheduling\ execution is managed via IS Job Server that can be found in CMC > Servers > Enterprise Information Management Services section and auto - load balance is done.

Former Member
0 Kudos

Hi Aasavari,

Many thanks for the information. I did not realise that the AL_MACHINE_INFO table was used for this purpose so good to understand that.

I have another question which I will start a new thread for.

Best regards,

Mike