mrc Documentation
michaels, ross & cole, ltd.
http://www.mrc-productivity.com/

Converting Web/Servlet Applications to Web 2.0

So you have been doing some research and testing of the Web 2.0 templates lately and you like what you see? We certainly can’t blame you – the Web 2.0 templates are streamlined to improve performance and simplify development. But what about all those applications you have already made with our Classic Templates? Surely you have spent many hours perfecting the look, and do not want to start from scratch.

Luckily, mrc has thought of that. Now with one simple click, you can convert your classic templates to the enhanced Web 2.0 without missing a beat & without losing any of your hard work!

Let’s walk through a tutorial:

Find an application you want to convert over to Web 2.0 that you have been working on in the Classic Template. Click Application Defaults and change the template to a Web 2.0 template. Click Accept. Now click Build/Compile.

Notice that above you are brought to a new screen asking you to preserve or discard your previous work. If you choose Discard paintings in old skeleton a new HTML layer will be used and any previous work to your Painting will be overwritten.

However, if you choose Preserve paintings in old skeleton, a series of events will happen with your application behind the scenes, including:

-Your old html file is renamed to XXXXX.html_old (where XXXXX is your application name)

-Your application will compile normally using the Web 2.0 Technology.

-Your new html file is renamed to XXXXX.html_web20

-Your old html file is moved back to its original name (XXXXX.html).

-mrc then merges the new functionality of the new template into the old html layer, thus preserving all of the time and effort that went into Painting your application.

The end result to you is the ability to quickly and easily convert old applications to Web 2.0 without having to repaint the html layer each time.

Common Questions:

Does this process copy over my application property files?

- No, this process does not convert your application properties. However, if your application was built prior to the Fall of 2006, your application properties will be imbedded into your old html file. You can use m-Painter to easily specify any changes to your application properties based upon what you had entered.

- For applications made after Fall of 2006, please make a backup copy of your XXXXp.xml file (where X is your application number) if you would like to retain your application property specifications.

What impact will this have on my sign on security?

- Web 2.0 templates use the newer mrcSignOn.html and mrcSignOn.xml security files. More information regarding Web 2.0 security can be found here.

The conversion process usually works perfectly, but every once in a great while I notice that some things have not copied over perfectly. Why is this?

- The conversion process from Classic to Web 2.0 is reliant on what you have painted as a developer. While we have done our best to account for everything, there may be a few instances where you will need to slightly modify the newly converted application.

- Also, please be aware that any modifications made to remove columns will require you to go into m-Painter to remove them.

I am using the pagename parameter that was discussed on the user forum (http://forums.mrc-productivity.com/tool/post/mrcuser/vpost?id=1079365) and I was curious whether or not this conversion process took the pagename into account?

- Great question, indeed we do account for this. Here is how you can accomplish the conversion (Note: this is applicable only for applications using the pagename parameter):

1. Lets assume you have an old skeleton titles I00010shd.html

2. Compile the application as Web 2.0

3. Rename I00010s.html to I00010s.html-web20

4. Call MRC902 through the URL line

http://XXYourWebServerXX/webapp/mrc/servlet/MRCPS.MRC902

5. Enter the Web 2.0 skeleton and old skeleton in the form and press Enter. The old skeleton will be updated to use within the Web 2.0 servlet.

Do you have other questions that weren’t answered here? If so, we’d love to hear from you. You can reach our helpdesk line at 630.916.0662