Hi. I am running Debian 6.04 (wheezy), just installed Weblogic Server 12c correctly in its default folder. After putting a simple hello world Classic ASP file under /autodeploy it simply doesn't want to execute

The server is correctly running as http://localhost:7001/console, it runs good as much as http://localhost:7001/index.asp

But it simply doesn't execute the ASP file, it just list the contents of the ASP instead, it dumps it. I tried with a .js file with a simple document.write ('hello world'); to turn out doing the same

What I am doing wrong?

Thanks
Diego

Weblogic is a Java J2EE applet server. So you need to compile Java code and jsp pages to work with it. What this means to you is that you can't run ASP pages in Weblogic natively. There is a company which provides a solution to convert .NET applications into Java byte code to be run in applet servers like Weblogic. But that's about the best you'll get, and even that doesn't make much sense unless you're working with an established application which is old and complicated.

As an analogy you're asking, "Why doesn't perl interpret my python code?" Well because it's a perl interpreter and not a python interpreter.

Thanks for your reply, but if I have to run a process/translate the ASP/.jsp files into something that Weblogic may understand makes no sense at all, to say the least

Instead of doing it I can keep an FTP client opened, transfer my source after every change into a paid hosting and run it from there through the browser. What would be the difference? I tried avoiding doing it in the aim it would have been supported natively by Weblogic as they claim to do in the product description, but if I had to add an extra step I would rather add an extra step that, well, sounds of any logic to me other than doing things based on the decision and whims of a third-party tecnology creator. I respect myself too much as a programmer to do this

What's the meaning of having to re-compile in order to "fit" the desires of weblogic ? I have enough with Linux illogical issues everyday and its illogical folder hierarchy layout to go another step doing things even more illogical. Well, sounds illogic to me that you don't even know where programs get installed on a quick look .It could be on /usr/local, it could be on /usr/local/share, usr/bin, usr/local/bin/

Senseless at every inch

Thanks for your reply, my complains doesn't goes against your kindness replying my question. Thanks

As far as the install hierarchy goes it's not illogical. Each distro simply defines it's own standards for how they want applications installed and handled. Sticking to one distro may keep you a little sane but those standards change as you migrate to other versions of Linux. This is not abnormal because not every developer has the same view as to how a GNU/Linux distro should be.

Take for instance this documentation in debian for maintainer standards.

Look at /usr/bin vs /usr/local/bin in RedHat and in Linux From Scratch. It's generally accepted that /usr is updated by OS package managers (PMs) but the PMs don't touch /usr/local which is where the user can compile and run their own system specific software.

As I said the it depends on what distro you're using and if you try to look at all distros as following "one standard" then that would be a mistake because they each outline their individual standards clearly for the most part (the major ones anyway).

Trust me, I understand your frustration with Linux because it's information overload and a lot to comprehend as a system maintainer. But it simply means the ways of doing things are different compared to other operating systems you're used to. It's not "like Windows" in any way but its own animal. Hence for the need to retrain your own thought process when working on it.

--- Back on Topic ---

Back to your original question, this article (section JSP versus ASP) may help clarify my earlier point. I agree with you that using that third party "convert/cross compiling" software would be a mistake.

Would you kindly provide the product description page which you are referring to about WebLogic being able to run ASP? In my experience getting Microsoft technologies to work on anything but Microsoft is a burden in and of itself. It's not a Linux problem but more of a corporate decision in a product and not something which GNU/Linux/Unix/Solaris/BSD/Mac/XYZ OS software can be blamed for.

SAM

Sure, please check http://markalexanderbain.suite101.co...-server-a68959, read first paragraph about ASP
I read it in other pages as well

I had enough of Linux though, I had to delete partition just now. In a last attemtp I tried to install Apache, mod_perl and all the jumping monkeys and still got an incomplete installation. Then you ask WHY running apt-get install apache2 may install an incomplete package? If I install an .exe on Windows I get it installed all at once, I don't care if it crashes or not, it INSTALLS complete at least. It was not the case with Apache, mod_perl was asking for a missing .h header file to find out later that apache2.2-common wasn't installed. Then you ask yourself: HOW COME installing something from a reliable source gets partially installed with 'missing parts' that you have to manually download later?

Maybe situations like these are funny for the typical Linux user, but I am a business man too not only a programmer and I need solutions. I wasted 3 hours yesterday JUST to LOCATE that the weblogic folder that stores your files/scripts is not /applications but /autodeploy .I read countless forums , even official techs saying that /applications where the place to go, to find out it was WRONG . 3 hours, do you have an idea all the things I can do in 3 hours ?

Well I wasted nearly 5 hours only yesterday, to come up here today and read from you 'hey buddy, Weblogic doesn't run ASP natively. To do so you need to do a,b,c,d,e,f,g..Z

I simply had enough, totally fed up after hours sitting in front of a root terminal trying senseless commands, trial-and-error attempts to hit the ground. Fed up

Thanks for all your help, time and kindness replying here

If this is your first time (or nearly first) at attempting to configure servers in a Linux environment and performing sysadmin functions then expect it to take a lot of time. There is a very large learning curve of reading documentation and man pages to do it properly. It can be daunting but I feel if you stick with it attempting to learn the thought process and how Unix tools are designed to work with one another that you'll be satisfied with the end result.

From your woes of apache2 package you need the developer package which contains the source code. In Debian this is called apache2-dev. After that your mod_perl should install and build just fine. It needed the header files so that it could compile against your version of apache. So a take away is that it did install a complete and working apache, you just needed the source code for something extra. As far as your take on what an operating system should be perhaps you should look at open source software in a different manner. You're used to paying for your software and when you demand support you get it. Being used to a system like that people tend to expect that type of service with everything they're running. This system is turned upside down when you apply the concepts of open source software. You don't always get the guarantee of support, people answer when... they answer and the software is largely developed by volunteers freely or organizations backing the developers (not the users). So in essence, you can't guarantee support if you didn't pay for it and the same can be said when you're attempting to get support for open source software. I read a really good article somewhere that explains that better than I can but I can't find it and did my best attempt. In summary it basically compared toy cars and legos (building toy cars) in a really good analogy. Anyway...

*EDIT --
I found the article: http://linux.oneandoneis2.org/LNW.htm
It's a fun read.
*END OF EDIT --

I do not recommend you trying to run anything business related on an unsupported server unless you truly know what you're doing. If you don't understand the security of the platform nor how to configure it properly then it's like running with no security (not referring to you directly but the royal "you"). RedHat would be the brand I recommend because they have a support guarantee. It's a rock solid server for high availability operations with the backing of RedHat. Their support cycle is 7 years long on a single release. I manage hundreds of RedHat servers and enjoy them.

--- Back on Topic ---

That article you referenced is for Sun Java Web Server 7.0 which is not WebLogic. According to these release notes, Sun Java Web Server is now called Oracle iPlanet Web Server. According to this FAQ Oracle iPlanet Server 7 still supports everything the old Sun Java Web Server 7.0 did and more (see references to support for Active Server Pages 3.0). It's best to look up official documentation to verify the claims of a third party website.

So I learned something new today that ASP can be run on Linux . Try using that iPlanet Web Server instead of WebLogic and let me know. Also, can you give me the ASP page which you are trying to test? I'm interested to experiment with this myself and don't write ASP.