on 01-22-2009 1:10 PM
Hi
We are in the process of migrating our CRM 4.0 running Web AS 620 (ABAP+J2EE) to CRM 4.0 Web AS 640 (ABAP +J2EE) on Windows 64 bit Microsoft cluster with Oracle 10g.
I have gone thru lot of installation guides for ABAP + J2EE (640) and do not find the steps for adding J2EE Server (640) to the Cluster.
As per the various guides, I believe the following procedure is right:
1) Install CI (ABAP)
2) Install Database Instance
3) MSCS Node A Configuration
4) MSCS Node B Configuration
5) Select Java Add-in for ABAP - Oracle (SAPINST)
- SCS Installation
- Java Database Schema Installation
- Central Instance Finanlization
I am not sure about the Step 5, as I would have choosen Java System Finalization option under Java Add-in for ABAP (Oracle) in the Central System installation. If I choose Jaa System Finalization, the step 3 & 4 would be choosen after the Java System Finalisation.
Any thoughts on this would be highly appreciated.
Regards
Chandu
Resolved by myself.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi chandu,
just another question:-)
The Cluster is now working fine and i can connect by Visual Administrator. But when i connect (attach) another database in SQL Server for use with SAP, i cannot connect by visual administrator anymore.
I'm not shure whether there are any informations stored in the database which are important to the visual administrator and are different from the informations in the earlier used database.
Kind regards
Stefan
Hi,
Since you had planned for Java Add-in cluster installation, i suggest first you complete the ABAP installation completely in cluster. Test the system in failover also.
Once the system is stable, plan for java addin.
Refer this SAP Note 779253 - Clustering your Java Add-In System on Windows.
Given clear information about the Java Add-In installation in windows clustering.
Hope it helps
Regards
KT
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Just to update on my progress.
I noticed there are different options in SAPINST for 32 bit & 64 bit. If you adding Java add-on to ABAP on 32 bit, the said SAP note needs to be implemented as there is no "High Availability option" under Java Add-on for ABAP in 32 bit SAPINST.
However, in 64 bit there is a option for High Availability install under Java add-on for ABAP. So, I believe the steps suggested in the notes are automated in 64 bit.
I checked both the sapinst and noted the following:
32 bit:
NW04 - Java Add-in for ABAP
Oracle
- Central System
- Distributed System
64 bit:
NW04 - Java Add-in for ABAP
Oracle
- Central System
- Distributed System
- High Availability System
- SCS installation
- Java Database Schema installation
- Central Instance Finalisation
- Dialog Instance Finalisation
We are configuring cluster on 64 bit, so i believe the steps outlined in the notes are automated under 64 bit.
Please comment.
Regards
Chandu
Hi
I have completed the installation as per the following steps:
1) Install CI (ABAP)
2) Install Database Instance
3) MSCS Node A Configuration
4) MSCS Node B Configuration
5) Select Java Add-in for ABAP - Oracle (SAPINST)
High-Availability System
- SCS Installation
- Java Database Schema Installation
However, when we are installing Central Instance Finalisation, we are
getting following error:
The ABAP Central Instance of SAP system CRQ is installed on host
mfacrmq. You have to run the installation step J2EE Add-in for ABAP
System on the installation host of the Central Instance.
Any ideas?
Regards
Chandu
Hi Chandu,
here are the steps:
1. Installation of SQL Server 2005 in a cluster (virtual Group for SQL)
2. Installation of the central instance on Node A (physical Node)/Abap non-unicode
3. Installation of the database instance on Node A (physical Node)/Abap non-unicode
4. Clustering of Node A
5. Clustering of Node B
So far everything is fine, the cluster with sap is running.
6. Installation of the supported SDK from sun on both nodes in the same directory.
7. copy of the profiles ending with the name of the physical node in another folder so that only the profiles dealing with the virtual host resides in the profiles folder.
8. starting of java system finalization from the netweaver master cd with the command mentioned in sapnote 779253.
9. The installation stopps with the error message: The Abap Central Instance of SAP System XXX is installed on host xxx (that is the virtual host). You have to run the installation step J2EE Add-in ... on the installation host of the central instance.
Best regards
Stefan
My installation was on Oracle and it worked.
Do you have options for Distributed System in the SAPINST or options for High Availability?
In the high availability tab in the SAPINST, you can first install SCS instance and then CI finalisation by starting SAPINST from the command prompt using ABAP virtual host.
I really had terrible time with SAP Support in resolving the issue. At the end, I resolved the issue by myself, by trying various steps.
One more thing, I had to delete SCS & DB Schema for Java before started the process.
Would interested with the solution.
Regards
Chandu
Hi
i have performed an scs installation with the high availability part on the netweaver master. After installation it is running as an instance on the physical not the virtual node. By starting the java system finalization i get the same error as before. Curious. I am performing all the steps on Node A.
Regards
Stefan
You are absolutely right! I missed the point that i have to perform the installation of the scs just from the command line. Before i started with this procedure after the installation of scs.
So following your advice everything worked fine.
Thank you very much - this was very helpful!
Kind regards
Stefan
Any comments on this?
Regards
Chandu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.