jobscheduler.com

In the forthcoming Flux 7.10, when you’re monitoring your jobs in the Operations Console, you can click on a particular job for detailed info:

This dialog shows timing info:

• when the job started
• elapsed time
• the average time taken by previous runs of this job, which acts as the projected amount of time the current job will run
• time left until the deadline
• deadline

The job scheduler engines in a cluster are shown at the top of the Flux 7.10 Operations Console. Clicking on any of those engines displays detailed information in a popup dialog. The mockup of that dialog is done:

In this sample engine status dialog, the engine is located on the host spur2.appgenics.com. The CPU of that host is 49% busy. The memory used is 65% of the total available memory.

The mockup for the Agent status dialog is done. This dialog shows the status of a process that ran on an agent. Status information like the script that ran, the elapsed time, standard output, and standard error are included. On the Current Command tab, this same information is shown for the currently executing command on that agent.

We’re close to finishing the static mockup of the front page of the new Flux Operations Console.

Here are two color variations on the same mockup for the new Flux Operations Console.

Check out the engines and agents status bars near the top. They give a succinct, attractive view of the health of the cluster.

The brown “suede” theme and the blue theme will be available for use in the Operations Console. You’ll be able to select a theme or upload your own.

Which theme should we use as the default? Suede or blue? Leave a comment!

A new implementation of the Flux Operations Console is in development for Flux 7.10. The Operations Console is a web application for IT operations staff to monitor, view, control, and edit jobs, workflows, and file transfers.

The simple wireframe below shows a rough preview.

Overall, the new Operations Console provides the most important information about a running Flux cluster on the homepage in a dashboard layout, with updates displayed in the browser in real time.

The status of Flux engines and agents are shown in a compacted view at the top. This view lets you see engine and agent health at a glance without taking up too much screen real estate. To control engines and agents or to view details, a popup window appears on a mouse click.

The list of jobs is shown below the engine and agent status bars and uses most of the browser window. Each row shows:

• the job name
• the predicted time for when the current job run will finish
• if the job run is taking longer than predicted, the amount of “overtime”
• the action (task) that is executing for that job. Due to splits, sometimes there are a multiple actions running simultaneously per job.
• the job status (firing, waiting, triggering, etc)
• the engine where the job is running
• the last message generated by the job

If the job is uploading or downloading a file, the File Transfer Monitor displays the usual file transfer statistics and progress bar, including the source host, destination host, and file transfer protocol used.

Two Fluxies were onsite at customer locations last week. IT people, not Java developers, were ramping up to use Flux to run jobs like calling database stored procedures, calling REST services, invoking SSH commands (the agentless architecture approach), running Windows executables, and running Unix shell scripts.

Very cool.

When loading freight onto its trucks, Con-way uses its Step Saver optimization software to determine optimal placement of trucks at its docks at Con-way’s freight assembly centers. If an incoming truck parks at the right dock at one of these assembly centers, then forklifts don’t drive as far to transfer freight. Trucks are loaded faster. Forklift fuel, tire tread, and maintenance is saved.

Flux is one of several parts of Con-way’s Step Saver application. Con-way says they save $3 million USD per year by using Step Saver, plus 44 minutes per shift formerly spent on planning duties, plus the savings on fuel, tires, and maintenance on the forklifts.

From the Network World article:

To get the job done, Step Saver leverages an array of development tools, including Java, CA Gen, IBM WebSphere Information Integrator Replication Edition V8.2, Tibco Application Integration Suite, Flux Java Job Scheduling, C++, and iText.

In Flux 7.10 (in beta – just ask support@fluxcorp.com for a copy), the job/workflow layout appearance data is now embedded directly in job/workflow XML files. This means you don’t need those extra layout files anymore. The graphical way in which you draw your jobs and workflows is saved within the job/workflow XML file itself.

The big benefit is that within the Flux Operations Console, jobs and workflows retrieved from a Flux engine will be laid out in their original form, not using an automatic layout algorithm.

The other benefit is that it’s simpler as there’s one less file to manage.

A company (not us) in South Portland, Maine is looking for a Flux Developer. Job details below from Gena Shelton, the recruiter looking to fill the position.

<begin message from Gena Shelton, the recruiter filling this position>

I am currently looking for a Flux Developer for a high profile client. Would anyone you know be interested in applying for the job listed below?

Location : South Portland, ME
Duration : 6 Months Contract to hire
Pay Rate : Open

Please send me an updated WORD Copy of your resume if you are interested.

Job Requirements

• Extensive experience with Flux to perform job scheduling, workflow, and file transfer functions.
• Strong knowledge of Web-based monitoring application like complete Java API for IT staff to oversee jobs, workflows and file transfers.
• Knowledge of user friendly graphical tools for designing jobs and workflows.
• Knowledge of “Control M” would be useful.

Thanks,

Gena Shelton
Senior Technical Recruiter
Global Technical Talent
Direct: 603-319-4910
Email: gshelton@gttit.com
www.gttit.com