SolMan 4.0 Installation

Hi,
Can anyone tell me what is the version of java needed for windows 2003 server with oracle 10g to install solution manager 4.0. Then, should we need to install JCE policy also. What is it, how to go about it?
Thanks in advance,
Sailesh K

Hi Sailesh K
I recommend to you to use the version of java j2sdk-1_4_2_09-windows-i586-p.exe, the JCE police will request you in the installation this it you can unload of the Link http://java.sun.com/j2se/1.4.2/download.html this file .zip and you do not have to decompress it, when it asks for the single installation it give the route it where is located the file jce_policy-1_4_2.zip
Best regards
Fernando Torres

Similar Messages

Service Desk Issue in SolMan 4.0 - Installation Number differrence

Hi all,
I am in the process of setting up Service Desk in SolMan 4.0. When I create a message in my satellite system, the message is sent successfully and appears in my Solution Manager. However, I have red light appearing. This is because I need to provide Sold-To Party and Reported By Business Partner entries in the support message. My understanding, please correct me if I am wrong, is that these entries can be automatically filled based on iBase information. I have followed the IMG to setup the iBase.
Upon further investigation, I noticed the following problem. My installation number in the satellite should be XXXXXXXXXX, this is reflected in the System Landscape and iBase. But, when I look at the SAP Attributes tab in the Support Message, the installation number is YYYYYYYYYY. I think that this difference is a possible cause of my problem at hand.
This was the problem as there was an entry in table BCOS_CUST with YYYYYYYYYY in the satellite system. Can anyone tell me where this entry came from? Could this be from configuration of Service Desk?
Thanks,
Robert

Thank you very much!
The problem is solved!
Im my case was necessary to apply SAP Note 1055630.
I have assigned the role "SAP_SM_S_USER_GRP" to the user with RFC_READ connection, refreshed the last alert in DSWP and tha is.
regards!
Thom

SolMan 4.0 Installation - wrong password for SID OFR

Hello all,
i get stuck in the phase 2 of SolMan Installation.
The log states:
"CJS-20004 Invalid password.<br>DIAGNOSIS: The password you specified for user 'S01OFR' is wrong.<br>SOLUTION: Enter the correct password."
S01OFR has been created on the i5 and i can logon with default password SAPOFR.
Where is my mistake ?
I did not define a password for S01OFR in SAPINST process.
Can i change it somewhere to the default password ?
Kind regards,
Juergen Scheckelhoff.

Hi Jürgen,
this sounds like a problem with the user creation and password change.
SAPinst checks whether the users are existing or not before it creates new users and changes the passwords to the masterpassword. If there are already users with the password SAPOFR these users will not changed anymore. (The step of the user creation can not successfully repeated by SAPinst.)
My suggestion would be to restart the installation from scratch. (Without a deeper look into the installation directory I'm unsure what aready is created by the installation.) To delete your current installation just use DLTR3SYS (and if necessary DLTR3INST). Make also sure that you have stopped the TMKSVR beforehand and that you are not logged in as S01OFR anymore.
Before you start to install again the system S01 please check if there are still remaining: WRKOBJ S01*
Am I right when I think that your iSeries users cannot have longer passwords than 8 because of your security level? For this as Volker suggested use another masterpassword with length 8.

SolMan 4 Java Installation/Patching Questions

Hi all,
We had our SolMan 4.0 system installed and configured several months ago. We have a java instance, but do not appear to have any components installed.
I want to install the JSPM, NWA, and SMD tools on the system, but I have been unable to determine which other components are also required.
I have searched through various upgrade and installation manuals, as well as through these forums and many notes, but I am unable to find any sort of list that details which java components need to be installed to run the tools listed above.
I would guess that the following patches are required: J2EE ENGINE CORE TOOLS, LIFECYCLE MGMT TOOLS, SAP J2EE Engine, SAP J2EE Engine Core. I do not know if this list is correct though.
I am looking forward to your responses.
Regards,
Rob

If anyone is running JSPM, NWA, or SMD on their SolMan 4.0 systems, please let me know what other java components are required to be installed.
Thanks

JDK error in SolMan 7.0 installation

I am installing SAP Solution Manager 7.0 on Windows 2003 Server R2 Enterprise x64 and Oracle 10.2.0.4 Patch 8
During the installation its asking me to install a JDK and enter the location.
But when I give the path C:\j2sdk1.4.2_12 it says this JDK does not support the 64-bit data model!
Notes:
1. I have already installed 64-bit PI 7.1 without errors on this same host with this same JDK and OS/DB
2. I searched for 64-bit JDK but only JDK 6 is available and I dont think SAP supports this yet.
3. Besides, I understand that 64-bit JDK is specially available only for SAP customers but I am unable to find it on service.sap/swdc
4. I searched SAP Note 723909 as mentioned in the installation guide but could not get much info out of it.
Can someone tell me how to proceed?
Thanks

I got the download link in SAP Note 941595
Its http://java.sun.com/j2se/1.4.2/SAPsite/download.html
Related links:
What are prerequisites for SAP ISA (Internet Sales)
/message/2787330#2787330 [original link is broken]

SOLMAN 7.0 Installation Error BDS_CONN22

Hi,
I encountered a problem when installing Solution Manager 7.0 on Windows with DB2 for LUW 9.1
During Import ABAP phase I got the following error:
(DB) INFO: BDS_CONN22 created #20080721171911
(DB) ERROR: DDL statement failed with SQL error
( CREATE UNIQUE INDEX "BDS_CONN22~0" ON "BDS_CONN22" ( "CLIENT", "LOIO_ID", "CLASSNAME", "CLASSTYPE", "LOG_SYSTEM", "OBJECT_KEY" ) ALLOW REVERSE SCANS )
(SQL error -205)
error message returned by dsql:
SQL0205N Column or attribute "CLIENT" is not defined in "SAPSOL.BDS_CONN22". SQLSTATE=42703
(DB) INFO: disconnected from DB
Anyone knows how to resolve or bypass this error. I am stuck with the installation.
Thank you.

Hi,
Check with following link
1. http://www.cs.toronto.edu/db/courses/343/Summer2003_L5201/DB2/msgs_2.pdf
2. Check the DB connection at OS level
Regards,
Srini Nookala

SolMan 7 SR3 installation : SMD could not start

Hello all,
It's the third time I'm installing a SolMan 7 SR3 (aka SolMan 4 SR4 previously) on a windows 2k3 SP2 server and for the third time, I'm getting the following error on the SMDAgent :
[Thr 11636] Wed Sep 24 16:34:30 2008
[Thr 11636] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 11636] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 11636] JLaunchISetState: change state from [Waiting for start (1)] to [Initial (0)]
[Thr 11636] JLaunchISetState: change state from [Initial (0)] to [Starting (2)]
[Thr 7500] Wed Sep 24 16:34:31 2008
[Thr 7500] JLaunchIExitJava: exit hook is called (rc = -11112)
[Thr 7500] **********************************************************************
*** ERROR => The Java VM terminated with a non-zero exit code.
*** Please see SAP Note 943602 , section 'J2EE Engine exit codes'
*** for additional information and trouble shooting.
[Thr 7500] JLaunchCloseProgram: good bye (exitcode = -11112)
This SMD is installed and configured by SAPinst. I get this error each time I try to start it.
My workaround was to reinstall a new SMD as standalone, which is working fine.
I just want to know why, using a standard SAPinst, I can't have a working SMD from scratch ?
System configuration :
OS : Windows Server 2003 SP2
Proc : Intel Xeon E5130
JVM : 1.4.2_16-b05
SAP source DVD : 51033517_13
Thanks for your help.

Yes, win 2003, x64.
I know version 18 of java stack causes failures and restarts. We changed to version 17 last week. The process which doesn´t start is SMDAgent.
This is the end of trace file...
JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node
-> arg[ 0]: run
-> arg[ 1]: jcontrol
Thu Oct 16 09:31:26 2008
JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
JLaunchISetState: change state from to
JLaunchISetState: change state from to
Thu Oct 16 09:31:29 2008
JLaunchISetState: change state from to
Thu Oct 16 09:31:33 2008
JLaunchIStartFunc: end of main method (rc = 0)
JLaunchIExitJava: exit hook is called (rc = -11112)
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 943602 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
JLaunchCloseProgram: good bye (exitcode = -11112)

Solman 4.0 installation error at Import Abap phase

Hi All,
I have started installing Solution Mangaer 4.0 and in the Import ABAP phase i am getting the following error.
D:\usr\sap\ISM\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
D:\usr\sap\ISM\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20070219155320
D:\usr\sap\ISM\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20070219155406
D:\usr\sap\ISM\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
D:\usr\sap\ISM\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Sep 1 2006 00:38:35
D:\usr\sap\ISM\SYS\exe\uc\NTI386\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l SAPVIEW.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(DB) INFO: APPL_DIAL created #20070219155406
(DB) INFO: APPL_DOMA created #20070219155406
(DB) INFO: APPL_DTEL created #20070219155406
(DB) INFO: APPL_ENQU created #20070219155406
(DB) INFO: APPL_FUGR created #20070219155406
(DB) ERROR: DDL statement failed
(CREATE VIEW "APPL_FUGRG" ( "AREA" , "DEVCLASS" , "OBJ_NAME" ) AS SELECT T0001."AREA", T0002."DEVCLASS", T0002."OBJ_NAME" FROM "TLIBG" T0001, "TADIR" T0002 WHERE T0001."AREA" = T0002."OBJ_NAME" AND T0002."PGMID" = 'R3TR' AND T0002."OBJECT" = 'FUGR')
DbSlExecute: rc = 103
(SQL error 942)
error message returned by DbSl:
ORA-00942: table or view does not exist
(DB) INFO: disconnected from DB
D:\usr\sap\ISM\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
D:\usr\sap\ISM\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20070219155406
Can you see to that and guide me what needs to be done.
Thanks in advance,
Sailesh K

Hello Sailesh,
The SQL error 942 error occurs when an object that does not exist is
referenced.
R3load creates views on several tables and fails creating
"APPL_FUGRG" because one of the tables referencing is missing
on db-level.
This is most probably due to an error which happened during the
import/load of tables before. It might also be that some load
processes are missing completely.
There may be some corruption of the export files, e.g. when NFS mounted
filesystems or wrong mounted CD-ROMs used
Another reason could be that SAPINST was restarted when there were still
some R3load processes running (Note 454368).
Please check for existence of "bck" files in the same directory
where the SAPVIEW log is (files like SAPVIEW.TSK.bck).
If there is, please retry the load with R3load, by adding the
command -merge_bck according to Note 455195.
Hope this helps,
Dolores

Solman installation stuck with error - SLES 10 , Oracle 10.2.0.4

Hi,
Solman 7.0 installation with ehp1 installation stuck with error - SLES 10 , Oracle 10.2.0.4
the error is at the step install DBA tools -> error is 'select status from v$instance did not match /^\s(\S+)\s$S/gNaNOPEN MIGRATE'.)
Just FYI : we had issue while installing Oracle , we have followed work arround 3 in the SAP Note 980426
Kindly help to proceed further
Thanks & regards,
Prabhakar Reddy.Y.C.

sapinst.log
CJS-00084 SQL statement or script failed. DIAGNOSIS: Error message: ORA-01092: ORACLE instance terminated. Disconnection forced
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, Data Mining and Real Application Testing options
. SOLUTION: For more information, see ora_sql_results.log and the Oracle documentation.
ERROR 2010-11-21 06:55:22.502
MUT-03025 Caught ESAPinstException in Modulecall: ORA-01092: ORACLE instance terminated. Disconnection forced
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, Data Mining and Real Application Testing options
ERROR 2010-11-21 06:55:22.533
FCO-00011 The step runSapdbaroleSql with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|
NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|ind|ind|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraDbaTools|ind|ind|ind|ind|11|0|
runSapdbaroleSql was executed with status ERROR ( Last error reported by the step :Caught ESAPinstException in Modulecall: ORA-01092: ORACLE instance terminated. Disconnection forced
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, Data Mining and Real Application Testing options
Edited by: prabhakaryc on Nov 21, 2010 7:01 AM

Solution Manager 4.0 - MSCS Installation

Hi All,
We are planning for Solman 4.0 Installation in Cluster environment with Windows 2003 server and MS SQL Server 2005.
I have some queries related to this task.
1. Is it possible to install Central Instance in first MSCS node and Database Instance in Additional MSCS node, activate failover in both points. Like if CI system goes down first MSCS node should failover to addtional node and if DI goes down additioonal MSCS node should failover to first MSCS node. Since in cluster installation document of solman, this type of failovers is not mentioned.
2. Enqueue Replication Server Installation: Our solman has both ABAP+Java stack. For this case how we can install ERS. In document it has mentioned we have install 4 times means
ERS1(ABAP), ERS2(Java) - First MSCS Node
ERS3(ABAP), ERS4(Java) - Additional MSCS Node
3. Is it mandatory to install in Dialog Instance in the cluster installation. Since in installation document it is mentioned like atleast one dialog instance should be installed.
Pls give me some inputs for this queries
Thanks in Advance
Regards
KT

Got Solution...Its not Mandatory to install ERS

BW / SolMan Logical System Change

Hello all, I am having a BW related issue and would really appreciate some advice. I realize some of this is for the solMan forums and will cross post (I normally dont)
ENVIRONMENT
New installation of Solution Manager EhP1 (19). System name is ED0. We are running Windows / MS SQL
System is only for Solution Manager ops (client 001), and CUA master (client 950).
BACKGROUND
We want to use full SolMan capabilities. This seems to include some limited BW interaction. We do not use BW in the landscape, so will rely on the "internal" BW in SolMan.
During installation, our person made a new client (000 > 400), set it as default (login/system_client), then ran tc:RSA1 and activated the content. (This sets the client)
Client 400 HAS NOT BEEN USED FOR ANYTHING other than the initial installation, and subsequent activation of BW. It has no connections to other systems, no data, cubes, or anything
PROBLEM
We were NOT AWARE that he had ran RSA1 and activated content, and began using client ED0_001 as our PRODUCTION SolMan client.
We are now unable to run RSA1 in anything but client 400.
We are unable to change the client 001 logical system name because Solution Manager has been built around it.
TROUBLESHOOTING
We changed table RSADMINA / field BWMANDT to 001 from 400. This changed the error from "You can only run in client 400" to "The logical system name has changed" (exit only)
In sandbox I duplicated this problem, then deleted the 400 client (with T000 entry). Changed the login/system_client to 001, RSDAMINA to 001, and ran function module RS_MANDT_UNIQUE_SET (set i_mandt to 001). After restart, RSA1 gives same error, logical system name changed"
On same sandbox after #2 above I attempted tc: BDLS to see if it would let me assign an exisiting logical system. It did not
QUESTIONS
Will it have any impact on Solution Manager operations to have the "BW Client" on ED0_400 while Solution Manager production is on ED0_001?
Is it possible to change the BW operating client to 001 from 400? (said another way, can I change the current logical systems BW is keyed with to a different, but existing, logical system)
Assuming the answer to Q1 is yes, and the answer to Q2 is no, what steps need to be performed to make BW fulfill the SolMan requirements?

Updated Information - Answer to Question #1.
I am embarrased I missed this section in the master guide the first time around. I will leave the question unanswered in case someone has an easy rememdy to changing the BI client logical system, as I would like to have it in my productive client if possible. However I am relieved I have the option of running it separately in case that can't be done.
There are three major options to consider when planning your system landscape in regards to BI.
BI in the Productive SAP Solution Manager Client
In this scenario, BI is used in the same productive client as SAP Solution Manager. This option allowsfor simpler configuration, and isolates the BI activities conducted for solution life cycle management from the data on a production BI instance. This is SAPu2019s recommendation.
BI in a Separate Client on SAP Solution Manager
In this scenario, BI activities are conducted in a separate client on the SAP Solution Manager system. This scenario provides increased security, as user access is more restricted. However, you must maintain users separately and this increased your administration effort. There is no technical benefit.
BI in a Separate, Non-Productive BI System
In this scenario, the BI activities are conducted in a separate, nonproductive BI system in the landscape. Data is sent to this system from the SAP Solution Manager system via RFC. This is only needed in rare cases for sizing purposes.

SolMan / BW Logical System Issue

Hello all, I am having a SolMan/BW related issue and would really appreciate some advice. I realize some of this is for the BW forums and will cross post (I normally dont)
ENVIRONMENT
New installation of Solution Manager EhP1 (19). System name is ED0. We are running Windows / MS SQL
System is only for Solution Manager ops (client 001), and CUA master (client 950).
BACKGROUND
We want to use full SolMan capabilities. This seems to include some limited BW interaction. We do not use BW in the landscape, so will rely on the "internal" BW in SolMan.
During installation, our person made a new client (000 > 400), set it as default (login/system_client), then ran tc:RSA1 and activated the content. (This sets the client)
Client 400 HAS NOT BEEN USED FOR ANYTHING other than the initial installation, and subsequent activation of BW. It has no connections to other systems, no data, cubes, or anything
PROBLEM
We were NOT AWARE that he had ran RSA1 and activated content, and began using client ED0_001 as our PRODUCTION SolMan client.
We are now unable to run RSA1 in anything but client 400.
We are unable to change the client 001 logical system name because Solution Manager has been built around it.
TROUBLESHOOTING
We changed table RSADMINA / field BWMANDT to 001 from 400. This changed the error from "You can only run in client 400" to "The logical system name has changed" (exit only)
In sandbox I duplicated this problem, then deleted the 400 client (with T000 entry). Changed the login/system_client to 001, RSDAMINA to 001, and ran function module RS_MANDT_UNIQUE_SET (set i_mandt to 001). After restart, RSA1 gives same error, logical system name changed"
On same sandbox after #2 above I attempted tc: BDLS to see if it would let me assign an exisiting logical system. It did not
QUESTIONS
Will it have any impact on Solution Manager operations to have the "BW Client" on ED0_400 while Solution Manager production is on ED0_001?
Is it possible to change the BW operating client to 001 from 400? (said another way, can I change the current logical systems BW is keyed with to a different, but existing, logical system)
Assuming the answer to Q1 is yes, and the answer to Q2 is no, what steps need to be performed to make BW fulfill the SolMan requirements?

Updated Information - Answer to Question #1
I am embarrased I missed this section in the master guide the first time around.
There are three major options to consider when planning your system landscape in regards to BI.
BI in the Productive SAP Solution Manager Client
In this scenario, BI is used in the same productive client as SAP Solution Manager. This option allowsfor simpler configuration, and isolates the BI activities conducted for solution life cycle management from the data on a production BI instance. This is SAPu2019s recommendation.
BI in a Separate Client on SAP Solution Manager
In this scenario, BI activities are conducted in a separate client on the SAP Solution Manager system. This scenario provides increased security, as user access is more restricted. However, you must maintain users separately and this increased your administration effort. There is no technical benefit.
BI in a Separate, Non-Productive BI System
In this scenario, the BI activities are conducted in a separate, nonproductive BI system in the landscape. Data is sent to this system from the SAP Solution Manager system via RFC. This is only needed in rare cases for sizing purposes.
I will leave the question unanswered in case someone has an easy rememdy to changing the BI client logical system, as I would like to have it in my productive client if possible. However I am relieved I have the option of running it separately in case that can't be done.

MEdia disk for Solman 4.0 Sr3 Instalaltion master

Hi Experts,
I want to install Solution manager 4.0 SR2, can any one please suggest me the media i need to download for Solman 4.0 Installation master SR2 (Media disk no). I can find the Solman Sr3 Instalaltion master but i coulld not find the Sr2 Disk.
Please help me with this.

Hello, See ora_sql_results.log
Are you trying to install this solman for a customer ? If yes, then you should go for latest release solman 7.1
Thanks

SolMan 3.1 sapinst throwing floating point exception

I am new to SAP CRM. I am trying to install SolMan 3.1
on Linux/Oracle. I have checked the kernel build of Redhat EL 3.0 and the glibc and seems to be fine on the machine. I also have EP installed on the same box so
the os dependencies should be good to go. While running INSTALL program for SolMan 3.1 installation I get Floating point Exception. Is there anything I am missing ? Is there any SolMan specific kernel to be
patched?
thanks
Sreenu

--> login as the user you use to install SAP
--> type
LD_ASSUME_KERNEL=2.4.21
Export LD_ASSUME_KERNEL
Let me know if the problem is solved.

SAP ME 6.0 Installation. Netweaver 7.3 service pack installation

Hi,
I am making a test installation of a SAP ME 6.0 environment.
I have installed Netweaver 7.3 on my application server, but the problem comes when I should patch
Netweaver 7.3 to required SPS01. According to SAP documents I have to install solution manager.
I know this may not be the appropriate forum for questions about netweaver and solution manager, but I anyway feel that it is related to ME since 6.0 requires Netweaver 7.3.
My questions are:
1) Do I have to install Solution manager to upgrade Netweaver 7.3?
If answer is yes I have follow-up questions:
1a) Do I have to install Solution manager on a separate server or can I use the same app-server as Netweaver 7.3?
1b) What version of SAP Solution manager should I install?
1c) Do I have to create a System Landscape directory (SLD). There is an installation phase regarding this in the
        Solution manager 7.1 installation.
Br,
Johan

Hi Tim,
Thank you for your answer. Not that happy though since it will require me to go ask my manager for more money to purchase a Solution manager server. Anyway I have yet another follow-up question.
1c) How will I get pass the SLD part of SOLMAN 7.1 installation if I have no SLD? At one point in the installation I am
      asked whether a) "Register in existing central SLD" or b) "Configure a local SLD". The B-option seems most logical
      here since I don't have a central SLD, but then it warns me that it will take several hours to create and I come to a screen
      where I am asked to enter information about my local SLD.
Br,
Johan

SolMan 4.0 Installation

Similar Messages

Maybe you are looking for