Installation GuideInstallation of Additional Usage Types or Technical Usages on SAP Systems Based on SAP NetWeaver 73 73 EHP1 Application Server Java

SAP ERP 60 EHP 6 (SAP Business Suite 7i 2011) on SAP NetWeaver 73 73 EHP1

Target Audience System Administrators Technical Consultants

CUSTOMERDocument version 120 ndash 2012-11-01

Document History

CAUTION

Before you start the implementation make sure you have the latest version of this document

You can find the latest version at the following locationhttpservicesapcomerp-inst

The following table provides an overview of the most important document changes

Version Date Description

120 2012-11-01 Updated Version

110 2012-08-06 Updated Version

10 2011-11-08 Initial Version

222 CUSTOMER 2012-11-01

Document History

CAUTION

Before you start the implementation make sure you have the latest version of this document

You can find the latest version at the following locationhttpservicesapcomerp-inst

The following table provides an overview of the most important document changes

Version Date Description

120 2012-11-01 Updated Version

110 2012-08-06 Updated Version

10 2011-11-08 Initial Version

222 CUSTOMER 2012-11-01

Table of Contents

Chapter 1 Introduction 5

11 About this Document 5

12 Naming Conventions 5

13 References to Java Support Package Manager Documentation 5

14 References to Maintenance Optimizer Documentation 5

15 Restrictions 6

Chapter 2 Planning 7

21 Planning the System Landscape 7

22 Options Available in the Java Support Package Manager 7

23 Sizing for Additional Usage Types or Technical Usages 8

24 SAP Notes 8

Chapter 3 Preparation 9

Chapter 4 Installation 13

Chapter 5 Post-Installation 15

Chapter 6 Deactivation 17

2012-11-01 CUSTOMER 322

This page is left blank for documents that are printed on both sides

1 Introduction

11 About this Document

This documentation describes how you can install additional Java technical usages or usage types on

an existing SAP ERP 60 EHP6 Java system based on SAP NetWeaver 73 73 EHP1 Java

ldquoExisting SAP systemrdquo means that this SAP system has at least Application Server Java (BASIC)

To install additional Java technical usages or usage types in an existing SAP system you cannot use

software provisioning manager 10 Instead you have to use the Java Support Package Manager (JSPM)

You perform the installation of additional technical usages or usage types in an existing Java system to

optimize total cost of ownership (TCO) That is you do not have to install a complete additional Java

system to run these additional technical usages or usage types

12 Naming Conventions

In this section the following naming conventions apply

The term ldquoSAP ERP 60 EHP6rdquo is used for ldquoSAP ERP 60 including SAP Enhancement Package 6 -

Technical Usage Central Applicationsrdquo

The term ldquotechnical usagerdquo is a valid synonym for ldquousage typerdquo In the following we use the term

ldquousage typerdquo both for SAP NetWeaver usage types and SAP ERP technical usages

13 References to Java Support Package Manager Documentation

This documentation does not describe how to run Java Support Package Manager (JSPM) in detail All

documentation references in this section regarding the JSPM tool refer to the following entry point in

the SAP Library

httphelpsapcomnw73 Application Help Function-Oriented View English SAP NetWeaver Library

Function-Oriented View Solution Life Cycle Management Software Logistics Java Support Package Manager

14 References to Maintenance Optimizer Documentation

This documentation does not describe how to run the Maintenance Optimizer (MOPZ) in SAP Solution

Manager All documentation references in this section regarding the Maintenance Optimizer refer to

the following entry point in the SAP Library

1 Introduction

11 About this Document

2012-11-01 CUSTOMER 522

This page is left blank for documents that are printed on both sides

1 Introduction

11 About this Document

This documentation describes how you can install additional Java technical usages or usage types on

an existing SAP ERP 60 EHP6 Java system based on SAP NetWeaver 73 73 EHP1 Java

ldquoExisting SAP systemrdquo means that this SAP system has at least Application Server Java (BASIC)

To install additional Java technical usages or usage types in an existing SAP system you cannot use

software provisioning manager 10 Instead you have to use the Java Support Package Manager (JSPM)

You perform the installation of additional technical usages or usage types in an existing Java system to

optimize total cost of ownership (TCO) That is you do not have to install a complete additional Java

system to run these additional technical usages or usage types

12 Naming Conventions

In this section the following naming conventions apply

The term ldquoSAP ERP 60 EHP6rdquo is used for ldquoSAP ERP 60 including SAP Enhancement Package 6 -

Technical Usage Central Applicationsrdquo

The term ldquotechnical usagerdquo is a valid synonym for ldquousage typerdquo In the following we use the term

ldquousage typerdquo both for SAP NetWeaver usage types and SAP ERP technical usages

13 References to Java Support Package Manager Documentation

This documentation does not describe how to run Java Support Package Manager (JSPM) in detail All

documentation references in this section regarding the JSPM tool refer to the following entry point in

the SAP Library

httphelpsapcomnw73 Application Help Function-Oriented View English SAP NetWeaver Library

Function-Oriented View Solution Life Cycle Management Software Logistics Java Support Package Manager

14 References to Maintenance Optimizer Documentation

This documentation does not describe how to run the Maintenance Optimizer (MOPZ) in SAP Solution

Manager All documentation references in this section regarding the Maintenance Optimizer refer to

the following entry point in the SAP Library

1 Introduction

11 About this Document

2012-11-01 CUSTOMER 522

1 Introduction

11 About this Document

This documentation describes how you can install additional Java technical usages or usage types on

an existing SAP ERP 60 EHP6 Java system based on SAP NetWeaver 73 73 EHP1 Java

ldquoExisting SAP systemrdquo means that this SAP system has at least Application Server Java (BASIC)

To install additional Java technical usages or usage types in an existing SAP system you cannot use

software provisioning manager 10 Instead you have to use the Java Support Package Manager (JSPM)

You perform the installation of additional technical usages or usage types in an existing Java system to

optimize total cost of ownership (TCO) That is you do not have to install a complete additional Java

system to run these additional technical usages or usage types

12 Naming Conventions

In this section the following naming conventions apply

The term ldquoSAP ERP 60 EHP6rdquo is used for ldquoSAP ERP 60 including SAP Enhancement Package 6 -

Technical Usage Central Applicationsrdquo

The term ldquotechnical usagerdquo is a valid synonym for ldquousage typerdquo In the following we use the term

ldquousage typerdquo both for SAP NetWeaver usage types and SAP ERP technical usages

13 References to Java Support Package Manager Documentation

This documentation does not describe how to run Java Support Package Manager (JSPM) in detail All

documentation references in this section regarding the JSPM tool refer to the following entry point in

the SAP Library

httphelpsapcomnw73 Application Help Function-Oriented View English SAP NetWeaver Library

Function-Oriented View Solution Life Cycle Management Software Logistics Java Support Package Manager

14 References to Maintenance Optimizer Documentation

This documentation does not describe how to run the Maintenance Optimizer (MOPZ) in SAP Solution

Manager All documentation references in this section regarding the Maintenance Optimizer refer to

the following entry point in the SAP Library

1 Introduction

11 About this Document

2012-11-01 CUSTOMER 522

SAP Solution Manager 71

httphelpsapcomsolutionmanager71 Application Help SAP Library English Maintenance

Management Maintenance Optimizer

SAP Solution Manager 70 ltEnhancement Packagegt

httphelpsapcomsolutionmanager70 Application Help SAP Solution Manager EHP1 ltcurrent

SP levelgt SAP Library English Change Request Management and Change Control Maintenance Optimizer

15 Restrictions

The existing SAP system must have at least usage type Application Server Java (BASIC)

Installing additional usage types might cause interdependencies between already installed SAP

applications Therefore carefully consider the implications of running software lifecycle processes

that affect your existing system landscape if you want to update an SAP system (this means

performing upgrades applying support packages installing enhancement packages) you have to

meet the requirements for all installed applications including SAP NetWeaver For SAP NetWeaver-

specific distribution models see httpwwwsdnsapcomirjsdnserver-infrastructure

EXAMPLE

You have successfully installed additional usage types for SAP SRM 70 EHP2 and SAP ERP 60

EHP6 Java on an existing SAP NetWeaver 73 73 EHP1 Application Server Java Now you want

to update your SAP ERP 60 EHP6 system with usage type XSS to the latest enhancement

package together with the latest enhancement package of SAP NetWeaver 73 73 EHP1

We do not recommend that you install additional usage types or technical usages in an existing

dual-stack (ABAP+Java) system For more information see How to Deploy SAP NetWeaver Dual Stack

vs Separated Stacks at httpscnsapcomdocsDOC-14359

1 Introduction

15 Restrictions

622 CUSTOMER 2012-11-01

2 Planning

21 Planning the System Landscape

You have to plan your SAP system landscape with the new additional usage types or technical usages

you want to install

We recommend that you check the following documents for that purpose

Documentation Where to Download

Master Guide mdash SAP Enhancement Package 1 for SAP NetWeaver 73

httpservicesapcominstallnw73

Master Guide mdash SAP Enhancement Package 6 for SAP ERP 60

httpservicesapcomerp-inst

SAP Business Suite Landscape Implementation - Technical Planning Guide

httpservicesapcominstguides SAP Business Suite Applications ltSAP ERP | SAP CRM | SAP SRMgt SAP enhancement packages for ltSAP ERP | SAP CRM | SAP SRMgt ltReleasegt SAP enhancement package ltNumbergt for ltSAP ERP | SAP CRM | SAP SRMgt ltReleasegt

Maintenance Planning Guide Using SAP Solution Manager ltRelease SPgt including Landscape Management Database (LMDB)

httpservicesapcommopz Information Links and Downloads How Torsquos and Guides

22 Options Available in the Java Support Package Manager

Check which Java Support Package Manager (JSPM) option is required for your additional usage type

installation

RECOMMENDATION

We strongly recommend that you use the Maintenance Optimizer in SAP Solution Manager

to calculate the required software packages and to generate the required stack configuration file

automatically

The Maintenance Optimizer supports you in selecting and downloading all required usage type

and Support Package files In addition the Maintenance Optimizer generates a stack configuration

2 Planning

21 Planning the System Landscape

2012-11-01 CUSTOMER 722

file and provides it to JSPM using the EPS inbox of SAP Solution Manager JSPM then uses this

information to install the usage type and Support Package files

If you use a stack configuration file generated by the Maintenance Optimizer you have to apply JSPM

option Support and Enhancement Package Stack

23 Sizing for Additional Usage Types or Technical Usages

You use the Quick Sizer tool available at httpservicesapcomsizing to get information about

additional disk space and RAM requirements for the additional usage types or technical usages you

want to install

For more information about the Quick Sizer and available sizing guides see the Master Guide mdash SAP

Enhancement Package 1 for SAP NetWeaver 73 at httpservicesapcominstallnw73 Planning

24 SAP Notes

Make sure that you have read the following SAP Notes

SAP Note Number Title

1584864 InstAddTechnical Usages BS 7i 2010 on 73 73 EHP1 Java Hubs

1538263 Sizing Information for SAP NetWeaver 73

2 Planning

23 Sizing for Additional Usage Types or Technical Usages

822 CUSTOMER 2012-11-01

3 Preparation

Procedure

1 Check which usage types are already installed on your system

You can do this in one of the following ways

Start JSPM and choose the Deployed Components tab

Check the usage type system information page of your system using the URL http

lthostgtlthttp_portgtutlUsageTypesInfo

For more information about how to do this see Viewing the Deployed Components in the Java Support

Package Manager documentation

2 Check the dependencies for the usage types you want to install

Technical Usages of SAP NetWeaver 73 73 EHP1

Technical Usage Name UT_NAME Long Text Depends on

AS AS Java Extensions Application Server Java (BASIC)

ADOBE ADOBE Adobe Document Services

Application Server Java (BASIC)

CE-APPS CE-APPS Composite Application Framework

Application Server Java (BASIC)

COMP-ENV COMP-ENV Composition Environment Platform

Application Server Java (BASIC) CE-APPS

BPM BPM Business Process Management and Business Rules Management

Application Server Java (BASIC) CE-APPS COMP-ENV

CE-VOICE CE-VOICE Composition Voice Application Server Java (BASIC) CE-APPS COMP-ENV

CE-PROCESS CE-PROCESS Guided Procedures Application Server Java (BASIC) CE-APPS COMP-ENV

ESR ESR Enterprise Services Repository

Application Server Java (BASIC)

DI DI Development Infrastructure

Application Server Java (BASIC)

BI BI Business Intelligence Java Application Server Java (BASIC)

EPC EPC EP Core ndash Application Portal

Application Server Java (BASIC)

3 Preparation

2012-11-01 CUSTOMER 922

Technical Usage Name UT_NAME Long Text Depends on

EP EP Enterprise Portal Application Server Java (BASIC) EPC

BASIC-RA BASIC_RA Demo Applications Application Server Java (BASIC)

Technical Usages of SAP ERP 60 EHP6

Technical Usage Name UT_NAME Long Text Depends on

BD BD SAP ERP Biller Direct Application Server Java (BASIC) AS Java Extensions

BP ERP BP-ERP SAP ERP Business Packages (Portal Content)

Application Server Java (BASIC) AS Java Extensions EPC BP-Common

XECO XECO SAP ERP Extended E-Selling Components

Application Server Java (BASIC) AS Java Extensions

XSS_core XSSC SAP ERP Self Services Core Application Server Java (BASIC) AS Java Extensions EPC BP-XSS BP-Common

XSS XSS SAP ERP Self Services Application Server Java (BASIC) AS Java Extensions EPC BP-XSS BP-Common XSS_core

LSOCP LSOCP SAP ERP Learning Solution Content Player

Application Server Java (BASIC) AS Java Extensions

UCES UCES SAP ERP Utilities Customer E-Services

Application Server Java (BASIC) AS Java Extensions

IS-R-SRS RetailStore SAP ERP Retail Store Applications

Application Server Java (BASIC) AS Java Extensions

BP-XSS BP-XSS SAP ERP Portal Content Self Services

Application Server Java (BASIC) AS Java Extensions EPC BP-Common XSS

BP-Common BP-Common SAP ERP Portal Content Common

Application Server Java (BASIC) AS Java Extensions EPC

ELSTER ELSTER SAP Integration for Elster Can be deployed on one of the following SAP NetWeaver 73 73

EHP1 Java EE Adapter Engine (optional standalone unit)

Java stack of an SAP NetWeaver 73 73 EHP1 Process Integration (PI) system

3 Preparation

1022 CUSTOMER 2012-11-01

Technical Usage Name UT_NAME Long Text Depends on

BCONS BCONS SAP Integration for BCONS Can be deployed on one of the following SAP NetWeaver 73 73

EHP1 Java EE Adapter Engine (optional standalone unit)

Java stack of an SAP NetWeaver 73 73 EHP1 Process Integration (PI) system

SWIFT SWIFT SAP Integration for SWIFT Can be deployed on one of the following SAP NetWeaver 73 73

EHP1 Java EE Adapter Engine (optional standalone unit)

Java stack of an SAP NetWeaver 73 73 EHP1 Process Integration (PI) system

3 Check hardware and software requirements

Check Java virtual memory settings according to SAP Note 1538263

Check the requirements for the Java Support Package Manager as described in Requirements for

Free Disk Space in the Java Support Package Manager documentation

4 You make the required software packages available for the additional usage types you want to

install

You have to use the Maintenance Optimizer to calculate the required software packages and

generate the stack configuration file

Proceed as described in Maintenance Procedure Scenarios Maintenance Transaction with Installation of an

Enhancement Package in the Maintenance Optimizer documentation

In this case you have to use JSPM option Support and Enhancement Package Stack for the installation

5 Copy the downloaded SCAs and the appropriate stack definition file to the JSPM inbox directory

as described in Detecting and Changing the JSPM Inbox Directory in the Java Support Package Manager

documentation

3 Preparation

2012-11-01 CUSTOMER 1122

Technical Usage Name UT_NAME Long Text Depends on

BCONS BCONS SAP Integration for BCONS Can be deployed on one of the following SAP NetWeaver 73 73

EHP1 Java EE Adapter Engine (optional standalone unit)

Java stack of an SAP NetWeaver 73 73 EHP1 Process Integration (PI) system

SWIFT SWIFT SAP Integration for SWIFT Can be deployed on one of the following SAP NetWeaver 73 73

EHP1 Java EE Adapter Engine (optional standalone unit)

Java stack of an SAP NetWeaver 73 73 EHP1 Process Integration (PI) system

3 Check hardware and software requirements

Check Java virtual memory settings according to SAP Note 1538263

Check the requirements for the Java Support Package Manager as described in Requirements for

Free Disk Space in the Java Support Package Manager documentation

4 You make the required software packages available for the additional usage types you want to

install

You have to use the Maintenance Optimizer to calculate the required software packages and

generate the stack configuration file

Proceed as described in Maintenance Procedure Scenarios Maintenance Transaction with Installation of an

Enhancement Package in the Maintenance Optimizer documentation

In this case you have to use JSPM option Support and Enhancement Package Stack for the installation

5 Copy the downloaded SCAs and the appropriate stack definition file to the JSPM inbox directory

as described in Detecting and Changing the JSPM Inbox Directory in the Java Support Package Manager

documentation

3 Preparation

2012-11-01 CUSTOMER 1122

This page is left blank for documents that are printed on both sides

4 Installation

Procedure

1 Start JSPM as described in Starting JSPM in the Java Support Package Manager documentation

2 We strongly recommend that you update JSPM to the most recent Support Package stack level as

described in Applying Single Support Packages in the Java Support Package Manager documentation

3 Run JSPM by choosing option Support and Enhancement Package Stack

4 Installation

2012-11-01 CUSTOMER 1322

This page is left blank for documents that are printed on both sides

5 Post-Installation

Procedure

1 After you have finished the deployment with JSPM you still need to activate newly installed

additional technical usages or usage types if the conditions described in Installation apply

If you have run option New Software Components you must always activate the newly installed usage

types or technical usages manually

NOTE

Keep in mind that you have to perform the manual activation separately for every additional

usage type that needs to be activated

Proceed as follows

1 Download Scripts_nw73_bs7i2011ZIP from the Attachments tab of SAP Note 1572608 and

extract it to a local directory on the central instance host of your SAP system

2 Edit script activeUTcmd (Windows) or activeUTsh (UNIX) and enter the required values

(see also the documentation given in the script itself)

JAVA_HOME=ltdirectory where the java bin directory of the SAP JVM is

locatedgt

GLOBAL_DIR=ltpath to the global directorygt

JDBC_CLASSPATH=ltjdbc drivers classpathgt

UT_NAME=[technical name of the technical usage or usage type to be

activated]

PRODUCT=[technical name of your SAP Business Suite application]

SID=ltSAP system ID of the existing SAP systemgt

Only valid for UNIX |

EXAMPLE

JAVA_HOME=usrsapC11SYSexejvmhpia64sapjvm_61008sapjvm_6

GLOBAL_DIR=sapmntC11global

JDBC_CLASSPATH=oracleclient112_64instantclientojdbc14jar

UT_NAME=BP-ERP

PRODUCT=ERP

SID=C11

End of UNIX |

Only valid for Windows |

EXAMPLE

SET JAVA_HOME=fusrsapC11SYSexejvmntia64sapjvm_61008sapjvm_6

5 Post-Installation

2012-11-01 CUSTOMER 1522

4 Installation

Procedure

1 Start JSPM as described in Starting JSPM in the Java Support Package Manager documentation

2 We strongly recommend that you update JSPM to the most recent Support Package stack level as

described in Applying Single Support Packages in the Java Support Package Manager documentation

3 Run JSPM by choosing option Support and Enhancement Package Stack

4 Installation

2012-11-01 CUSTOMER 1322

This page is left blank for documents that are printed on both sides

5 Post-Installation

Procedure

1 After you have finished the deployment with JSPM you still need to activate newly installed

additional technical usages or usage types if the conditions described in Installation apply

If you have run option New Software Components you must always activate the newly installed usage

types or technical usages manually

NOTE

Keep in mind that you have to perform the manual activation separately for every additional

usage type that needs to be activated

Proceed as follows

1 Download Scripts_nw73_bs7i2011ZIP from the Attachments tab of SAP Note 1572608 and

extract it to a local directory on the central instance host of your SAP system

2 Edit script activeUTcmd (Windows) or activeUTsh (UNIX) and enter the required values

(see also the documentation given in the script itself)

JAVA_HOME=ltdirectory where the java bin directory of the SAP JVM is

locatedgt

GLOBAL_DIR=ltpath to the global directorygt

JDBC_CLASSPATH=ltjdbc drivers classpathgt

UT_NAME=[technical name of the technical usage or usage type to be

activated]

PRODUCT=[technical name of your SAP Business Suite application]

SID=ltSAP system ID of the existing SAP systemgt

Only valid for UNIX |

EXAMPLE

JAVA_HOME=usrsapC11SYSexejvmhpia64sapjvm_61008sapjvm_6

GLOBAL_DIR=sapmntC11global

JDBC_CLASSPATH=oracleclient112_64instantclientojdbc14jar

UT_NAME=BP-ERP

PRODUCT=ERP

SID=C11

End of UNIX |

Only valid for Windows |

EXAMPLE

SET JAVA_HOME=fusrsapC11SYSexejvmntia64sapjvm_61008sapjvm_6

5 Post-Installation

2012-11-01 CUSTOMER 1522

This page is left blank for documents that are printed on both sides

5 Post-Installation

Procedure

1 After you have finished the deployment with JSPM you still need to activate newly installed

additional technical usages or usage types if the conditions described in Installation apply

If you have run option New Software Components you must always activate the newly installed usage

types or technical usages manually

NOTE

Keep in mind that you have to perform the manual activation separately for every additional

usage type that needs to be activated

Proceed as follows

1 Download Scripts_nw73_bs7i2011ZIP from the Attachments tab of SAP Note 1572608 and

extract it to a local directory on the central instance host of your SAP system

2 Edit script activeUTcmd (Windows) or activeUTsh (UNIX) and enter the required values

(see also the documentation given in the script itself)

JAVA_HOME=ltdirectory where the java bin directory of the SAP JVM is

locatedgt

GLOBAL_DIR=ltpath to the global directorygt

JDBC_CLASSPATH=ltjdbc drivers classpathgt

UT_NAME=[technical name of the technical usage or usage type to be

activated]

PRODUCT=[technical name of your SAP Business Suite application]

SID=ltSAP system ID of the existing SAP systemgt

Only valid for UNIX |

EXAMPLE

JAVA_HOME=usrsapC11SYSexejvmhpia64sapjvm_61008sapjvm_6

GLOBAL_DIR=sapmntC11global

JDBC_CLASSPATH=oracleclient112_64instantclientojdbc14jar

UT_NAME=BP-ERP

PRODUCT=ERP

SID=C11

End of UNIX |

Only valid for Windows |

EXAMPLE

SET JAVA_HOME=fusrsapC11SYSexejvmntia64sapjvm_61008sapjvm_6

5 Post-Installation

2012-11-01 CUSTOMER 1522

5 Post-Installation

Procedure

1 After you have finished the deployment with JSPM you still need to activate newly installed

additional technical usages or usage types if the conditions described in Installation apply

If you have run option New Software Components you must always activate the newly installed usage

types or technical usages manually

NOTE

Keep in mind that you have to perform the manual activation separately for every additional

usage type that needs to be activated

Proceed as follows

1 Download Scripts_nw73_bs7i2011ZIP from the Attachments tab of SAP Note 1572608 and

extract it to a local directory on the central instance host of your SAP system

2 Edit script activeUTcmd (Windows) or activeUTsh (UNIX) and enter the required values

(see also the documentation given in the script itself)

JAVA_HOME=ltdirectory where the java bin directory of the SAP JVM is

locatedgt

GLOBAL_DIR=ltpath to the global directorygt

JDBC_CLASSPATH=ltjdbc drivers classpathgt

UT_NAME=[technical name of the technical usage or usage type to be

activated]

PRODUCT=[technical name of your SAP Business Suite application]

SID=ltSAP system ID of the existing SAP systemgt

Only valid for UNIX |

EXAMPLE

JAVA_HOME=usrsapC11SYSexejvmhpia64sapjvm_61008sapjvm_6

GLOBAL_DIR=sapmntC11global

JDBC_CLASSPATH=oracleclient112_64instantclientojdbc14jar

UT_NAME=BP-ERP

PRODUCT=ERP

SID=C11

End of UNIX |

Only valid for Windows |

EXAMPLE

SET JAVA_HOME=fusrsapC11SYSexejvmntia64sapjvm_61008sapjvm_6

5 Post-Installation

2012-11-01 CUSTOMER 1522

SET GLOBAL_DIR=FusrsapC11SYSglobal

SET JDBC_CLASSPATH=fsapdbprogramsruntimejarsapdbcjar

SET UT_NAME=BP-ERP

SET PRODUCT=ERP

SET SID=C11

End of Windows |

3 Open a command prompt and run script activeUTcmd (Windows) or activeUTsh (UNIX)

separately for every additional usage type that you need to activate

NOTE

Make sure you run activeUTcmd (Windows) or activeUTsh (UNIX) with the required

command line parameters as described in the documentation given in the script itself

To activate usage types you must set command line parameter ndashaction to true

2 You check the Master Guide for further implementation and configuration steps

CAUTION

You must not run the automated configuration for the added technical usages or usage types

Instead you have to configure them manually

5 Post-Installation

1622 CUSTOMER 2012-11-01

6 Deactivation

If you need to deactivate technical usages or usage types proceed as follows

Procedure

1 Download Scripts_nw73_bs7i2011ZIP from the Attachments tab of SAP Note 1572608 and extract

it to a local directory on the central instance host of your SAP system

2 Edit script activeUTcmd (Windows) or activeUTsh (UNIX) and enter the required values (see

also the documentation given in the script itself)

JAVA_HOME=ltdirectory where the java bin directory of the SAP JVM is locatedgt

GLOBAL_DIR=ltpath to the global directorygt

JDBC_CLASSPATH=ltjdbc drivers classpathgt

UT_NAME=[technical name of the technical usage or usage type to be deactivated]

PRODUCT=[technical name of your SAP Business Suite application]

SID=ltSAP system ID of the existing SAP systemgt

Only valid for UNIX |

EXAMPLE

JAVA_HOME=usrsapC11SYSexejvmhpia64sapjvm_61008sapjvm_6

GLOBAL_DIR=sapmntC11global

JDBC_CLASSPATH=oracleclient112_64instantclientojdbc14jar

UT_NAME=BP-ERP

PRODUCT=ERP

SID=C11

End of UNIX |

Only valid for Windows |

EXAMPLE

SET JAVA_HOME=fusrsapC11SYSexejvmntia64sapjvm_61008sapjvm_6

SET GLOBAL_DIR=FusrsapC11SYSglobal

SET JDBC_CLASSPATH=fsapdbprogramsruntimejarsapdbcjar

SET UT_NAME=BP-ERP

SET PRODUCT=ERP

SET SID=C11

End of Windows |

3 Open a command prompt and run script activeUTcmd (Windows) or activeUTsh (UNIX)

separately for every additional usage type that you need to deactivate

6 Deactivation

2012-11-01 CUSTOMER 1722

6 Deactivation

If you need to deactivate technical usages or usage types proceed as follows

Procedure

1 Download Scripts_nw73_bs7i2011ZIP from the Attachments tab of SAP Note 1572608 and extract

it to a local directory on the central instance host of your SAP system

2 Edit script activeUTcmd (Windows) or activeUTsh (UNIX) and enter the required values (see

also the documentation given in the script itself)

JAVA_HOME=ltdirectory where the java bin directory of the SAP JVM is locatedgt

GLOBAL_DIR=ltpath to the global directorygt

JDBC_CLASSPATH=ltjdbc drivers classpathgt

UT_NAME=[technical name of the technical usage or usage type to be deactivated]

PRODUCT=[technical name of your SAP Business Suite application]

SID=ltSAP system ID of the existing SAP systemgt

Only valid for UNIX |

EXAMPLE

JAVA_HOME=usrsapC11SYSexejvmhpia64sapjvm_61008sapjvm_6

GLOBAL_DIR=sapmntC11global

JDBC_CLASSPATH=oracleclient112_64instantclientojdbc14jar

UT_NAME=BP-ERP

PRODUCT=ERP

SID=C11

End of UNIX |

Only valid for Windows |

EXAMPLE

SET JAVA_HOME=fusrsapC11SYSexejvmntia64sapjvm_61008sapjvm_6

SET GLOBAL_DIR=FusrsapC11SYSglobal

SET JDBC_CLASSPATH=fsapdbprogramsruntimejarsapdbcjar

SET UT_NAME=BP-ERP

SET PRODUCT=ERP

SET SID=C11

End of Windows |

3 Open a command prompt and run script activeUTcmd (Windows) or activeUTsh (UNIX)

separately for every additional usage type that you need to deactivate

6 Deactivation

2012-11-01 CUSTOMER 1722

NOTE

Make sure you run activeUTcmd (Windows) or activeUTsh (UNIX) with the required

command line parameters as described in the documentation given in the script itself To

deactivate usage types you must set command line parameter ndashaction to false

6 Deactivation

1822 CUSTOMER 2012-11-01

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options

Cross-references to other documentation or published works

Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

2012-11-01 CUSTOMER 1922

Typographic Conventions

Example Description

ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo

ExampleExample

Arrows separating the parts of a navigation path for example menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

httpwwwsapcom Textual cross-references to an internet address

example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note for example SAP Note 123456

Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options

Cross-references to other documentation or published works

Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and

names of installation upgrade and database tools

EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE

EXAMPLE Keys on the keyboard

2012-11-01 CUSTOMER 1922

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +4918 0534 34 34F +4918 0534 34 20

wwwsapcom

copy Copyright 2012 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer StreamWork SAP HANA and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countriesBusiness Objects and the Business Objects logo BusinessObjects Crystal Reports Crystal Decisions Web Intelligence Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd Business Objects is an SAP companySybase and Adaptive Server iAnywhere Sybase 365 SQL Anywhere and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc Sybase is an SAP company

2022 CUSTOMER 2012-11-01

Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way

2012-11-01 CUSTOMER 2122

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

• Installation of Additional Usage Types or Technical Usages on SAP Systems Based on SAP NetWeaver 73 73 EHP1 Application Server Java
• • Table of Contents
  • 1 Introduction
  • • 11 About this Document
    • 12 Naming Conventions
    • 13 References to Java Support Package Manager Documentation
    • 14 References to Maintenance Optimizer Documentation
    • 15 Restrictions
    • • 2 Planning
      • • 21 Planning the System Landscape
        • 22 Options Available in the Java Support Package Manager
        • 23 Sizing for Additional Usage Types or Technical Usages
        • 24 SAP Notes
        • • 3 Preparation
          • 4 Installation
          • 5 Post-Installation
          • 6 Deactivation
          • • Copyright and trademarks

Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll other product and service names mentioned are the trademarks of their respective companies Data contained in this document serves informational purposes only National product specifications may varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) for informational purposes only without representation or warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing herein should be construed as constituting an additional warranty

DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way

2012-11-01 CUSTOMER 2122

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

• Installation of Additional Usage Types or Technical Usages on SAP Systems Based on SAP NetWeaver 73 73 EHP1 Application Server Java
• • Table of Contents
  • 1 Introduction
  • • 11 About this Document
    • 12 Naming Conventions
    • 13 References to Java Support Package Manager Documentation
    • 14 References to Maintenance Optimizer Documentation
    • 15 Restrictions
    • • 2 Planning
      • • 21 Planning the System Landscape
        • 22 Options Available in the Java Support Package Manager
        • 23 Sizing for Additional Usage Types or Technical Usages
        • 24 SAP Notes
        • • 3 Preparation
          • 4 Installation
          • 5 Post-Installation
          • 6 Deactivation
          • • Copyright and trademarks

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom

copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice

• Installation of Additional Usage Types or Technical Usages on SAP Systems Based on SAP NetWeaver 73 73 EHP1 Application Server Java
• • Table of Contents
  • 1 Introduction
  • • 11 About this Document
    • 12 Naming Conventions
    • 13 References to Java Support Package Manager Documentation
    • 14 References to Maintenance Optimizer Documentation
    • 15 Restrictions
    • • 2 Planning
      • • 21 Planning the System Landscape
        • 22 Options Available in the Java Support Package Manager
        • 23 Sizing for Additional Usage Types or Technical Usages
        • 24 SAP Notes
        • • 3 Preparation
          • 4 Installation
          • 5 Post-Installation
          • 6 Deactivation
          • • Copyright and trademarks