Installing SAP Web Application Server

Proven Practice

Application Servers - Installing SAP Web Application Server

Product(s): IBM Cognos 8.3, SAP Web Application Server

Area of Interest: Infrastructure

IBM Cognos Proprietary Information DOC ID: AS02 Version 8.3.0.0

Installing SAP Web Application Server

Copyright

Your use of this document is subject to the Terms of Use governing the Cognos software products and related services which you have licensed or purchased from Cognos. The information contained in this document is proprietary information of Cognos Incorporated and/or its licensors and is protected under copyright and other applicable laws. You may use the information and methodologies described in this document 'as is' or you may modify them, however Cognos will not be responsible for any deficiencies or errors that result from modifications which you make. Copyright 2007 (c) Cognos Incorporated. All Rights Reserved. You can print selected pages, a section, or the whole book. Cognos grants you a non-exclusive, non-transferable license to use, copy, and reproduce the copyright materials, in printed or electronic format, solely for the purpose of providing internal training on, operating, and maintaining the Cognos software. This document is maintained by the Best Practices, Product and Technology team. You can send comments, suggestions, and additions to Best Practices, Product and Technologies.

IBM Cognos Proprietary Information

mailto:+Best%20Practices%20-%20Product%20and%20Technology?subject=Proven%20Practices%20-%20feedback

mailto:+Best%20Practices%20-%20Product%20and%20Technology?subject=Proven%20Practices%20-%20feedback

Installing SAP Web Application Server


TABLE OF CONTENT 1 Introduction ...........................................................................................................................................1

1.1 Purpose..............................................................................................................................................1 1.2 Scope.................................................................................................................................................1 1.3 Definitions, Acronyms, and Abbreviations.......................................................................................1 1.4 Assumptions......................................................................................................................................3

2 Base Product Installation......................................................................................................................5 2.1 SAP WAS 6.40 .................................................................................................................................5

2.1.1 Demo-only Install for SAP WAS 6.40 with MaxDB ..............................................................5 2.1.2 Install SAP WAS 6.40 with Oracle .......................................................................................10 2.1.3 Possible Problems..................................................................................................................15 2.1.4 Installing another SAP WAS Central Instance on the same machine....................................16

3 Product Update Installation ...............................................................................................................20 3.1 Service Packs ..................................................................................................................................20

4 Start and Stop SAP WAS ...................................................................................................................26 4.1 SAP WAS 6.40 ...............................................................................................................................26

4.1.1 Run SAP WAS Services via Services ...................................................................................26 4.1.2 Run SAP WAS Services via SAP Management Console......................................................26

5 Advanced Topics..................................................................................................................................28 5.1.1 Extending SAP WAS: Adding a new Java Dialog Instance .................................................28 5.1.2 Deploying on a SAP WAS Cluster........................................................................................33

5.2 Web Server plugins.........................................................................................................................33 6 Application Server References / Resources.......................................................................................34

6.1 Troubleshooting ..............................................................................................................................34 6.1.1 SAP WAS Log Viewer..........................................................................................................34

6.2 Web Sites ........................................................................................................................................35 6.3 Documentation................................................................................................................................35

Installing SAP Web Application Server 1

1 Introduction

1.1 Purpose This document is for those who have limited experience with SAP Web Application Server and who wish to set up a SAP WAS environment. The document consists of detailed instructions that explain the steps required. The goal is to set up a basic environment for testing purposes and not necessarily a high performance production environment. Except where noted, the primary focus of this document will be to cover the setup steps required for IBM Cognos 8.3.

1.2 Scope The instructions in this document will work cross platform however the examples shown will be based on a Windows install. UNIX installations require slight modifications to syntax but should otherwise be identical. For example, regarding the syntax for variables, use ${VARIABLE} for UNIX and %VARIABLE% for Windows. Consult your UNIX documentation for more information regarding commands, syntax and scripting. This document will take you through the steps to install SAP Web Application Server for use with IBM Cognos 8.

1.3 Definitions, Acronyms, and Abbreviations

Term Definition JVM Java Virtual Machine

A software "execution engine" that safely and compatibly executes the byte codes in Java class files on a microprocessor (whether in a computer or in another electronic device). The JVM is responsible for the hardware and operating system independence of the J2SE platform, the small size of compiled code (bytecodes), and platform security.

J2SE Java 2 Platform, Standard Edition There are two principal products in the J2SE platform family: J2SE Runtime Environment (JRE) and J2SE Development Kit (JDK).

JRE Java Runtime Environment The JRE provides the Java APIs, Java virtual machine, and other components necessary to run applets and applications written in the Java programming language. It is also the foundation for the technologies in the Java 2 Platform, Enterprise Edition (J2EE) for enterprise software development and deployment. The JRE does not contain tools and utilities such as compilers or debuggers for developing applets and applications

JDK Java Development Kit The JDK is a superset of the JRE, and contains everything that is in the JRE, plus tools such as the compilers and debuggers necessary for developing applets and applications.

J2EE Java 2 Platform, Enterprise Edition Combines a number of technologies in one architecture with a comprehensive Application Programming Model and Compatibility Test Suite for building enterprise-class server-side applications.



The Java 2 Platform, Enterprise Edition (J2EE) defines the standard for developing multitier enterprise applications. The J2EE platform simplifies enterprise applications by basing them on standardized, modular components, by providing a complete set of services to those components, and by handling many details of application behavior automatically, without complex programming.

SAP WAS SAP Web Application Server Visual Administrator The Visual Administrator enables you to carry out administration

tasks at runtime and to control each individual server service. The Visual Administrator must establish a connection to the running server.

SAP Config tool You can use the config tool to configure the cluster elements of the SAP J2EE Engine from a remote system. There is a GUI-based and a text-based interface. With the config tool you can also configure the J2EE Engine while it is offline.

SAP Management Console The Management Console displays all the installed components in a hierarchy. When you open the hierarchy, an icon for a server instance appears; this icon may be green, yellow, or gray. The system database is a blue icon.

Description of SAP Web AS 6.40 Instances

SAP Instance Description Central instance The central instance is the core component of an SAP system.

Exactly one central instance must exist in each SAP system. The central system usually provides all SAP system utilities, especially the central utilities enqueue service and message service.

Database instance The database instance means generally speaking the database which is used for data storage by the J2EE Engine. The database schema as such is a named collection of objects, such as tables, views, clusters, procedures, and packages, associated with a particular user.

Central services instance SAP Central Services (SCS) form the basis of communication and synchronization for the J2EE cluster. A central services instance consists of the enqueue service and the message service. Central Services are a special example of a Java instance.

Java instances A Java instance is a unit in the SAP Web Java cluster, which can be started, stopped, and monitored separately. It runs on a physical server; but it is also possible to run several instances on one server. An instance is identified by the system ID (SID) and the instance number. These instances are optional SAP instances that can be used to create additional application servers. This way, you can scale the performance of your SAP system in an easy way. The dialog instances of an SAP Web AS Java system are called Java dialog instances.



1.4 Assumptions

Before continuing, make sure the following prerequisites have been met.

• That you have the necessary licenses and files (appropriate for your environment) to perform the

installation and any applicable updates. These can be acquired from SAP (customer) or internally (IBM). Once the installation is complete, the user must contact SAP to obtain a permanent license. The SAP licenses are not available from IBM. SAP WAS 6.40, SP13 is supported on Windows.

• That you have the necessary access rights to perform the installation. It is best if the user used to

install SAP Web Application Server is the same user used to setup and run IBM Cognos 8. Root access is not a requirement for the installation on UNIX. On Windows, the user should be a member of the Administrators group.

• That you have the necessary system resources to perform the installation. There is considerably

more memory, hard disk space and CPU power required to run any full Application Server than running Tomcat. The minimal requirements for SAP WAS should be compared to available resources. Please refer to your SAP documentation and the SAP Support Portal.

For version 6.40, running with less than 1 GB of RAM is not suggested (although it may be possible for testing purposes only), 2GB should be considered a minimum. Make sure you have adequate disk space to install SAP WAS 6.40. You will require 4 GB for SAP WAS. Please refer to your SAP customer documentation and the SAP Support Portal for more information. SAP Notes are released on a regular basis with product updates.

• The JVM used is one that is supported by SAP WAS and IBM Cognos 8. You must install this

before installing SAP WAS. SAP WAS does not package a JVM with its install kit. You must copy the contents of <cognos8_install_directory>\bin\jre\<version>\lib\ext to <JAVA_HOME>\jre\lib\ext. Do not overwrite existing files. You cannot use the JRE shipped with the IBM Cognos 8 install.

For version 6.40, make sure JDK 1.4.2_07 (or higher) is installed on the machine. SAP WAS 6.40 does not support JDK 1.3 or 1.5. Consult the SAP Support Portal for the latest SAP Notes on this subject.

• SAP WAS 6.40 requires that the host name be 12 characters or less in length. If your machine name is longer, you will have to rename the machine and have it registered to the network with the new machine name. Contact your Help Desk for details on this.

• For SAP WAS 6.40, a database server is required for use as their Content Store for the SAP WAS

Central Instance. SAP WAS 6.40 supports Oracle, MS SQL Server and DB2. There is a separate set of installation DVD’s available from SAP for each database type. The database must be installed, and configured and running before starting the SAP WAS installation program. Refer to your database documentation for more information on how to install the database server. Also, each database type requires sufficient resources to install and run. For example, for Oracle, you will need another 4 GB for the database server. If you intend to use the same database server as the IBM Cognos 8 Content Store, as well, use a different database instance. The database instance created by the SAP WAS install should be reserved for the use of SAP WAS, only. They should not reside in the same database instance.



Note: If you are setting up SAP WAS 6.40 for demonstration purposes only, you can install from the SAP Developer Studio DVD. It installs MaxDB for use as the SAP Content Store. Refer to the appropriate section for the install steps.

• The file system must be NTFS. Do not install SAP directories on a FAT partition. If the machine

is not using NTFS, it must be changed before installing SAP WAS. Contact your Help Desk for more information on how to do this.

• That you have the customer documentation available as a resource. You should have both the

IBM Cognos 8 documentation as well as the SAP WAS documentation.

• That you are familiar with the operating system (OS) with which you are using. This document assumes you are familiar with the OS. This includes user commands at the command line, syntax and scripting.

• That you are familiar with IBM Cognos 8. You should already know how to setup and run the

product using Tomcat.



2 Base Product Installation

2.1 SAP WAS 6.40

SAP WAS 6.40 is part of SAP’s platform solution called SAP NetWeaver 2004.

Note: SAP WAS 6.40, with SAP J2EE Engine 6.40, SP9 is supported for CRN 1.1 MR2, only. For the IBM Cognos 8 release, a minimum of SAP WAS 6.40, SP13 is supported.

Before starting, make sure the prerequisites have been followed. Specify your JAVA_HOME environment variable before starting the install.

Note: If you are setting up SAP WAS 6.40 for demonstration purposes only, you can install from the SAP Developer Studio DVD. It includes MaxDB for use as the SAP Content Store. For this install, you do not need Oracle Database server.

2.1.1 Demo-only Install for SAP WAS 6.40 with MaxDB

The following steps describe a SAP WAS install that can be used for demo purposes, only. Instead of using the Oracle Database Server, it utilizes a database called MaxDB provided with the SAP WAS install. The following setup should not be used by customers for production environments. It should only be used for development, testing or demo purposes.

For this release, you must map a network drive to the location of the SAP install DVDs. The DVD required for this install is (51030277) SAP WEB AS Java, SAP NetWeaver Developer Studio.

The steps outlined below depict the Windows installation.

1. You must login as a member of the Administrators group in order to run the install. Navigate to the DVD location or the location where you have copied the DVD. Navigate to <SAP_DVD>\ DEVST\SAPINST\NT\I386 and run sapinst.exe. (For example, if you copied the DVD to a hard drive location, you would go to E:\sap_dvd\DEVST\SAPINST\NT\I386.)

2. In the Welcome screen, navigate to Install a SAP NetWeaver Developer Workplace. Highlight Install a SAP NetWeaver Developer Workplace and click Next.



3. In the next dialog, you are prompted to select a Standard Installation or a Custom Installation. Select Custom Installation and click Next.

4. The next dialog specifies the Installation options. Select the Install J2EE engine, database and create DB schema on the local host option and uncheck the Install SAP NetWeaver Developer Studio checkbox.

Note: SAP J2EE Engine 6.30 was shipped with the original SAP NetWeaver ’04 release. This must be installed before you can install the update for SAP J2EE Engine 6.40, SP13. The steps to install SAP J2EE Engine 6.40, SP13 are outlined later in this document.



5. The next dialog prompts you for the system parameters for the J2EE Engine. Enter a unique value for the SAP System ID. Select the drive and enter a password for the SAP System users.

6. In the following dialog, enter password for the Administrator and Guest users for the J2EE Engine. You are also prompted for instance numbers, max heap size for memory and the JDK location. Unless you have specific requirements, you can take the default values.



7. In the next dialog, select the J2EE DB option. The J2EE Engine with ABAB is not discussed in this document. For more information, refer to the SAP documentation.

8. Enter the database parameters in the next dialog. It’s best to use the same ID for the database that you used for the SAP System ID. You can select the drive and set the data volume. Enter a password for the database user.

These parameters will be used for the MaxDB setup. The install will install the database and create services in your system registry. The database files will be located in <drive>:\sapdb.

9. The next dialog shows a summary of the install details. If you want to make changes, click the Back button. Click Start to begin the installation. The installation will take several minutes.



10. The Installation Progress dialog will be displayed as the program installs SAP WAS.

You may encounter errors while the install is running.

When this occurs, click on the View Log button to see the error messages. Refer to the “Possible Problems” section below for tips on troubleshooting.

11. When the install completes, you will see the following dialog. Click OK.



This completes the first part of the installation of SAP WAS. The files have been installed in <drive>:\usr\sap.

You must now install a service pack to upgrade the SAP J2EE Engine to version 6.40, SP13. Proceed to the Product Update Installation section of this document to continue. Refer to the SAP Support Portal for more information and the latest SAP Notes. The update install for SP13 must be applied before using the SAP WAS instance for IBM Cognos 8.

2.1.2 Install SAP WAS 6.40 with Oracle

For this example, we will use Oracle9i as the database server. The SAP WAS install creates an Oracle database instance for use as its Content Store. The Oracle database server must be installed on the same machine where the SAP WAS installation will reside. If Oracle is not available and running when the SAP WAS install is running, the SAP WAS install will fail with errors. Refer to your Oracle documentation for more information on how to install Oracle DB Server. If you intend to use Oracle as the IBM Cognos 8 Content Store, as well, use a different database instance. The database instance created by the SAP WAS install should be reserved for the use of SAP WAS, only. They should not reside in the same database instance.

For this release, you must map a network drive to the location of the SAP install DVDs. Or, if you are installing from the DVDs, you must make them available in parallel. You can accomplish this by using two DVD drives or by copying the DVDs to a local drive. The DVDs required for this install are (51030191) Installation Master DVD and (51030277) SAP WEB AS Java, SAP NetWeaver Developer Studio.

The steps outlined below depict the Windows installation.

1. You must login as a member of the Administrators group in order to run the install. Navigate to the DVD location or the location where you have copied the Master DVD. Navigate to <SAP_DVD>\IM1\SAPINST\NT\I386 and run sapinst. (For example, if you copied the DVD to a hard drive location, you would go to E:\master_dvd\IM1\SAPINST\NT\I386.)



2. In the Welcome screen, expand SAP NetWeaver ’04, then J2EE System and Central System. Highlight Install a J2EE Server in Default Mode.

3. You will encounter the next dialog if you’ve already run the install program on the machine. It asks you if you want to run a new installation or continue an old one. Make sure the Run a new installation option is selected.

4. In the next dialog, you are prompted for the location of the J2EE Engine 6.30 installation files. These are located on the (51030277) SAP WEB AS Java DVD. Navigate to the J2EE1 directory in the Browse dialog and click OK.




5. The next dialog shows install parameters for the SAP System ID, the Database Instance it will use for its Content Store (not the same as the IBM Cognos 8 Content Store) and the location of the JVM. If you want to change these, check the checkbox for the appropriate parameter, otherwise, do nothing.



6. You will be prompted to enter a password for the administrative user in the next dialog. This user is created by the SAP install and will run the SAP services.

7. You are then prompted for the location of the IGS install files in the next dialog. Navigate to the IGS directory on the (51030277) SAP WEB AS Java DVD and click OK in the Browse dialog.



8. The next dialog shows a summary of the install details. If you want to make changes, click the Back button. Click Start to begin the installation. The installation will take several minutes.

9. The Installation Progress dialog will be displayed as the program installs SAP WAS.

You may encounter errors while the install is running.

When this occurs, click on the View Log button to see the error messages. Refer to the “Possible Problems” section below for tips on troubleshooting.

10. When the install completes, you will see the following dialog. Click OK.



This completes the first part of the installation of SAP WAS. The files have been installed in <drive>:\usr\sap.

You must now install a service pack to upgrade the SAP J2EE Engine to version 6.40, SP13. Proceed to the Product Update Installation section of this document to continue. Refer to the SAP Support Portal for more information and the latest SAP Notes.

2.1.3 Possible Problems

Throughout the course of the installation, you may encounter errors while it is running. Here are some examples of known issue’s that may occur. To avoid such errors, ensure the machine has adequate resources. Also, it would be beneficial if other processes unrelated to the installation and the operation of the system were shutdown while the installation is in progress.

• ERROR 2005-01-12 12:08:20

CJS-00084 SQL statement or script failed. DIAGNOSIS: Error message: ORA-03113: end-of-file on communication channel.

If you encounter this error, click on the Retry button.

• If you notice that the status of the install program seems to be stuck on “Stopping instance ‘JC00’…” or “Stopping instance ‘SCS01’…”, you can help it continue by manually stopping the associated SAP service in Services.



• The following error may occur during the Registering SDM Targets, Deploy JDDI or SAP J2EE Engine Server Core phases of the SAP WAS install.

MUT-02041 SDM call of deploySdaList ends with returncode 4. See output of logfile C:\Program Files\sapinst_instdir\WEBAS_640_J2EE_ONLY\CS\DEFAULT\callSdmViaSapinst.log. If this error occurs, then navigate to <drive>:\usr\sap\<SAPSID>\<Jxxx>\SDM\program\config directory and open the sdmrepository.sdc file in a text editor. For example, if SAP WAS is installed on the D drive, with an SAPSID of J2E and an instance called JC00, look for D:\usr\sap\JCM\JC02\SDM\program\config\sdmrepository.sdc In the text editor, search for the following text.

<sdm-operation_mode> standalone </sdm-operation_mode>

Change standalone to integrated.

<sdm-operation_mode> integrated </sdm-operation_mode>

Save the file and continue with the install. This error may occur more than once. You will have to redo the workaround.

2.1.4 Installing another SAP WAS Central Instance on the same machine

If you intend to install and deploy the IBM Cognos 8 components as separate applications, then you’ll need to install another SAP WAS instance. For a full instance, you’ll need to run the base install and then the SP13 update, again. If installing on the same machine as an existing SAP WAS instance, the install program will detect that one already exists.

The same prerequisites used for the single server install must be followed.

1. You must login as a member of the Administrators group in order to run the install. Navigate to the DVD location or the location where you have copied the Master DVD. Navigate to <SAP_DVD>\IM1\SAPINST\NT\I386 and run sapinst. (For example, if you copied the DVD to a hard drive location, you would go to E:\master_dvd\IM1\SAPINST\NT\I386.)

2. In the Welcome screen, expand SAP NetWeaver ’04, then J2EE System and Central System. Highlight Install a J2EE Server in Default Mode.



3. You will encounter the next dialog if you’ve already run the install program on the machine. It asks you if you want to run a new installation or continue an old one. Make sure the Run a new installation option is selected.

4. In the next dialog, you are prompted for the location of the J2EE Engine 6.30 installation files. These are located on the (51030277) SAP WEB AS Java, SAP NetWeaver Developer Studio DVD. Navigate to the J2EE1 directory in the Browse dialog and click OK. Click Next.




5. The next dialog shows install parameters for the SAP System ID, the Database Instance it will use for its Content Store (not the same as the IBM Cognos 8 Content Store) and the location of the JVM. Since the install program has detected the existing install, the SAP System ID and Database Name are blank. You will have to enter new values.

6. Enter a new SAP System ID and Database name. They cannot be the same as the existing SAP System ID and Database. Each system and database must be unique.



For example, the new SAP System ID and Database Name will be JCM.

7. The Parameter Values dialog will be displayed with the user-defined values inserted. If you wish to modify any values, check the checkbox for the parameter and click the Next button. Otherwise, to keep the displayed values.

8. The rest of the dialogs are identical to the original setup. Once the base install has been completed, the update install for SP13 must be applied to the SAP WAS instance before any IBM Cognos 8 components can be deployed.



3 Product Update Installation

In order to run IBM Cognos 8, you must install a service pack for SAP WAS 6.40. Specifically, you need the service pack install for SAP J2EE Engine 6.40, SP13. It is the J2EE Engine which powers SAP WAS.

3.1 Service Packs

IBM Cognos 8 requires SP13 for SAP J2EE Engine 6.40. Customers can download the install kit from the SAP Support Portal. There is an install kit for each of the supported database types used for the SAP Content Store. Be sure to obtain the correct kit. The kit can also be obtained from the Application Server Competency Group for internal IBM Cognos use. The following steps describe the installation of SAP J2EE Engine 6.40, SP13.

1. The Service Pack is downloaded as a series of SAR files, which need to be unzipped using the sapcar.exe utility. Use the following syntax in a command prompt.

sapcar.exe -xf SAPFILE.SAR 2. You must login as a member of the Administrators group in order to run the install. Navigate to

the location of the SAP J2EE Engine 6.40, SP13 update. For example, you copied the Service Pack Update to a hard drive location, such as C:\sap640\SP13update, you would go to C:\sap640\SP13update\SAPINST-CD\SAPINST\NT\I386. Start sapinst.exe.

3. You will see the Welcome page. Select Apply Support Package 13.




4. You will be prompted to provide the profile for the existing installation. SAP retains a software profile on each SAP installation to keep track of the components and versions installed. This is located in <drive>:\usr\sap\<sapid>\SYS\profile\<sapid>_JCxx_servername. For example, D:\usr\sap\J2E\SYS\profile\J2E_JC00_SERVERNAME. You can browse to the location.

Once you have selected it, click OK.

Click Next.


5. In the next dialog, make sure the JDK path is correct and enter your machine name and the password you used for the SAP System users.

6. The update install will now do a Prerequisite Check on the system.



7. A Results dialog will be displayed. If an issue is found, it will be highlighted in red as demonstrated below. You can make the appropriate changes and adjustments before continuing with the installation.

8. A summary for the install will be displayed next. If you wish to change the settings, use the Back button. Click Start to start the installation process. The install can take several minutes.



You will then get a reminder to make sure the database for the SAP Content Store has been started. Make sure it has been started and click OK.



9. The status of the install is then displayed while the install program runs.

10. Once the install program has completed, it will display the following dialog. Click OK to exit.

The SAP WAS install is now ready to be configured for use with IBM Cognos 8.



4 Start and Stop SAP WAS

4.1 SAP WAS 6.40

4.1.1 Run SAP WAS Services via Services

SAP WAS 6.40 is automatically setup to run as a service.

The Windows install creates services that the user can start and stop. The startup type is set to ‘automatic’, by default, but you may wish to reset it to ‘manual’ if you do not want the services to startup whenever the machine reboots. For example, for an install using J2E as the SAP instance, the services would be called SAPJ2E_00 an SAPJ2E_01.

The database services must be running before starting the SAP services.

4.1.2 Run SAP WAS Services via SAP Management Console

You can also start and stop the services by using the SAP Management Console. You can start the console from the Start button. The Management Console displays all the installed components in a hierarchy. When you open the hierarchy, an icon for a server instance appears; this icon may be green, yellow, or gray. The system database is a blue icon.



From the Start button, select All Programs -> SAP Management Console.

To start the application server, highlight ‘<servername> 0’ and click on the Start icon, or right-click and select Start from the menu. If the Message Server and Enqueue Server haven’t been started, yet, start it by selecting ‘<servername> 1’ and clicking start. These must be started before starting the J2EE Server.

To stop the application server, highlight ‘<servername> 0’ and click on the Stop icon, or right-click and select Stop from the menu. You’ll be asked if you really want to stop the instance. Click Yes to stop it, or No to cancel the action.

If you click on Process List, you will see the current status of the server instance.

Note: One difference between SAP WAS 6.40 and 6.20 is that 6.40 launches a program called jlaunch which hosts the JVM. SAP WAS 6.20 launched the actual JVM.



5 Advanced Topics

5.1.1 Extending SAP WAS: Adding a new Java Dialog Instance

If you intend to install IBM Cognos 8 components in a clustered environment, you need to have more than one Java Instance. You can extend the configuration by adding a new Java Dialog Instance. To do this, you must run the SP13 install again to install a new instance. You can install a new Java Dialog Instance on a different machine or on the same machine as the original installation and point the instance to the existing Central Instance.

The following steps illustrate installing a new Java Dialog Instance on the same host machine as the Central Instance. The Central Instance uses an Oracle Database Server.

You will need the SAP System information, usernames and passwords, Oracle database information and JVM information.

1. You must login as a member of the Administrators group in order to run the install. Navigate to the location of the SAP J2EE Engine 6.40, SP13 update. For example, you copied the Service Pack Update to a hard drive location, such as C:\sap640\SP13update, you would go to C:\sap640\SP13update\SAPINST-CD\SAPINST\NT\I386. Start sapinst.exe.

You will see the Welcome page. Select Dialog Instance Installation. Click Next.



2. You will be prompted with a dialog that says the install program has detected an existing installation for SP13. You have the option to start a new install or to continue with an old one. Select the Run a new installation option.

3. The next dialog prompts you for the SAPID of your SAP System and the host name of the Central Instance. Do not check the Central Instance runs UNIX or OS400 checkbox.

Enter the information for your SAP system. (Hint: Look under the installation directory <drive>:\usr\sap, and you should see a directory with the same name as the SAPID.) For example, your SAPID is J2E and the Central Instance host is SERVERNAME.



4. You will be prompted to confirm the JDK install location. Ensure it is correct (the same one used for the Central Instance).

5. The next dialog prompts for the domain. For an installation on the same machine, select Local Installation. For an installation on a different machine than the Central Instance, select either the Installation in Domain of Current User or the Installation in Different Domain option, depending on your circumstances. For domain installations, you need to be a member of the Domain Admins group. Contact your system administrator group and Help Desk for more information on this. Refer to you SAP documentation for more information.

In this example, select the Local Installation option.

6. Enter the passwords for the SAP System and Service Administrators. They must be the same passwords entered when the users were created for the original installation.



7. The next dialog specifies the J2EE Engine parameters for the new Java Dialog Instance. Do not use an existing Instance number. The install program detects existing SAP Instances on the system. Each instance must be unique. Unless you have specific requirements, take the defaults presented in the dialog.

8. The next dialog prompts for the Database information for the Oracle Database Server hosting the SAP WAS Content Store. Make sure the Listener name and the port number are correct.



9. A summary dialog will be displayed before starting the installation. Ensure the information is correct. If you need to change any information, use the Back button. If everything is correct, click on the Start button to start the installation process. The install can take several minutes to complete.

10. The Installation Progress dialog displays the progress of the install. The status of the current phase of the installation is displayed in the status box at the bottom of the dialog.

Once the install completes, a completion dialog is displayed. Click OK to exit the program.



You can configure the new instance via the SAP WAS Config tool and the Visual Administrator.

5.1.2 Deploying on a SAP WAS Cluster

Currently, SAP WAS clustering is not tested or supported for IBM Cognos 8.

5.2 Web Server plugins

Currently, SAP WAS plug-ins are not tested or supported for IBM Cognos 8.



6 Application Server References / Resources

6.1 Troubleshooting

6.1.1 SAP WAS Log Viewer

You can view the SAP logs from its Log Viewer. The Log Viewer provides a runtime control for displaying log messages. These messages assist you in monitoring problems and searching through messages to diagnose problems. There are three ways to access the Log Viewer: the Integrated Log Viewer in the Visual Administrator tool, the Standalone Log Viewer and the Command Line Log Viewer. The Standalone Log Viewer is shown below.

The standalone version of the Log Viewer server provides the ability to monitor logs in the system when the J2EE Engine is not running properly, does not start up at all, or is not available on the system to be monitored.

The standalone installation file is located under the J2EE admin directory (default path: <drive>\usr\sap\<SID>\JC<INSTACE_NUM>\j2ee\admin\logviewer-standalone) and it can be started using logviewer.bat.

The Integrated Log Viewer can only be accessed when SAP WAS is running.




6.2 Web Sites

SAP’s main website: http://www.sap.com

Main page for SAP NetWeaver: http://www.sap.com/solutions/netweaver/index.epx

SAP’s Developer’s Resource site: http://www.sdn.sap.com/sdn

Main dev2dev page for SAP WAS: https://www.sdn.sap.com/irj/sdn/developerareas/netweaver

The following sites require a user login. You can contact your SAP representative for more information.

The Product Availability Matrix lists the supported configurations for SAP products. It can be accessed from the SAP Service Marketplace: http://service.sap.com/pam

SAP Support Portal: https://websmp104.sap-ag.de/support

SAP Partner Portal: https://websmp104.sap-ag.de/partnerportal

6.3 Documentation

SAP’s online documentation can be found at the SAP website listed below. http://help.sap.com

The interface for the library is called the SAP Knowledge Warehouse. http://help.sap.com/saphelp_nw04/helpdata/en/e1/8e51341a06084de10000009b38f83b/frameset.htm

http://www.sap.com/

http://www.sap.com/solutions/netweaver/index.epx

http://www.sdn.sap.com/sdn

https://www.sdn.sap.com/irj/sdn/developerareas/netweaver

http://service.sap.com/pam

https://websmp104.sap-ag.de/support

https://websmp104.sap-ag.de/partnerportal

http://help.sap.com/

http://help.sap.com/saphelp_nw04/helpdata/en/e1/8e51341a06084de10000009b38f83b/frameset.htm

Date post:	12-Sep-2021
Category:	Documents
Upload:	others
View:	7 times
Download:	0 times

Installing SAP Web Application Server

Documents