Scheduling jobs to run LOCAL

[donmiller]

We're developing a UBE that will serve as an interface to legacy system data (ISAM files). The UBE will identify changes in data that need to be interfaced and using an ODBC connection, will update the legacy files directly. We've used this approach to embed calls to ODBC to update data in real-time from interactive applications in JDE.

The restriction with this approach is that this UBE must run locally on a NT platform, the ODBC connection is not availbale from the UNIX Enterprise server. The requirements for this interface dictate that the UBE must run periodically (every 30 - 60 minutes) to update the legacy system throughout the day.

Is there a way to schedule a job in JDE to run LOCAL? I realize we could solve the problem with a NT application server by mapping the UBE to run on that server, but we would like to make use of one of our Citrix server to run this UBE instead. We don't want to have to put in an application server just to support this relatively short-term interface.

Is there a way to submit the UBE from the NT OS similar to the runube command from UNIX?

Any thoughts would be appreciated.

 

[cnc__guy]

There is a runube command for the NT OS also. Syntax is similar to that of
the UNIX command.

Check it out and see if this will meet your needs. Then you just have to
schedule the appropriate runube command to run when you want it to via the
NT Scheduler.

James
JDE CNC Consultant

 

[OWHell]

Try LaunchUBE

OW Hell

 

[SSAJAROFF92]

Don :

You've got three choices :

a) Use LaunchUBE.exe, a GUI program that allows you to launch UBE
locally but doesn't accept command line parameters. A piece of crap!
b) To write a C or VB program that calls JDE UBEs via APIs and submit
them locally from there. It sounds too difficult for such a simple task.
c) Look for a spare PC with 384 Mb RAM and 10 Gb disk and install
a minimal UBE Server there just to run JDE Services for your UBE.
(1 Queue will suffice). I think that this is the easiest way.

Sebastian Sajaroff (JDELIST)

 

[dhelsley]

Why bother with a UBE?

Use the ODBC connection to the Oracle (OneWorld) database to read the data you are tranferring to the the legacy system. Then use the ODBC connection you already use to update the legacy system.

With this approach you can write the job in VB, Access or another PC development language. The NT scheduler has no problem launching these.

The downside is that you'll need to transform any values that are not in a base form (stored without decimals or in a OneWorld format) such as dates. Since this is a short term interface there's not to much risk in hard coding these transformations.

 

[donmiller]

Thanks to all. The solution for us has turne dout to be 'printube'. This command accepts command line parameters for the UBE and version name as well as an option to display the output on scres=en vs. just saving the output to the local PrintQueue directory.

This works well for us since we wanted an option to run this interface on-demand as well as a scheduled job. The scheduling will be done with a script and an NT service.

Thanks