Adding Java Stack to Upgraded ERP6.0 ABAP Stack

[Former Member]

Hi All,

I have upgraded SAP R/3 4.7 to ERP 6.0 SR3 with MSSQL 2005 on Windows 2003 Enterprise Edition.

Right now my upgraded system is having only ABAP stack and I want to add Java Stack to It.

I want to know is there any specific procedure to do this task, or it can be done just as normal installation by running Sapinst and selecting the Java stack option when it shows the component to be installed and then making sure the correct instance number is avaliable (01 in my case as 00 is for ABAP stack) and making sure for the ports that will be assigned to Java Stack.

Please clear me if I am wrong and there is some separate procedure by SAP.

Regards

Vinay Paul.

[markus_doehr2]

> I have upgraded SAP R/3 4.7 to ERP 6.0 SR3 with MSSQL 2005 on Windows 2003 Enterprise Edition.

> Right now my upgraded system is having only ABAP stack and I want to add Java Stack to It.

I can just recommend: Avoid dual stack installation.

Better install a complete AS-Java separately, may be on the same machine (different system number and <SID>). This has a number of BIG advantages:

- If you do system copies you must use sapinst. It's no more possible to just copy the database over as you do with ABAP-only instances

- future upgrades must be done in parallel, means, if an ERP upgrade will come you'll need to run two upgrade processes in parallel

- Support packages must be in sync, that means, if you have to patch your java, you will have to patch your ABAP too which can lead to dependency chains where you need to install a certain patch to fix your Java (e. g. Portal) but end up in the need to patch your central application (which you certainly do not want).

SAP also recommends avoiding the dual stacks. If you read

https://www.sdn.sap.com/irj/sdn/landscapedesign

--> How to Deploy SAP NetWeaver - Guidance for better System Landscape Designs

you'll see that SAP recommends installing separate instances (apart from special cases).

Markus

[Former Member]

>

> I can just recommend: Avoid dual stack installation.

>

> Better install a complete AS-Java separately, may be on the same machine (different system number and <SID>). This has a number of BIG advantages:

>

Dear Markus,

Thanks for reply...

I do not have Seperate machine to install AS-Java...So as you said I can do this on same machine as well with different SID and Instance no. ... so We have to install Seperate database as well for AS-JAVA ..So now Our both AS ABAP and AS JAVA are like just totally not attached with each other so we have to do some connectivity things as well to connect ABAP + JAVA...

Earlier we use to install ABAP + JAVA on the same machine with just different instance no. but now as you said we have to install one database different SID + different instance now. ...difference is of DATABASE and SID then dual stack..

Our reason to install JAVA instance is we want to take out some ADOBE FORMS ...so for this ADS is required and so is JAVA.

If I will install AS JAVA on the same machine with different SID and Different instance no. then how to make the connectivity between AS ABAP and AS JAVA ?

Kindly Suggest !

Regards,

VP

[markus_doehr2]

> If I will install AS JAVA on the same machine with different SID and Different instance no. then how to make the connectivity between AS ABAP and AS JAVA ?

The same way you'd do it if both instances were installed together. There are only some very few occurences where a direct connection is used (FastRFC), I'm not really aware of any application that makes use of that (former alleged) advantage of having a dual stack.

Markus

[Former Member]

Dear Markus,

Thanks for your response and sorry for the late reply, due to some reasons this task was delayed.

I am now installing the java stack separately with different SID and instance number on the same machine.

I have installed the MSSQL Client with different SID and now I am running the sapinst

I have one Doubt that is which menu option should i go with in sapint for installing java instance

1 SAP ERP6.0 SR3>SAP Systems>MS SQL Server>Central System>Central System.

2 SAP ERP6.0 SR3>Software Life Cycle Option>JAVA Addin for ABAP>MS SQL Server>Central System-->

SCS for Java Add-in

Database Instance for Java Add-in

Central Instance for Java Add-in

I think I have to go with 1st option but not 100% sure.

After that I have to select only "AS Java from Additional Net-weaver Software Units"

Regards

VP

[Former Member]

You need to select the first option.

Select AS JAVA, EP & EP Core.

For using the Adobe forms in productions it requires a seperate licenses. Make sure that you got the licenses.

Mahesh

[Former Member]

Hi Mahesh,

But We do not require EP neither EP core.. ...it will make server heavy unnecessarily.

And do we have to select anything from ERP software units ?

I am not able to find the relevant document for this on service marketplace.

Kindly confirm.

Thanks,

VP

[Former Member]

Hi Mahesh,

But We do not require EP neither EP core.. ...it will make server heavy unnecessarily.

And do we have to select anything from ERP software units ?

I am not able to find the relevant document for this on service marketplace.

Kindly confirm.

Thanks,

VP

[markus_doehr2]

I can just highly recommend thinking again about a Java Addin. It's no more recommended, you will create a hard dependency to the ERP system which you most likely don't want. If you fix an error in the Java part then you must install the corresponding ABAP support package in your ERP system!

For Adobe DS you need an AS Java only, no portal necessary.

I would especially install AD on a separate box/instance due to its hardware requirements and patching cycles.

Markus