You are on page 1of 30

®

© 2006 IBM Corporation
Job Scheduling Console 8.3 & 8.4



Giulia Giannitrapani
IBM Tivoli Customer Support - TWS L2 Support Engineer

IBM Software Group
2
Contents

Job Scheduling Console 8.3 & 8.4 – What’s new

JSC Troubleshooting steps
 JSC - Determine product version & FP level
 JSC – setting traces
 JSC – Setting ORB Traces
 JSC – Logging

Q&A
®

© 2006 IBM Corporation
Job Scheduling Console – What’s new
IBM Software Group
4
New Features
New Infrastructure base
The Job Scheduling Console is now based on a J2EE infrastructure. It no longer requires the
Tivoli Management Framework.

Creating engines using the Job Scheduling Console
It is now possible to create engines at any time from within the Job Scheduling Console.

New Features of the JS Editor
A new Explorer View is now available for job streams and job stream instances.
Add job definitions ″on the fly″.

 Job stream versioning
Several instances of the same job stream might be present in a single plan.

 Defining draft job streams
It is now possible to define a job stream and mark it as a draft job stream.

 Job Stream Dependency Resolution

 Assigning run cycles & time restrictions to Job Streams
For distributed engines there are improved windows for defining and using run cycles.

Launch TDWC (JSC 8.4 only)



IBM Software Group
5
Old infrastructure base
Java
Based
UI
J
C
F

CORBA
T
W
S

E
n
g
i
n
e

T
W
S

M
a
s
t
e
r

Connector
Scheduling
Model
Production
Plan
Model API Plan API
TMF Managed
Node
T
W
S

E
n
g
i
n
e

T
W
S

D
o
m

M
g
r

Connector
Production
Plan
Plan API
TMF
Managed
Node
T
W
S

E
n
g
i
n
e

T
W
S

F
T
A

Connector
Production
Plan
Plan API
T
W
S

E
n
g
i
n
e

T
W
S

F
T
A

Connector
Production
Plan
Plan API
TMF
Managed
Node
T
W
S

E
n
g
i
n
e

T
W
S

B
a
c
k
u
p

M
a
s
t
e
r

Connector
Scheduling
Model
Production
Plan
Model API Plan API
TMF Managed
Node
TWS 8.2 Architecture
IBM Software Group
6
Java
Based
UI
R
M
I

S
t
u
b
s

RMI / IIOP
T
W
S

E
n
g
i
n
e

T
W
S

F
T
A

Production
Plan
Plan API
T
W
S

E
n
g
i
n
e

T
W
S

M
a
s
t
e
r

Production
Plan
Plan API
T
W
S

E
n
g
i
n
e

T
W
S

B
a
c
k
u
p


M
a
s
t
e
r

Production
Plan
Plan API
Bobcat
Model/Planning EAR
Plan Mgmt EAR
T
W
S

E
n
g
i
n
e

T
W
S

D
o
m

M
g
r

Production
Plan
Plan API
Bobcat
Plan Mgmt EAR
T
W
S

E
n
g
i
n
e

T
W
S

F
T
A

Production
Plan
Plan API
Bobcat
Plan Mgmt EAR
Bobcat
Model/Planning EAR
Plan Mgmt EAR
Scheduling
Model
DB2
RMI / IIOP
RMI,
or HTTP
TCP/IP
TCP/IP
TCP/IP
TCP/IP
JDBC
TWS 8.3 Architecture
New infrastructure base
IBM Software Group
7
Creating engines using the Job Scheduling Console

It is now possible to create engines at
any time from within the Job Scheduling
Console.
IBM Software Group
8
New Features of the JS Editor – New Explorer View
 New Explorer View is now available for job stream and job stream instances.
IBM Software Group
9
New Features of the JS Editor - Add Job definition “on the fly”
 New job definitions can be added “on the fly”, and a quick option is also
available for adding multiple jobs with one click
The “New” button allows
creating a new job
definition “on the fly”.
The “Edit” button allows
editing an existing job
definition.
IBM Software Group
10
Job Stream Versioning
 Multiple versions of the same job
stream can be defined at the same
time: each one has a user-defined
Valid From date and a calculated
Valid To date.
 At any time only one version is valid
 Different versions share Name,
Workstation and lock status fields.
 When defining external
dependencies, no target version is
selected: versions of referenced
instances are resolved according to
their scheduled time.
IBM Software Group
11
Defining Draft Job Streams
 Job Streams can be temporarily
(without limitation) marked as Draft
and ignored by the planning
process until their definition is
complete.
 Any job stream can be moved from
/ to the Draft state at any time:
when running the planning process,
draft job streams defined at that
time are ignored.
 Draft job streams are excluded
from the chain of valid job stream
versions: i.e., their Valid To date is
left undefined and they don’t fit in
any point of the timeline.
 It is not possible to define multiple
versions for the same job stream
with the same valid from despite if
they are draft or not
Select “Is Draft” if you want the
definition being stored into database but
not used into Production Plan.
IBM Software Group
12
Job Stream Versions and Draft
“Valid from”, “Valid to” and “I s Draft”
information when querying the database.
IBM Software Group
13
Job Stream Dependency Resolution
 Job Stream Dependency
Resolution
Dependencies can now link job stream
instances in different days and different
plans
During planning and submission the
referenced instance is selected follows
the Dependency Resolution criteria
IBM Software Group
14
Assigning Run Cycles to JobStreams
 JSC panels for
creating/modifying Run Cycles
have been completely revised.
There’s only one flow for
creating run cycles; the
definition of the run cycle is part
of this flow.
 Selecting the requested type,
the panel is filled with
appropriate controls to enter the
required information.
 More than one Run Cycle can
be assigned to a single
JobStream
 The combination of Run Cycle
specifications will determine
when the JobStream will run
IBM Software Group
15
Assigning Time Restrictions to JobStreams
 Time restrictions can be defined
at the Run Cycle level, and are
used for job stream instances
generated by that run cycle.
 Time restrictions can be also
defined at the job stream level,
to be used both for Run Cycles
that don’t define their own
settings or when submitting
schedules ad-hoc.
IBM Software Group
16
Launch TDWC
®

© 2006 IBM Corporation
JSC Troubleshooting steps
®

© 2006 IBM Corporation
JSC Troubleshooting steps:
Determine product version & FP level
IBM Software Group
19
“About Job Scheduling Console”
®

© 2006 IBM Corporation
JSC Troubleshooting steps:
setting traces
IBM Software Group
21
Setting traces
Trace levels are defined into the file
 <user_home>/.twsconsole/logging.properties

The file is copied to the user home directory, .twsconsole subdirectory,
the first time user logs in to the Job Scheduling Console.

If you want to refresh the file contents, you can rename or move the
existing logging.properties file so that the Job Scheduling Console
creates a new one when you next log in
IBM Software Group
22
Logging properties keys
com.tivoli.logging Enables and disables the tracing function. Possible values are true and false. The default
value is false
com.tivoli.level Sets the error level to be recorded in the log file. Possible values are as follows:
OFF No data is traced.
INFO Informational messages are traced.
WARNING Warning information is traced.
ERROR Error information is traced. (default value)
FATAL Information on fatal errors is traced.
ALL All of the above data is traced.
All tracing levels, excluding OFF, also include the data recorded by lower tracing levels.
handler.file.fileName Specifies the name for the log file. The file is created in .xml format.
handler.file.fileDir Specifies the path where the log file is created. When you first log in to the Job Scheduling
Console, the default value for the log file directory is changed to
user_home_directory/.twsconsole/userdata. This procedure prevents the information in the log
file being overwritten when another user logs in to the Job Scheduling Console.
handler.file.maxFiles Specifies the maximum number of log files that can be created. The default value is 3.
handler.file.maxFileSize Specifies the maximum size of the log files. The default value is 3072. If this value is
exceeded, a new file is created. If the maximum number of log files is exceeded, the log files
are overwritten in the order they were created.
handler.file.appending Specifies whether the new information is appended in the log file, or if a new file is created.
Possible values are true and false. The default value is false.
®

© 2006 IBM Corporation
JSC Troubleshooting steps:
Setting ORB Traces
IBM Software Group
24
ORB Traces
 An Object Request Broker (ORB) manages the interaction between
clients and servers, using the Internet InterORB Protocol (IIOP). It
enables clients to make requests and receive responses from servers
in a network-distributed environment .

 When a connection problem between the JSC and Application Server
occurs, it could be useful to enable traces enabled on client side.
IBM Software Group
25
Enabling ORB traces 1/2
DCF 1282039 explains how enable ORB trace:

Client side:

1. Go to <JSC_Installation_directory>\bin\java directory
2. Make a backup copy of NTconsole.bat file
3. Modify NTconsole.bat file adding the following variables definition in the next-to-last line. The line
which starts with "start "JSC"...."

-Dcom.ibm.CORBA.Debug=true -Dcom.ibm.CORBA.CommTrace=true

Modified line should appear similar to the following:

start "JSC" "%JAVAPATH%/bin/javaw"
- Dcom.ibm.ssl.keyStore="%KEYSDIR%\JSCDefaultKeyFile.jks"
-Dcom.ibm.ssl.trustStore="%KEYSDIR%\JSCDefaultTrustFile.jks"
-Dcom.ibm.CORBA.ConfigURL=%CORBA_CONFIG%
-Dice.pilots.html4.defaultEncoding=UTF8
-Djava.security.auth.login.config="%CONFIGSECURITY%"/wsjaas_client.conf
-Dinstall.root="%TMEJHOME%"
-Dinstall.dir="%TMEJHOME%" -Dconfig.dir="%CONFIGDIR%"
-Dcom.ibm.CORBA.Debug=true -Dcom.ibm.CORBA.CommTrace=true
-DJSCPATH="%JSCPATH%" -Dcom.ibm.CORBA.Debug.Output="%TEMP%/JSCOrb.trc"
-Xms30m com.tivoli.jsc.launcher.JSGUIMain
IBM Software Group
26
Enabling ORB traces 2/2
Server side:
1. Make a backup copy of server.xml contained the following directory:
<TWShome>/appserver/profiles/twsprofile/config/cells/DefaultNode/nodes/DefaultNode/servers/server1
2. Modify, in the server.xml change the line:
startupTraceSpecification="*=info"
with this new one:
startupTraceSpecification="ORBRas=all=enabled“

Modify the third last line in server.xml file (the line starts with "jvmEntries xmi" characters) by
adding ORB traces specifications:
-D com.ibm.CORBA.Debug.Output=${SERVER_LOG_ROOT}/JSCOrb.trc -Dcom.ibm.CORBA.Debug=true
-Dcom.ibm.CORBA.CommTrace=true


IBM Software Group
27
Producing ORB traces

1. Restart WAS and JSC.

2. Replicate the error and collect from the client
machine the JSCOrb.trc file from the %TEMP%
directory.

®

© 2006 IBM Corporation
JSC Troubleshooting steps:
Logging
IBM Software Group
29
Where to find logs
 Installation logs
File twsconsole_ismp.log is stored into :
 the %TEMP% directory for Windows systems
 <home_dir>/tmp for Unix platforms
 General purpose logs
If traces have been enabled, file TWSConsole.log file can be found under
 Directory specified on logging.properties file, handler.file.fileDir key.
In the same directory you can find also JSC_err.log, JSC_out.log. They are
used to redirect stderr and stdout.

IBM Software Group
30
Q&A