Start of Content Area

Background documentation Systems with Master and Slave Index Servers  Locate the document in its SAP Library structure

This section depicts the configuration for systems with master and slave index servers.

One Master Index Server, Two Slave Index Servers

This graphic is explained in the accompanying text

TREX admin tool, Landscape Configuration

Areas Scenario, Scenario Details, and Index

Area

Field

Value

Scenario

Use Backup Index/Queue Servers

 

 

Use Slave Index Servers

!

 

Use a File Server

 

Scenario Details

Use One Shared Backup Server

 

 

Assign Existing Indexes/Queues to New Backup/Slave Servers

 

Index

Search on Master/Backup Server

 

 

Search Version

majority

 

Replication Threads

1

Hosts table (extract 1)

Host

Name Server Mode

Master Index/Queue Server

Slave Index Server for

Preprocessor Mode

mytrexmaster1

1st master

!

 

index

mytrexslave1

slave

 

! mytrexmaster1

search

mytrexslave2

2nd master

 

! mytrexmaster1

search

Hosts table (extract 2)

Host

Base Path

mytrexmaster1

%(SAP_RETRIEVAL_PATH)

mytrexslave1

%(SAP_RETRIEVAL_PATH)

mytrexslave2

%(SAP_RETRIEVAL_PATH)

 

Two Master Index Servers, Two Slave Index Servers Each

One index server per host

This graphic is explained in the accompanying text

TREX admin tool, Landscape Configuration

Areas Scenario, Scenario Details, and Index

As in the previous example

Hosts table (extract 1)

Host

Name Server Mode

Master Index/Queue Server

Slave Index Server for

Preprocessor Mode

mytrexmaster1

1st master

!

 

index

mytrexmaster2

2nd master

!

 

index

mytrexslave1

slave

 

! mytrexmaster1

search

mytrexslave2

slave

 

! mytrexmaster1

search

mytrexslave3

slave

 

! mytrexmaster2

search

mytrexslave4

slave

 

! mytrexmaster2

search

Hosts table (extract 2)

Host

Base Path

mytrexmaster1

%(SAP_RETRIEVAL_PATH)

mytrexmaster2

%(SAP_RETRIEVAL_PATH)

mytrexslave1

%(SAP_RETRIEVAL_PATH)

mytrexslave2

%(SAP_RETRIEVAL_PATH)

mytrexslave3

%(SAP_RETRIEVAL_PATH)

mytrexslave4

%(SAP_RETRIEVAL_PATH)

Two index servers per host

This graphic is explained in the accompanying text

TREX admin tool, Landscape Configuration

Areas Scenario, Scenario Details, and Index

As in the previous example

Hosts table (extract 1)

Host

Name Server Mode

Master Index/Queue Server

Slave Index Server for

Preprocessor Mode

mytrexmaster1

1st master

!

 

index

mytrexslave1

slave

 

! mytrexmaster1

search

mytrexslave2

2nd master

 

! mytrexmaster1

search

Hosts table (extract 2)

Host

Base Path

Services

mytrexmaster1

%(SAP_RETRIEVAL_PATH)

nameserver, preprocessor1,
indexserver1, queueserver, indexserver2

mytrexslave1

%(SAP_RETRIEVAL_PATH)

nameserver, preprocessor1,
indexserver1, queueserver, indexserver2

mytrexslave2

%(SAP_RETRIEVAL_PATH)

nameserver, preprocessor1,
indexserver1, queueserver, indexserver2

TREXDaemon.ini on all hosts (extract)

[daemon]

programs=nameserver, preprocessor1, indexserver1, queueserver, indexserver2

 

 

End of Content Area