HOW TO RUN WEB LOGIC 8.1 SERVER

I want to run weblogic8.1 server ... so any body can u help me? I need urgently so kindly pls sent immediately......Thanking you
[149 byte] By [SIVACHANDRAN55a] at [2007-11-27 9:14:34]
# 1

hi

http://support.sas.com/documentation/configuration/serverinstallations/weblogic/InstallInstructions913sp2.html

Installing the BEA WebLogic Server and Deploying Web Applications Using SAS 9.1.3 SP2, SP3, and SP4

This document explains how to install and configure supported versions of the BEA WebLogic Server that are available for download from the BEA web site. You can use this J2EE application server to run such SAS web applications as SAS Web Report Studio and SAS Information Delivery Portal. These installation instructions do not apply to the OEM version of WebLogic that SAS ships with the SAS Solutions.

Note: If you wish to upgrade your existing WebLogic 8.1 installation to Service Pack 3, follow the instructions located below at Using the Service Pack 3 Upgrade Installer for WebLogic Server 8.1.

Note: WebLogic 8.1 Service Pack 4 is supported only on Solaris 10 (SPARC). Please use the full installer; the upgrade installer is not supported.

Note: If you want to make sure that all of the required patches have been applied to your server, follow the instructions located below at Ensuring That All Necessary Patches Have Been Installed.

If you are an experienced WebLogic administrator, there is not much special information that you will need. You simply install the correct version of the BEA WebLogic Platform梱ou can determine the correct version by visiting the SAS Third Party Software Downloads for SAS 9.1.3 SP2, SP3, and SP4 page梐nd configure a managed server in which the SAS web applications can run. To avoid having to edit advanced properties in the SAS Configuration Wizard, you should use the following names and port numbers when you configure the WebLogic servers and domain:

* Name of domain: mydomain

* Name of managed server: myserver

* Listen port for administration server: 7501

* Listen port for managed server: 7001

You should also read over the information in this document concerning the configuration of your managed server and the steps you must perform after installing your SAS web applications.

If you are new to the BEA WebLogic Server, you can use the instructions in this document to install and configure WebLogic for use with the SAS web applications and to deploy the SAS web applications to the server. The document discusses the following tasks:

* Acquiring the Server and Security Patches

* Acquiring and Installing the JDK

* Installing the Server

* Applying Required Patches

* Configuring the Server

* Deploying Applications

Note: This documentation is not meant to replace the BEA documentation. It is intended for users who want to quickly configure the BEA WebLogic Server in a way that will facilitate the deployment of the SAS Intelligence Platform.

Acquiring the Server and Security Patches

To acquire the server:

1. Determine the version of BEA WebLogic Server required and patches needed. To do this, go to the SAS Third Party Software Downloads page. Click the Web Application Servers link for the version of the SAS Intelligence Platform that you are installing. This will take you to the Application Servers table. This table lists supported operating systems and WebLogic Server versions. The Notes column contains information about required patches, if any.

2. Contact BEA to acquire the relevant version of BEA WebLogic Server and patches.

Note: If you are downloading the installer, we recommend that you download the WebLogic Server Package Installer rather than the WebLogic Server Net Installer.

Acquiring and Installing the JDK

A Java Virtual Machine (JVM) is required to run WebLogic Server. The JDK requirement varies depending on your operating system. WebLogic Server supports specific JDKs provided by other vendors such as HP, IBM, and Sun.

To acquire the JDK:

1. Determine the version of the Java Development Kit (JDK) that you need. To do this, go to the SAS Third Party Software Downloads page. Click the Java Development Kit link for the version of the SAS Intelligence Platform that you are installing. This will take you to the Java Software Development Kits table. This table lists supported JDKs by operating system.

2. Review the Notes column, and follow the the Download link to obtain the JDK.

3. 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:

1. Start the WebLogic installation program in console mode. (You can also start the installer in graphical mode, if your operating system supports it, by omitting the mode=console argument. See Installing WebLogic Platform Using Graphical-Mode Installation for more information.)

Note that BEA WebLogic Server 8.1 SP4 is supported only on Solaris 10 (SPARC).

* On Windows systems, you can use Windows Explorer to navigate to the EXE file that you downloaded. Then double-click the icon representing the file.

* On Solaris systems, change directories to the directory that contains the BIN file that you downloaded. Then enter the following commands:

chmod a+x filename.bin

./filename.bin -mode=console

* On HP-UX and AIX systems, you download a JAR file. Start the installer by adding your JDK's bin directory to your PATH and then entering this command:

java -jar filename.jar mode=console

2. On all systems, the BEA installation program will load, and you will see a Welcome screen.

3. In the Welcome screen, click Next.

4. In the BEA License Agreement screen, select Yes and click Next.

5. In the Choose BEA Home Directory screen, select Create a new BEA Home, leave the default value in the BEA Home Directory text box, and 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.

6. In the Choose Install Type screen, select Custom Installation and click Next.

7. In the Choose Components screen, leave WebLogic Server selected, deselect WebLogic Workshop, and click Next.

8. In the Choose Product Directory screen, leave the default value in the Product Installation Directory text box, and click Next.

9. Windows only: In the Install Windows Services screen, select the Yes radio button, and click Next.

10. At this point, the WebLogic files will be copied to your disk. When the copy is complete, the Installation Complete screen will appear. In the Installation Complete screen, uncheck the Install XML Spy check box (Windows only), deselect Run Quickstart, and click Done.

Note: On HP-UX systems, you must also install a supplemental JAR. The installation instructions that you need are located here.

Applying Required Patches

When you downloaded the BEA WebLogic Platform, you should also have downloaded any required patches. Some of these patches come with installation instructions. For those patches, follow the installation instructions. For the other patches, which are delivered as JAR files, you "apply" the patches by adding the JAR files to your managed server's CLASSPATH. You will add these files to the CLASSPATH later, when you configure the managed server.

Configuring the Server

To configure your server:

1. Start the BEA WebLogic Configuration Wizard by executing the script config.extension. This script is located in BEA-install-dir\weblogic81\common\bin. (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.)

2. In the wizard's Create or Extend a Configuration screen, select Create a new WebLogic configuration, and click Next.

3. In the Select a Configuration Template screen, leave the default value (Basic WebLogic Server Domain) selected, and click Next.

4. In the Choose Express or Custom Configuration screen, select the Custom mode, and click Next.

5. In the Configure the Administration Server screen, set the Name to myadminserver, set the Listen port to 7501, and click Next.

6. In the Managed Servers, Clusters, and Machine Options screen, select Yes, and click Next.

7. In the Configure Managed Servers screen, click Add. Then, set Name to myserver, set Listen port to 7001, and click Next.

8. In the Configure Clusters screen, click Next.

9. In the Configure Machines screen, first select the correct tab: Machine if you are configuring the software on a Windows system and Unix Machine if you are working on a UNIX system. Then click Add. Set the Name to new_machine_1 if on a Windows system. Set the Name to new_unix_machine_1 if on a UNIX system. Click Next.

10. In the Assign Servers to Machines screen, move the myadminserver and myserver icons from the Server list to the Machine or UNIX Machine list. Then click Next.

11. In the Database (JDBC) Options screen, click Next.

12. In the Messaging (JMS) Options screen, click Next.

13. 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.e, additional users, groups, and roles), and click Next.

14. Windows only: In the Configure Windows Options screen, select both Yes radio buttons, and click Next.

15. Windows only: In the Build Start Menu Entries screen, set the text fields as shown in the list below:

* Shortcut link name - Start SAS Managed Server

* Program - startManagedWebLogic.cmd

* Argument - myserver http://localhost:7501/

* Working directory -

* Description - Link to start myserver outside of Node Manager

Then, click Next.

16. On the Configure Server Start Mode and Java SDK screen:

1. Select Production Mode.

2. Select Other Java SDK, and then either use Browse to navigate to the installation directory for the J2SDK that you installed for use with the SAS Intelligence Platform (for example, C:\j2sdk1.4.2_05) or specify the directory.

3. Click Next.

17. In the Create WebLogic Configuration screen, enter the name mydomain in the Configuration Name text box, and click Create.

18. The Configuration Wizard creates your configuration. In the Creating Configuration screen, deselect Start Admin Server, if visible, then click Done. You will exit the BEA WebLogic Configuration Wizard.

19. Set the common environment variables for WebLogic by editing the file commEnv.extension in BEA-install-dir\weblogic81\common\bin. Set JAVA_HOME to point to the installation directory for the Java 2 SDK that you installed for use with the SAS Intelligence Platform. Then save the file.

20. Start the administration server and the Node Manager.

* Windows: You can start these services from the Services window in the Control Panel (Start > Settings > Control Panel > Administrative Tools > Services). Right-click the icon for each service, and select Start from the pop-up menu.

* UNIX: Start these processes by executing these scripts:

o BEA-install-dir/user_projects/domains/mydomain/startWebLogic.sh

o BEA-install-dir/weblogic81/server/bin/startNodeManager.sh

21. With the administration server and the Node Manager running, you can start the WebLogic Server Console in order to configure your managed server. Start the console by opening a web browser and browsing to http://localhost:7501/console.

22. Log on to the console using the administrator user ID and password that you specified while running the BEA WebLogic Configuration Wizard.

23. 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. Set the following properties:

* Java Home: Directory where you installed the version of the Java 2 SDK required by the SAS Intelligence Platform, for example, C:\j2sdk1.4.2_05.

* BEA Home: Directory where you installed WebLogic, for instance, C:\bea.

* Class Path: Prepend the following JAR files to your current CLASSPATH:

o The JAR files for any patches that you have not already installed.

o JDK-install-dir\lib\tools.jar

o BEA-install-dir\weblogic81\server\lib\weblogic_sp.jar

Note: Depending on which WebLogic Server release, service pack, or patch has been installed, the weblogic_sp.jar file might not exist on the system. Regardless of whether the file currently exists, BEA recommends that it be included in the CLASSPATH to ensure compatibility with any updates.

o BEA-install-dir\weblogic81\server\lib\weblogic.jar

o BEA-install-dir\weblogic81\server\lib\ojdbc14.jar

o JDK-install-dir\jre\lib\rt.jar

o BEA-install-dir\weblogic81\server\lib\webservices.jar

On Windows systems, use semicolons to separate CLASSPATH entries, and on UNIX systems, use colons.

Note: The directory separator used in the paths above is appropriate for Windows systems. On UNIX systems, replace the backslashes with slashes (/).

* Arguments: - For information about what JVM options to enter here, see the SAS Intelligence Platform Web Application Administration Guide, which is available from this web site. Search for the section "Quick Start Settings." The exact set of arguments that you should use varies depending on your platform and on how many users your SAS web applications willl have.

* Security Policy File: Full path to the file weblogic.policy. The file is located in BEA-install-dir\weblogic81\server\lib.

After setting these properties, click the Apply button.

24. You can now start the managed server. You can do this by performing these steps in the WebLogic Server Console:

* In the left-hand pane, expand the Servers folder, right-click the icon for myserver, and select Start/stop this server from the pop-up menu.

* In the right-hand pane, click the Start this server link.

drvijayy2k2a at 2007-7-12 22:02:51 > top of Java-index,Enterprise & Remote Computing,Web Tier APIs...