Question regarding the installation of a J2EE 6.40 Add-in

[Former Member]

Hi all,

I would like to install a J2EE engine on a test instance of ECC 5.0 and have a few questions regarding the installation...

Do I have to use the MASTER CD to first install the J2EE engine (Support Package 0) and then apply the latest support packages found on the SAP Marketplace?

Or should be able to directly install the J2EE Add-In by using the latest support packages found on the SAP Marketplace?

Best regards,

Xavier Vermaut

[Former Member · Accepted solution]

Hi Xavier,

You can install latest J2EE addins directly without installing first SP0 and then applying patch.

Regards,

Bhavik

[Former Member · Accepted solution]

Thanks Bhavik for your reply,

That's what I actually thought but I get the following problem... Here's what I wrote into my customer message... I am still waiting for an answer and would like to get this solved ASAP

Dear SAP,

We would like to install the J2EE 6.40 Add-In on our ECC 5.0 instance

(TST) but get the following error message at the very beginning of the

installation

> Cannot find an installed ABAP system, which is a prerequisite for a

> J2EE Add-In installation. The installation cannot continue.

We checked the installation logs (sapinst_dev.log) and found the

following :

> Found these instances:

> sid: MGR, number: 00, name: DVEBMGS00, host: erpqs1a

> sid: TST, number: 10, name: DVEBMGS10, host: erpqs1a

Why does the installation say that it can not find any ABAP systems when

having previously found the 2 different instances running on this

server?

Would this problem be related to the fact that we have two instances on

this server?

Please find hereunder the way we performed this installation :

01) Download of the 4 different parts of SAP J2EE Engine 6.40 SP 10

(Solaris 10 - Oracle)

Part I : SAPINST10_0-20000121.SAR (Solaris 64)

Part II : CTRLORA10_0-20000121.SAR (Solaris 64)

Part III : J2EERTOS10_0-20000121.SAR (Solaris 64)

Part IV : J2EERT10_0-10001982.SAR (OS Independant)

02) Extract these 4 archives into /install/J2EE_640

03) Check Java Version and Environment Variables

04) Check Solaris Pre-Requisites

05) Adapt "product.xml" as specified in OSS Note 697535 (IGS)

06) Log in as 'root'

07) Set DISPLAY environment Variable

08) Move to the Installation directory

( /install/J2EE_640/SAPINST-CD/SAPINST/UNIX/SUNOS_64 )

09) ./sapinst

10) In the 'Welcome to Netweaver Installation' screen, select

=> Dialog Instance Finalization

Any idea how to get this solved?

Best regards,

Xavier Vermaut

Message was edited by: Xavier Vermaut

[Former Member · Accepted solution]

Hello,

"=> Dialog Instance Finalization" is only for an ABAP-Dialog-Instance.

If you want to install in a central system, you have to use the install CDs and choose the similar point "Java System Finalization" . This installs the SCS instance, the Java part of the central instance, and the Java database schema.

regards,

[Former Member]

Xavier,

I have a similar problem when following step b) on page 19 of "Web AS Java 6.40 SR1 Solaris:Oracle" part II. This is the "Dialog Instance Finalization" step from the install guide.

I am installing from NW04 SR1 disks. I get error CJS-20049

"Cannot find an installed ABAP system"

I also have 2 SAP systems on this host and sapinst detects them both including the SCS associated with this new instance. However, sapinst reports some messages about the Unix admin account for the other SAP system on the host (a WebAS 6.20), but no account info for the admin account of this new install.

Anybody have ideas or experience?

Thanks,

Bill Looper

looper@water.ca.gov

[Former Member]

Hi Xavier,

You cannot install a J2EE add-in directly from a SP install. You need to use the SAPInst on the master cd to install the SP9 (if you have SR1 version), and then upgrade it to SP13 using the SAPInst from the SP package you downloaded.

Be sure your ABAP stack is on the same SP level while you upgrade J2EE.

Regards,

Hart