JSC8.3

5/21/2018 JSC8.3

1/30

2006 IBM Corporation

Job Scheduling Console 8.3 & 8.4

Giulia GiannitrapaniIBM Tivoli Customer Support - TWS L2 Support Engineer

5/21/2018 JSC8.3

2/30

IBM Software Group

2

Contents

Job Scheduling Console 8.3 & 8.4Whats new

JSC Troubleshooting steps JSC - Determine product version & FP level JSCsetting traces JSCSetting ORB Traces JSCLogging

Q&A

5/21/2018 JSC8.3

3/30


Job Scheduling ConsoleWhats new

5/21/2018 JSC8.3

4/30

IBM Software Group

4

New FeaturesNew 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 ConsoleIt is now possible to create engines at any time from within the Job Scheduling Console.

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

Job stream versioningSeveral instances of the same job stream might be present in a single plan.

Defining draft job streamsIt 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 StreamsFor distributed engines there are improved windows for defining and using run cycles.

Launch TDWC (JSC 8.4 only)

5/21/2018 JSC8.3

5/30

IBM Software Group

5

Old infrastructure base

JavaBased

UIJCF

CORBA

TWSEngine

TWSMaster

Connector

Scheduling

Model

ProductionPlan

Model API Plan API

TMF ManagedNode

TWSEngine

TWSDomMgr

Connector

ProductionPlan

Plan API

TMFManagedNode

TWSEngine

TWSFTA Connector

ProductionPlan

Plan APITWSEng

ine

TWSFTA Connector

ProductionPlan

Plan API

TMFManaged

Node

TWSEngine

TWSBackupMas

ter

Connector

Scheduling

Model

ProductionPlan

Model API Plan API

TMF ManagedNode

TWS 8.2 Arch itectur e

5/21/2018 JSC8.3

6/30

IBM Software Group

6

JavaBased

UI RMIStubs

RMI / IIOP

TWSEngine

TWSFTA

ProductionPlan

Plan API

TWSEngine

TWSMaster

ProductionPlan

Plan API

TWSEngine

T

WSBackup

Master

Production

Plan

Plan API

Bobcat

Model/Planning EAR

Plan Mgmt EAR

TWSEngine

TWSDomMgr

ProductionPlan

Plan API

Bobcat

Plan Mgmt EAR

TWSEngine

TWSFTA

ProductionPlan

Plan API

Bobcat

Plan Mgmt EAR

BobcatModel/Planning EAR

Plan Mgmt EAR

SchedulingModel

DB2

RMI / IIOP

RMI,or HTTP

TCP/IP

TCP/IP

TCP/IP

TCP/IP

JDBC

TWS 8.3 Architecture

New infrastructure base

5/21/2018 JSC8.3

7/30

IBM Software Group

7

Creating engines using the Job Scheduling Console

It is now possible to create engines atany time from within the Job Scheduling

Console.

5/21/2018 JSC8.3

8/30

IBM Software Group

8

New Features of the JS EditorNew Explorer View

New Explorer View is now available for job stream and job stream instances.

5/21/2018 JSC8.3

9/30

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 alsoavailable for adding multiple jobs with one click

The New button allowscreating a new jobdefinition on the fly.

The Edit button allowsediting an existing jobdefinition.

5/21/2018 JSC8.3

10/30

IBM Software Group

10

Job Stream Versioning

Multiple versions of the same jobstream can be defined at the sametime: each one has a user-definedValid From date and a calculatedValid To date.

At any time only one version is valid

Different versions share Name,Workstat ionand lock status fields.

When defining externaldependencies, no target version isselected: versions of referenced

instances are resolved according totheir scheduled time.

5/21/2018 JSC8.3

11/30

IBM Software Group

11

Defining Draft Job Streams Job Streams can be temporarily

(without limitation) marked as Draft

and ignored by the planningprocess until their definition iscomplete.

Any job stream can be moved from/ to the Draft state at any time:when running the planning process,

draft job streams defined at thattime are ignored.

Draft job streams are excludedfrom the chain of valid job streamversions: i.e., their Valid To date isleft undefined and they dont fit in

any point of the timeline. It is not possible to define multiple

versions for the same job streamwith the same valid from despite ifthey are draft or not

Select Is Draft if you want thedefinition being stored into database butnot used into Production Plan.

5/21/2018 JSC8.3

12/30

IBM Software Group

12

Job Stream Versions and Draft

Valid f rom, Valid to and I s Draftinformation when querying the database.

5/21/2018 JSC8.3

13/30

IBM Software Group

13

Job Stream Dependency Resolution

Job Stream DependencyResolution

Dependencies can now link job streaminstances in different days and differentplans

During planning and submission the

referenced instance is selected followsthe Dependency Resolut ion cri ter ia

5/21/2018 JSC8.3

14/30

IBM Software Group

14

Assigning Run Cycles to JobStreams

JSC panels forcreating/modifying Run Cycleshave been completely revised.Theres only one flow forcreating run cycles; thedefinition of the run cycle is partof this flow.

Selecting the requested type,the panel is filled withappropriate controls to enter therequired information.

More than one Run Cycle canbe assigned to a singleJobStream

The combination of Run Cyclespecifications will determinewhen the JobStream will run

5/21/2018 JSC8.3

15/30

IBM Software Group

15

Assigning Time Restrictions to JobStreams

Time restrictions can be definedat the Run Cycle level, and areused for job stream instancesgenerated by that run cycle.

Time restrictions can be alsodefined at the job stream level,to be used both for Run Cyclesthat dont define their own

settings or when submittingschedules ad-hoc.

5/21/2018 JSC8.3

16/30

IBM Software Group

16

Launch TDWC

5/21/2018 JSC8.3

17/30


JSC Troubleshooting steps

5/21/2018 JSC8.3

18/30


JSC Troubleshooting steps:

Determine product version & FP level

5/21/2018 JSC8.3

19/30

IBM Software Group

19

About Job Scheduling Console

5/21/2018 JSC8.3

20/30



setting traces

5/21/2018 JSC8.3

21/30

IBM Software Group

21

Setting traces

Trace levels are defined into the file /.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 theexisting logging.properties file so that the Job Scheduling Consolecreates a new one when you next log in

5/21/2018 JSC8.3

22/30

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.ALLAll 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 SchedulingConsole, the default value for the log file directory is changed touser_home_directory/.twsconsole/userdata. This procedure prevents the information in the logfile 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 isexceeded, a new file is created. If the maximum number of log files is exceeded, the log filesare 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.

5/21/2018 JSC8.3

23/30



Setting ORB Traces

5/21/2018 JSC8.3

24/30

IBM Software Group

24

ORB Traces

An Object Request Broker (ORB) manages the interaction betweenclients and servers, using the Internet InterORB Protocol (IIOP). Itenables clients to make requests and receive responses from serversin a network-distributed environment .

When a connection problem between the JSC and Application Serveroccurs, it could be useful to enable traces enabled on client side.

5/21/2018 JSC8.3

25/30

IBM Software Group

25

Enabling ORB traces 1/2DCF 1282039 explains how enable ORB trace:

Client side:

1. Go to \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 linewhich 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

5/21/2018 JSC8.3

26/30

IBM Software Group

26

Enabling ORB traces 2/2Server side:

1. Make a backup copy of server.xmlcontained the following directory:

/appserver/profiles/twsprofile/config/cells/DefaultNode/nodes/DefaultNode/servers/server1

2. Modify, in the server.xmlchange 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) byadding ORB traces specifications:

-D com.ibm.CORBA.Debug.Output=${SERVER_LOG_ROOT}/JSCOrb.trc -Dcom.ibm.CORBA.Debug=true

-Dcom.ibm.CORBA.CommTrace=true

5/21/2018 JSC8.3

27/30

IBM Software Group

27

Producing ORB traces

1. Restart WAS and JSC.

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

5/21/2018 JSC8.3

28/30



Logging

IBM S ft G

5/21/2018 JSC8.3

29/30

IBM Software Group

29

Where to find logs

Installation logsFile twsconsole_ismp.log is stored into :

the %TEMP% directory for Windows systems

/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 areused to redirect stderr and stdout.

IBM S ft G

5/21/2018 JSC8.3

30/30

IBM Software Group

30

Q&A

Documents

JSC8.3