Download weblogic 8.1 documentation

After using google again I found a comment with someone mentioning using richfaces 3. Now I have seen many people say use version xxx even 3. After all I did get it working with 3. This is not optimal, but I geuss it works. Some taglibrary references needed changing, and packages changed to some extent. I could post my project configuration for this if anyone ever needs it. Getting this all to work on weblogic 8.

But the reference documentation for 3. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Richfaces 3. Asked 11 years, 11 months ago. Active 11 years, 5 months ago. Viewed times. Following are the jar files contained in my web-application.

I'd prefer not to make any at all, chances are those changes will be denied Oh this error occurs when attempting to view the page, so deployment is successful. Improve this question. Pascal Thivent k gold badges silver badges bronze badges. Install the JDK that you downloaded by following the vendor's instructions. Make a note of the installation location as you will need it when you configure WebLogic. Installing the Server To install the server: Start the WebLogic installation program in console mode.

Then double-click the icon representing the file. On Solaris systems, change directories to the directory that contains the BIN file that you downloaded. In the Welcome screen, click Next. Note: Normally, the default value works fine. However, if the default path contains one or more spaces, you must change it so that it does not contain any spaces. At this point, the WebLogic files will be copied to your disk.

When the copy is complete, the Installation Complete screen will appear. The directory separators used in this section are for Windows systems. If you are working on a UNIX system, replace each backslash with a slash. In the Configure the Administration Server screen, set the Name to myadminserver , set the Listen port to , and click Next. In the Configure Managed Servers screen, click Add. Then, set Name to myserver , set Listen port to , and click Next. In the Configure Clusters screen, click Next.

Then click Add. Click Next. Then click Next. In the Configure Administrative Username and Password screen, enter a user ID in the User name text field and a password in the User password and Confirm user password text fields. Select No for Advanced Security, i.

The Configuration Wizard creates your configuration. Set the common environment variables for WebLogic by editing the file commEnv. Then save the file. Start the administration server and the Node Manager. Right-click the icon for each service, and select Start from the pop-up menu.

Recommended: To configure the managed server for use with the Node Manager that is, to be able to start the managed server using the Administrative Console , go to the server's Configuration: Remote Start properties page, and set the properties listed below. To get to this page, expand the Servers folder in the tree structure on the left, and select myserver.

On the right side of the interface, select the Configuration tab if it is not already selected ; then, select the Remote Start subtab. For illustrative purposes, it is presumed that you have installed and deployed the stock quote demo. Note: Again, you may need to replace localhost with your host name, and with the port number used by your web server.

If you are experienced in web application development, and especially if you wish to add web services to an existing or complex webapp, you can take an alternate approach to running Axis.

Instead of adding your classes to the Axis webapp, you can add Axis to your application. Axis is a complicated system to install. This is because it depends on the underlying functionality of your app server, has a fairly complex configuration, and, like all distributed applications, depends upon the network too. We see a lot of people posting their problems on the axis-user mailing list, and other Axis users as well as the Axis developers do their best to help when they can.

But before you rush to post your own problems to the mailing list, a word of caution:. Axis is free. This means nobody gets paid to man the support lines. All the help you get from the community is voluntary and comes from the kindness of their hearts.

They may be other users, willing to help you get past the same hurdles they had to be helped over, or they may be the developers themselves. But it is all voluntary, so you may need to keep your expectations low! Has this put you off joining and participating in the Axis user mail list? We hope not--this list belongs to the people who use Axis and so will be your peers as your project proceeds.

We just need for you to be aware that it is not a 24x7 support line for people new to server side Java development, and that you will need to be somewhat self sufficient in this regard. It is not a silver bullet. However, knowing how to make effective use of the list will help you develop better with Axis.

Axis is simply an implementation of SOAP which can be added to your own webapp, and a webapp which can host your own web services. Installing it can be a bit fiddly, especially given Java 1. If you follow a methodical process, including testing along the way, using happyaxis and the bundled test services, you will find it easier to get started with Axis. The basic steps for enabling it are compiling the SOAP Monitor java applet, deploying the SOAP Monitor web service and adding request and response flow definitions for each monitored web service.

In more detail:. Copy all resulting class files i. Go to the directory deploy-monitor. Introduction This document describes how to install Apache Axis. For more details on using Axis, please see the user guide. Things you need to know before writing a Web Service: Core Java datatypes, classes and programming concepts. What threads are, race conditions, thread safety and sychronization. What a classloader is, what hierarchical classloaders are, and the common causes of a "ClassNotFoundException".

How to diagnose trouble from exception traces, what a NullPointerException NPE and other common exceptions are, and how to fix them. What a web application is; what a servlet is, where classes, libraries and data go in a web application.

How to start your application server and deploy a web application on it. What HTTP is. The core protocol and error codes, HTTP headers and perhaps the details of basic authentication. What XML is. Not necessarily how to parse it or anything, just what constitutes well-formed and valid XML. Before you can do that, you have to install it and get it working. Step 1: Preparing the webapp Here we assume that you have a web server up and running on the localhost at port Tomcat 4.

An example of weblogic. Step 3: starting the web server This varies on a product-by-product basis. Step 4: Validate the Installation After installing the web application and dependencies, you should make sure that the server is running the web application. Validate Axis with happyaxis Follow the link Validate the local installation's configuration This will bring you to happyaxis.

Look for some services From the start page, select View the list of deployed Web services. The first step is to add your code to the server. Classpath setup In order for these examples to work, java must be able to find axis.

Step 7: Testing This step is optional, but highly recommended. Change directory to the distribution directory for xml-axis and execute the following command or its Unix equivalent : On Windows java -cp. Advanced Installation: adding Axis to your own Webapp If you are experienced in web application development, and especially if you wish to add web services to an existing or complex webapp, you can take an alternate approach to running Axis.

The core concepts are Add axis. What if it doesn't work? But before you rush to post your own problems to the mailing list, a word of caution: Axis is free. Post to the user mail list, not the developer list. You may think the developer mail list is a short cut to higher quality answers. But the developers are also on the user list along with many other skilled users--so more people will be able to answer your questions.

Also, it is helpful for all user issues to be on one list to help build the searchable mailing list archive. Don't ask non-Axis-related questions. Even questions about the MS Soap toolkit or. NET client side, don't get many positive answers--we avoid them. Never bother posting to the soapbuilders mailing list either, that is only for people developing SOAP toolkits, not using them--all off-topic messages are pointedly ignored.

There is no guarantee that anyone will be able to solve your problem. The usual response in such a situation is silence, for a good reason: if everybody who didn't know the answer to a question said "I don't know", the list would be overflowed with noise. Don't take silence personally. Never expect an immediate answer. Even if someone knows the answer, it can take a day or two before they read their mail.

So if you don't get an answer in an hour or two, don't panic and resend.