What to do if you change the DDS display file source member after you WebFace an application[ Return to top of page ]
If you change the DDS display file source member AFTER you've WebFaced an application, Web development expert Jim Mason says you need to do the following:
- Reconvert only that specific DDS source file in your WebFacing application.
- Export your WebFacing application to a .war file again.
- Redeploy the .war file to your application server.
The communication between the WebFacing Java code and the host 5250 RPG application is based on the DATA BUFFERS for input and output for each record format. Any changes to the buffers in your DDS display file or their contents require you to reconvert that specific display file.
Alternatives to executing iSeries commands[ Return to top of page ]
Web development expert Jim Mason says WebFacing doesn't handle system user interface screens in the current release. That means commands such as WRKSPLF won't work in a WebFaced applications. You have several options to handle this situation:
- Spend money (maybe lots) to get a different IBM or third-party solution (iSeries Access for Web, HATS, etc.). -- Bad idea
- Upgrade to the Advanced edition of WDSC, which has a spool file viewer built in. –- OK, but costs real money to upgrade
- Buy or find a spool file to PDF utility to generate PDF files from spool files. -- Not a bad choice
- Create your RPG application to select, view spool files and WebFace that. A number of customers have already done this. -- Good choic.
- Create simple CL "wrapper" commands with input parms for your key system commands. Then use the Web interaction wizard in WDSC to Web-enable the CL commands. You CAN'T get results from WRKSPLF, BUT for other commands it's great. -- Great where it fits
WebFaced app that limits customers' view of data[ Return to top of page ]
Is it possible to place some of WebFaced applications on the Internet for use by customers and make it so each customer views only their information? Web development expert Jim Mason says yes, but it takes some programming.
Here's the basic model that his team followed:
- A customer logs in to a basic security Web application. (We have a simple Web security system.)
- During login, we record the user's customer name, account number as the current information in a session variable.
- When the WebFacing 5250 application starts, a CL program is passed the session variables as parms. The CL program runs an OPNQRYF using the customer number restricting orders to only those for this customer.
- We automatically populated the customer number field on the initial order inquiry screens by modifying the generated screens.