Steps to configure Datastage operations console in 8.7

-
Steps to configure Datastage operations console in 8.7
Step1)Creating the operations database schema
Creating the operations database schema for an Oracle database on a UNIX or Linux system
Database : oracle11g


cd $DSHOME/../DSODB/scripts/Oracle11g
./generate_ddl.sh
Checking required files….
Setting required parameters…
Usage: generate_ddl.sh <DSODBTableSpaceName> <DSODBDatafilePath>
Parameters:
<DSODBTableSpaceName>
Name of the operations database tablespace.
<DSODBDatafilePath>
Location where the tablespace data files will be created. It must be an
existing path. Do not add a trailing slash or backslash (/ or \).
Example: /u01/app/oracle/oradata/dbname
For example:
generate_ddl.sh dsodbspace /u01/app/oracle/oradata/dbname
./generate_ddl.sh DSODB_TBS ‘+DATA1′
Checking required files….
Setting required parameters…
Generating the SQL setup files…
Created file DSODB_setup.sql
Created file DSODB_setup_remove.sql
File generation complete
To complete the task please refer to Step B of the README file.
Step2:
To create the database schema and tables, and to grant the required privileges, enter the command:
sqlplus <oracle_system_user/oracle_system_password@database_service_name>
@DSODB_setup.sql <dsodbpassword>
example, enter this command:
sqlplus sys/*****@UISDV1 @DSODB_setup.sql password
Step3)Configuring the connection
The connection parameters are set in the DSODBConnect.cfg configuration file which is stored in the $DSHOME/../DSODB directory in the installation directory
sample config file for oracle database:
# Licensed Materials – Property of IBM
# Copyright IBM Corp. 2011
# DataStage Operations Database Connection Definition for Oracle
# ==============================================================
# The following parameters define the connection to the Operations Database.
# “DBTYPE” must be set to identify which database manager is in use.
# This file is for Oracle. For DB2 and SQL Server databases, copy the file
# ./scripts/DB2_LUW_9_X/DSODBConnect.cfg or ./scripts/SQLServer200X/DSODBConnect.cfg
# into the DSODB directory, then edit it as appropriate.
DBTYPE=ORACLE
# “Driver” is the Java class name for the JDBC driver to be used.
# (The following example is for a connection using the Information Server branded driver.)
Driver=com.ibm.isf.jdbc.oracle.OracleDriver
# “JAR” specifies a jar file that is needed to run the driver.
# The file must be placed in the ASBNode/lib/java subdirectory of the
# InformationServer installation directory on this system unless a full path is specified.
# NOTE that a full path MUST use forward-slashes as separators EVEN ON A WINDOWS SYSTEM.
# The property may be repeated if more than one jar needs to be loaded.
# (The following example specifies the Information Server branded driver.)
JAR=ISoracle.jar
# “URL” is used to identify the database concerned.
# (The following example is for an Oracle database that holds the
# xmeta Information Server repository. Note the inclusion of a port number.)
URL=jdbc:ibm:oracle://localhost:1521;SID=xmeta
# The following specify the username and password to connect to the DSODB schema.
Username=xxxx
Password=xxxx
Modify the URL according to the environment.
Optionally, encrypt the Username, Password, or both parameters The values of one or both of these parameters can be stored in a strongly encrypted form.
/ASBNode/bin>./encrypt.sh
Enter the text to encrypt:
Enter the text again to confirm:
Dec 27, 2011 11:02:04 PM java.util.prefs.FileSystemPreferences$2 run
INFO: Created user preferences directory.
{iisenc}5cpVKdoBUIrd5w/NWkKuwg==
/Server/DSODB/bin>./DSAppWatcher.sh -test
Error: DSODB is turned OFF in the DSODBConfig.cfg file.
Checking Database Connection:
Successfully loaded the database driver.
Successfully connected to the database.
DB Schema version number: 1
Test Failed.
sample SODBConfig.cfg file:
# Licensed Materials – Property of IBM
# (c) Copyright IBM Corp. 2010, 2011
#
# DataStage Operations Database Monitor Configuration
# ===================================================
# Lines in this file are either comments, introduced by a # sign like this,
# or of the form “key=value”. Key lines may be commented out below. If this file is edited,
# the data collection system must be stopped and restarted before changes take effect.
# The following switches the whole data collection system on if set to 1, or off if 0.
# A setting of 0 cannot be overridden at project level -
# however individual projects can be switched off by setting this to 0
# in a copy of this file placed in the project’s directory.
DSODBON=0
# Job Log Events
# ==============
# Normally, all Fatal log messages, Control messages, and the first N Warning messages
# of a run will be captured, except as modified by the following settings.
# Note: The message severity is looked at AFTER any Message Handlers have been invoked,
# which may adjust it or even discard the message altogether.
# The following specifies how many warning messages are to be captured for each run.
# Unless overridden by a “must capture” setting below, after this many warning log
# messages have been turned into events any further warnings will not be sent to the ODB.
# Default is 10. The value is capped at 1000.
# MaxWarnings=10
Now we need to set DSODBON=1 and then test the setup again.
/Server/DSODB/bin>./DSAppWatcher.sh -test
DSODB is turned ON in the DSODBConfig.cfg file.
Link Monitoring is OFF.
Job Run Usage is ON.
Resource Monitoring is ON.
Checking Database Connection:
Successfully loaded the database driver.
Successfully connected to the database.
DB Schema version number: 1
Test Successful.
Server/DSODB/bin>./DSAppWatcher.sh
Usage: DSAppWatcher.sh -start [appname | all] | -stop [appname] | -status [ appname ] | -test
./DSAppWatcher.sh -start
AppWatcher:STARTED
EngMonApp:STARTING
ODBQueryApp:STARTING
ResMonApp:STARTING
Start the IBM InfoSphere™ DataStage® Operations Console.
Procedure
If you are using HTTP, enter this URL from a supported browser:
where
domain is the name or IP address of your InfoSphere Information Server system
port is the port number your InfoSphere Information Server system is configured to use. The default port number for HTTP is 9080
If you are using HTTPS, enter this URL from a supported browser:
where
domain is the name or IP address of your InfoSphere Information Server system
port is the port number your InfoSphere Information Server system is configured to use. The default port number for HTTPS is 9443
Configuring for an MPP or grid environment
a.Edit the RemoteShell.sh file in the /InformationServer/Server/PXEngine/DSResourceTracker/ directory.
#!/bin/sh
# Set to rsh / ssh as appropriate
ssh “$@”
Configuration options for job runs
As a minimum we need to set DSODBON=1 to monitor jobs.
Set DSODBON=1 if you want to capture monitoring data
MonitorLinks 0 or 1 Controls if stage-level and link-level statistics, and references to data locators, are captured at the end of each job run.
Set MonitorLinks=0 if you do not want to capture this data is not to be captured. The default value is 0.
Set MonitorLinks=1 if you want to capture this data.
Configuration Options for System Resource Usage:
ResourceMonitor=1
ResourceNode=servername1
ResourceNode=servername2
ResourceLocalFS=Specifies a file system path whose disk mount point is to be monitored for used and free space.
ResourceRemoteFS=Specifies a file system path on a remote node whose disk mount point is to be monitored for used and free space.
Configuration Options for project monitoring data:

Configuration file

The options that are used to configure the collection of monitoring data for all jobs in all projects are set in the DSODBConfig.cfg configuration file. This system-level configuration file is stored in the /Server/DSODB directory in the installation directory.
Some of the options in the system-level configuration file can be overridden for a specific project by placing a project-level configuration file with the same name, DSODBConfig.cfg, in the project directory.
Starting and Stopping the AppWatcher Process:
Issue this command from the /InformationServer/Server/DSODB/bin directory:
DSAppWatcher.sh –start
DSAppWatcher.sh –stop
Managing the data collection processes using the DSAppWatcher.sh script
Use the DSAppWatcher.sh script to manage the data collection processes.

The DSAppWatcher.sh script takes one of these parameters:
  • -start [ AppName | all ]
  • -stop [ AppName ]
  • -status [ AppName ]
  • -test
Starting a Specified Process:
On Unix and Linux, run DSAppWatcher.sh from the /InformationServer/Server/DSODB/bin directory.
Issue this command to restart the specified process, which is then monitored as normal by the AppWatcher process.
DSAppWatcher.sh -start AppName
AppNames:
AppWatcher
EngMonApp
ODBQueryApp
ResMonApp
Above information is also available in IBM website .








































































Popular posts from this blog









Shrink you container size up to 95%.






-















BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file   








Read more










alma linux: dnf Module yaml error: Unexpected key in data






-















  While applying recent updates to a server running Rocky Linux 8, an error presented itself.   Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3]     The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual.   dnf update libmodulemd     For a detailed explanation as to the cause of this problem.           








Read more