Malik, <p>This is excellent artical. <BR>
I may need to contact you if need youe assistance. <p>Bharat Pandya

Malik, <p>This is excellent artical. <BR>
I may need to contact you if need your assistance. <p>Bharat Pandya

Do you have the same information using WDSC? <p>Dave

David, <p>I am afraid not. My expertise are Web Enablement of AS/400 through .Net. I tend to stay away from all Java products if I can help it. I find websphere sadistically inconvenient. <p>I wish I could help you. If you need some help with Web development using .Net, please all means do let me know. <p>Thanks <BR>
Malik

I have been reading about how easy the .NET framework is to use for web development. This is a great article on how to actually try it. Keep up the good work and let's see more articles.

Hi Malik, <p>Thanks for writing the article. It was an interesting read. <p>Please help me to understand the <i>architecture</i> of your application. I'm sure you're familiar with MVC. Obviously, the browser interface is the View. What are the Model and Controller? <p>Does the web user need direct *USE or *READ authority to the data? What if the user will be updating data? Does the user need direct *CHANGE or *WRITE authority in that case? If so, that's a breach of security. The user should not have direct use of the file and should use the Model. <p>How "easy" would it be to add another user interface to this application, something besides HTML? <p>Just as a point of reference, on the iSeries, one could use HTML or JSP as the View, a Java servlet as the Controller and a backend RPG program defined as a stored procedure using adopted authority as the Model. With the Model separated out, one could add other user interfaces as well. <p>Regards, <p>Chris

The web user actually does not even have to have a profile on the AS/400 at all. <BR>
Let me explain.. <p>Front end or the view as you call it is the ASPX page instead of JSP <BR>
Controller is XML Webservice to put it loosely instead of a Servlet <BR>
Model is an RPG program directly or used as an store procedure. <p>You are thinking in pure Java terms.. <p>Actually its pretty simple.. <p>ASPX page can interact directly with an RPG/cobol or C++ object on the AS/400 with or without a store procedure. The user authority is determine by the OLEDB provider which actually starts a job on the AS/400 under the user profile provided in connection string. Based on this user profile the jobdescription is determined and library lists determined and the object authority is checked. Its actually very similar to starting a interactive job on the AS/400. The authority is checked based on your user profile. ASPX page is using client access OLEDB drivers to make a call to AS/400 and starts a job in QSERVER subsystem and pass in a userid for that job. This became the basis of all your authority just like any other job on the AS/400. <p>The web user do not even have to have user profile on the AS/400 because, again, its the OLEDB driver and the user profile mentioned in the OLEDB driver that have to have a user profile on the AS/400. <p>This way anyone can use the web page regardless of his/her user profile exists on the AS/400 or not. That makes .Net a very flexible platform. <p>You can however restrict webpages to only authorized users in your domain by setting up IIS to allow only authunticated users. <p>The security of ASPX page or ASP.Net application is totally seperate from the secuirty of AS/400. One has nothing to do with the other. The OLEDB drivers detemines that part. The bridge is client Access OLEDB drivers.As far as AS/400 is concerned aspx page is no different than an odbc data transfer call from excel. AS/400 treat all aspx calls as regular client access calls. <p>As far as adding how easy it is to add another user interface? <BR>
How about just adding another page to the asp.net app and keep adding it. Its quite trivial. <p>The AS/400 secuirty is actually not comprised in any way. AS/400 does check who is making the call over tcp/ip and can elaborately accept or reject RPC through exit programs. The aspx page must make a RPC call with a valid user ID and password and that user id must have access to the objects it is trying to use. <p>Updating database works the same way, the remote procedure call(RPC) must be made from aspx page through client access OLEDB drivers pretty much similar to the way a 5250 session is started and a user id and password must be passed in. AS/400 will check the authority of the user profile comming in over TCP/IP and start a job in qserver and if the RPC is an update call then it updates the files. <p>To simplify the architecture of a ASP.Net application, allow me to use an AS/400 analagy.. ASPX page is nothing but a elaborate SDA. You define your menu and define which programs to call on what option. The difference is that your menu sits in Windows environment rather than AS/400. <p>Hope I answered your question. <p>Malik <BR> This e-mail address is being protected from spam bots, you need JavaScript enabled to view it

This is a discussion about <B>Convert AS/400 Data into XML</b>.<p align='center'><a href=http://www.mcpressonline.com/mc? This e-mail address is being protected from spam bots, you need JavaScript enabled to view it @.6aeb7f4b>Click here for the article</a>.</p>

<a href="/mc? This e-mail address is being protected from spam bots, you need JavaScript enabled to view it @.6b24d1dc">Tahir Malik "TechTip: Populate Files on the iSeries from Oracle or SQL Server" 5/17/05 7:12am</a> <p>hope all is well with you... <p>Rgds <BR>
Malik