DSXchange

Posted: **Tue Feb 14, 2012 7:52 pm**

Several ISD jobs with sparse lookups repeat the start/abort/start/abort, etc., cycle every night while DB2 goes offline for backups. Are there any graceful options to avoid the constant churn during the DB2 backup window?

Posted: **Wed Mar 14, 2012 2:36 pm**

Are your web services customer facing? Having web services failing is not pretty and can create quite a mess for you to clean up.

Have your DBA's allow a specific username access to DB2 while it is quiesced, as long as your user is only reading data and not writing into the database there is no harm in allowing you to read while backups are in progress.

grant quiesce_connect on database to username

Posted: **Wed Mar 14, 2012 7:38 pm**

OK, thanks for the tip! They are customer facing, but not during the backup window, so I suppose they could simply be undeployed and redeployed too. Of course it would be easier to leave them up and running 24x7. I will discuss it w/ DBA...

Posted: **Sat Apr 19, 2014 8:51 pm**

I created scripts that undeploy and deploy the ISD applications using the command line. Scheduled scripts using crontab.

Posted: **Wed May 07, 2014 5:42 pm**

Hi
Could you share the script to deploy/undeploy a webservice?

Right now i have to use Service Directory itself to deploy/undeploy them.

Where can i read up to find out all command-line utilities that are useful for manipulating DataStage jobs or Service Director?

Thanks

Posted: **Wed May 07, 2014 9:11 pm**

Here is a sample start script. Substitue in your own paths and values for AAA, BBB, etc.

The encrypted credential files are an optional, very nice feature for avoiding clear-text passwords in scripts and process commands.

Code: Select all

#! /bin/ksh
#
# Script:
# StartISD_AAA.ksh
#
# Change Log:
# MM/DD/YYYY NAME - created script

# set environment variables
export ISDADMIN_PATH=/opt/IBM/InformationServer/ASBNode/bin
export AUTH_FILE=/MyPath/ToMyEncrypted/CredentialFile.txt

# start Information Services Director applications one by one
echo "--------------------------------------------------"
echo "starting Information Services Director applications..."
date
echo "--------------------------------------------------"
$ISDADMIN_PATH/ISDAdmin.sh -authfile $AUTH_FILE -action deploy -project PPP -application BBB
$ISDADMIN_PATH/ISDAdmin.sh -authfile $AUTH_FILE -action deploy -project PPP -application CCC
$ISDADMIN_PATH/ISDAdmin.sh -authfile $AUTH_FILE -action deploy -project PPP -application DDD

echo "--------------------------------------------------"
echo "start complete"
date
echo "--------------------------------------------------"

The stop script is just like above with minor syntax differences only:

Code: Select all

$ISDADMIN_PATH/ISDAdmin.sh -authfile $AUTH_FILE -action undeploy -application BBB
$ISDADMIN_PATH/ISDAdmin.sh -authfile $AUTH_FILE -action undeploy -application CCC
$ISDADMIN_PATH/ISDAdmin.sh -authfile $AUTH_FILE -action undeploy -application DDD

Here is one link to an ISD command line topic.

http://pic.dhe.ibm.com/infocenter/iisin ... tions.html

While you're in the Information Center, search on "command line" to find many more, search on "encrypt" etc.

Posted: **Fri May 09, 2014 7:40 am**

Thanks for showing the code!

DSXchange

ISD job will start/abort/start/abort, etc.

ISD job will start/abort/start/abort, etc.

Re: ISD job will start/abort/start/abort, etc.