• The Four Hundred
  • Subscribe
  • Media Kit
  • Contributors
  • About Us
  • Contact
Menu
  • The Four Hundred
  • Subscribe
  • Media Kit
  • Contributors
  • About Us
  • Contact
  • AppWorx Brings Job Scheduler to OS/400

    May 24, 2005 Alex Woodie

    iSeries shops looking for a new cross-platform job scheduler gained a new option this month when AppWorx introduced an OS/400 agent with AppWorx version 6.1. The Java-based job scheduler has long been used in Oracle ERP environments, and now iSeries shops can utilize the AppWorx functions, including job launching, status tracking, and even capturing output.

    AppWorks is a Bellevue, Washington, company that started life as ISA Corp. in 1990. The company expanded from its initial focus on Oracle applications running on Windows and Unix platforms to include other operating systems and applications, including J.D. Edwards EnterpriseOne, Lawson‘s ERP software, PeopleSoft Enterprise, Retek Retail, SAP‘s R/3 and mySAP, Siebel‘s CRM software, and SunGard‘s SCT software for governments. Today the company supports Windows, Unix, Linux, OpenVMS, and OS/400.

    “We developed the OS/400 agent in response to requests by customers and potential customers, mostly in the J.D. Edwards, Retek Retail, and European markets,” writes Tim Kramer, the company’s marketing director. “We wanted to round out our offering and the OS/400 agent is a significant step towards accomplishing that.”

    AppWorx separates itself from other batch job schedulers on the market by eschewing the traditional script-based control in favor of an object-oriented design that sits above the applications, which makes it “application aware” and capable of reacting to error codes, the company claims. Using an object-based architecture also enables changes to be more easily cascaded down to all the systems, which saves time and reduces errors, the company says.

    AppWorx says it can automate any batch environment, no matter how complex the workflow or interdependencies of various enterprise systems. The software handles the task of passing any dynamic or static parameters to each job, and enables users to set up processes to execute using “before,” “during,” and “after” conditional logic. Jobs can be linked to run as soon as the output is available from a previous job, or jobs can be scheduled to execute at a certain time. Queuing enables jobs with the highest priority to be run first, while the ad-hoc setting lets power users run reports as needed.

    In addition to being a batch job scheduler, AppWorx also provides output management that routes the results of certain jobs to the appropriate file or output device. This feature is handy for automatically kicking off reports, and with its CPU throttling capability, users can be assured that large reports won’t bog a server down.

    Users interact with AppWorx through a graphical interface that enables them to set up batch scheduling by dragging and dropping elements on a screen. Users can also choose from various graphical analytical packages to view things like expected run times of a job chain or a job stream, the current job backlog, historical data, and a 24-hour preview of the schedule. Apparently, it’s similar to using Excel to control your business process flow, as the company claims that “AppWorx is the spreadsheet for your application batch processing environment.”

    The company is allowed to boast–a little. In Gartner‘s last Magic Quadrant on job schedulers, AppWorx was featured as the “most visionary.” The company has 500 customers, a drop in the bucket compared to the big boys of systems management–IBM Tivoli, BMC Patrol, Hewlett-Packard‘s OpenView, and Computer Associates‘ Unicenter.


    The vendor has developed extensions to enable AppWorx to work with various enterprise applications. The software will also work with native job schedulers provided by several ERP vendors, such as SAP.

    In addition to OS/400 support, AppWorx 6.1 offers improved SAP integration through a new Java interface that’s certified by SAP for its eXternal Interface for Job Background Processing (XBP2.0). This release also brings support for JDBC drivers, enabling AppWorx to take account of things like dynamic parameters and database triggers in setting up its schedule.

    AppWorx 6.1 with the OS/400 agent is available now. Pricing is tier-based and starts at $18,000. For more information, visit www.appworx.

    Share this:

    • Reddit
    • Facebook
    • LinkedIn
    • Twitter
    • Email

    Tags:

    Sponsored by
    ARCAD Software

    [Podcast] IBM i DevOps Techtalk : 3-Part Series on Key Git Topics

    Listen in to these 3 short episodes as our experts Jeff Tickner, Ray Bernardi and Alan Ashley share their expertise on GIT, and discuss how best to use Git with the IBM i and its advantages.

    Moving To Git

    The topic of this IBM i DevOps TechTalk is “Moving to Git.”  It features Jeff Tickner, Ray Bernardi and Alan Ashley as they discuss what is Git and how to best use Git with the IBM i. Listen in for tips on:

    • Key Git Advantages
    • Git Considerations for a successful implementation
    • Working with branches and automated merges
    • Getting started and ARCAD’s Centralized approach

    Moving to Git – Gitflow

    Tune into this IBM i DevOps TechTalk on a key Git concept – Gitflow. Jeff Tickner, CTO NA, shares his knowledge and experiences from real-world implementations. Learn:

    • What is Gitflow and the benefits.
    • Bi-directional development with push/pulls and merging conflicts. Why you need this 2-way integration.
    • Flexible Gitflow options.
    • How ARCAD’s tooling elegantly supports Gitflow for the IBM i Developer

    Listen to this episode to get a jump on Git and partner with an expert on your DevOps journey.

    Moving to Git – The Build

    In this episode, we’ll discuss an important Git topic – The Build. If you are not using Git for IBM i source control, you are likely planning for it. A key part of the process you must understand is “The Build”.

    You may ask, why? Isn’t it just a standard IBM i build?

    No! Tune in as Jeff Tickner, CTO NA and Alan Ashley, Sr. Solutions Architect, discuss:

    • The differences between a standard IBM i build and a build with Git.
    • Understanding options and advantages with ARCAD versus Better Object Builder (Bob).
    • What are personal builds?
    • Advantages of automated builds with tools like Jenkins and Azure

    Partner with the leader as you make the DevOps journey to modern, agile IBM i development.

    Listen Now

    Share this:

    • Reddit
    • Facebook
    • LinkedIn
    • Twitter
    • Email

    Admin Alert: Configuring an i5/OS-based EIM Table for Single Sign-On Creating Pivot Tables on the iSeries

    Leave a Reply Cancel reply

Volume 5, Number 21 -- May 24, 2005
THIS ISSUE
SPONSORED BY:

Bytware
Aldon
iTera
Asymex
Affirmative Computer

Table of Contents

  • AppWorx Brings Job Scheduler to OS/400
  • Looksoftware Shakes Up Product Line
  • CCSS Boosts Problem Resolution in QMessage Monitor
  • WRQ Improves Security of Terminal Emulation Suite

Content archive

  • The Four Hundred
  • Four Hundred Stuff
  • Four Hundred Guru

Recent Posts

  • Rocket DevOps Now Supports VS Code
  • DR Testing As A Service: One More Thing That You Don’t Have To Do
  • The First Step In DevOps Is Not Tools, But Culture Change
  • As I See It: IT Come Home
  • IBM i PTF Guide, Volume 25, Number 39
  • ARCAD’s Deal with IBM for DevOps In Merlin Is Exclusive
  • In The IBM i Trenches With: Maxava
  • Is The Cloud On Your IBM i Horizon?
  • Four Hundred Monitor, September 20
  • IBM i PTF Guide, Volume 25, Number 38

Subscribe

To get news from IT Jungle sent to your inbox every week, subscribe to our newsletter.

Pages

  • About Us
  • Contact
  • Contributors
  • Four Hundred Monitor
  • IBM i PTF Guide
  • Media Kit
  • Subscribe

Search

Copyright © 2023 IT Jungle