E9.2 Using Orchestrator versus DB2 Stored Procedures to extract data from JDE

[Mumha]

Hi

The company I work for currently has E9.10 and is in the process of upgrading to E9.20.

An outside company created a web application to (currently) show orders/statuses etc for our customers. We've created DB2 stored procedures to extract the required data for that company to build into their web application. That works well, for what it provides.

As we are now moving to E9.20, we are looking to redesign this and not only outflow information, but also to take in everything from new item data to purchase orders to changing/deleting lines etc. For that, we have been looking at using Orchestrator, and not need to use Stored Procedures any longer.

My question is whether anyone else has been down this road, and what their experience is ? From the training we have received, we have been re-evaluating whether we can get rid of SPs after all. Maybe we should just use Orchestrator as the delivery vehicle, rather than the data extractor AND delivery vehicle. Also, on the inbound, I can see we could use standard BSFNs to do a lot of the work, but I'm wondering whether sending the data through the 47 tables would be a safer option ?

Thanks in advance.

 

[Harshal Sheth]

I see a big drive with orchestrator to move away from DB2 SPs / RPG /CLP etc.

The primary advantage of move will provide you with an online connectivity using REST api integration. This will make you future proof.

Bigger challenge is to find people with development skills on as400/DB2 platform.

You will remove a large technological dependency by moving to o
Orchestrâtions.

 

[Mumha]

I see a big drive with orchestrator to move away from DB2 SPs / RPG /CLP etc.

The primary advantage of move will provide you with an online connectivity using REST api integration. This will make you future proof.

Bigger challenge is to find people with development skills on as400/DB2 platform.

You will remove a large technological dependency by moving to o
Orchestrâtions.

Thanks for your reply, Harshal.

I actually started out on a System 36 back in the 80s, before moving on to the 38/400/iSeries although the last 20 years it's been platform independent as there's always been a CNC, so I haven't had as much interaction with the iSeries as I would have liked.

It's certainly exciting to see what Orchestrator can do.

We have done a week's training on Orchestrator, and it does appear so far that we will be swopping one programming language for another, which will then need to be maintained. However, certainly it is a big plus on the connectivity side.