Install DS engine on Database server

[le thuong]

We have 1 server for Datastage (with all tiers installed) and 1 server for the DBMS SQL Server.
Best practice for performance would be assigning the DB stage (ODBC or other native - when reading from the database or writing to the database) to a node corresponding to the DB server in the configuration file ?
In this case, do I have also to install the Datastage engine tier on the DB server ?

Thanks for your time

[ray.wurlod]

For absolutely best performance having the DataStage engine co-resident with the database server is the way to go. But performance is usually satisfactory where they are on different machines connected by a very high speed network.

[le thuong]

For absolutely best performance having the DataStage engine co-resident with the database server is the way to go. But performance is usually satisfactory where they are on different machines connected by a very high speed network.

I found in Planning,Installation and Configuration guide (page 80):

"Copying parallel engine components to system nodes (Windows) When you configure an MPP system, you must copy the parallel engine components to all of your processing nodes."

This seems to indicate that it is mandatory to install DS engine on all physical servers ?

I defined the following configuration file (2 servers BERNINI3 and monet) where Datastage is installed on BERNINI3 only and I got an error when Checking the configuration file:

{
node "node1"
{
fastname "BERNINI3"
pools ""
resource disk "E:/IBM/InformationServer/Server/Datasets" {pools ""}
resource scratchdisk "E:/IBM/InformationServer/Server/Scratch" {pools ""}
}
node "node3"
{
fastname "monet"
pools "sourceSQL"
resource disk "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data" {pools "sourceSQL"}
resource scratchdisk "E:\Tmp" {pools "sourceSQL"}
}
}

##I IIS-DSEE-TFCN-00001 16:21:53(000) <main_program>
IBM WebSphere DataStage Enterprise Edition 8.1.0.4987
Copyright (c) 2001, 2005-2008 IBM Corporation. All rights reserved



##I IIS-DSEE-TFCN-00006 16:21:53(001) <main_program> conductor uname: -s=Windows_NT; -r=2; -v=5; -n=BERNINI3; -m=Pentium
##I IIS-DSEE-TCOA-00067 16:21:53(002) <main_program> OS charset: windows-1252.
##I IIS-DSEE-TCOA-00068 16:21:53(003) <main_program> Input charset: UTF-8.
##I IIS-DSEE-TFSC-00001 16:21:53(004) <main_program> APT configuration file: E:/IBM/InformationServer/Server/Configurations/aptconfigtest.apt
rsh: connection to server failed: monet(514): 10038: An operation was attempted on something that is not a socket.
##W IIS-DSEE-TFPM-00152 16:22:23(000) <main_program> Accept timed out retries = 8
##E IIS-DSEE-TFPM-00153 16:22:23(001) <main_program> The section leader on monet died
##E IIS-DSEE-TFPM-00356 16:22:23(002) <main_program>

**** Parallel startup failed ****

This is usually due to a configuration error, such as
not having the Orchestrate install directory properly
mounted on all nodes, rsh permissions not correctly
set (via /etc/hosts.equiv or .rhosts), or running from
a directory that is not mounted on all nodes. Look for
error messages in the preceding output.


##I IIS-DSEE-TFPM-00177 16:22:23(003) <main_program> Step started on node BERNINI3; it uses 2 nodes.
The program running the step is /E=/IBM/InformationServer/Server/PXEngine/bin/orchadmin.exe.

##I IIS-DSEE-TFPM-00178 16:22:23(004) <main_program> The ORCHESTRATE startup program in /E=/IBM/InformationServer/Server/PXEngine/bin/standalone.exe is being used.

##I IIS-DSEE-TFPM-00181 16:22:23(005) <main_program> A startup script is not being used.

##I IIS-DSEE-TFPM-00183 16:22:23(006) <main_program> The TCP port being used for startup is 10,000; the associated socket number is 3.

##I IIS-DSEE-TFPM-00184 16:22:23(007) <main_program>
Node status:


##I IIS-DSEE-TFPM-00185 16:22:23(008) <main_program> BERNINI3 -
##I IIS-DSEE-TFPM-00186 16:22:23(009) <main_program> OK

##I IIS-DSEE-TFPM-00185 16:22:23(010) <main_program> monet -
##I IIS-DSEE-TFPM-00187 16:22:23(011) <main_program> rsh issued, no response received


##E IIS-DSEE-TFPM-00247 16:22:23(012) <main_program> Unable to contact one or more Section Leaders.
Probable configuration problem; contact Orchestrate system administrator.

##E IIS-DSEE-TFSC-00011 16:22:23(013) <main_program> Step execution finished with status = FAILED.
##E IIS-DSEE-TCOA-00069 16:22:23(014) <main_program> ERROR: check configuration file failed.