Installation of Solution Manager

Please understand that I am very new at this so if this question causes a laugh then I do not mind - as long as I get the clarification of where I am going wrong smile.
I need to install solution manager on V5R4. According to the latest on SAP that is version 4.0. However what is available is DB2/400 ASCII.
I want to do a UNICODE installation and as far as I know ASCII is non unicode - is this correct? I also want to be on Netweaver 2005 and not 04 or 04s.

Hello Anette,
I hope the followings would help:
-Like Victor said, IBM has a 4 days training on SAP on iSeries. I took it this Febr. (in the U.S, so I don't know if they offer it in Europe, because there was a student came all the way from Denmark). The material is just a bit out dated, mainly on 6.20/6.40 and not on the 7.0, but the material provides enough info for starter.
- I just finished installing Sol Manager 4.0 on V5R3, and had a post in the forum.
You might search on it for reference. The folks in the forum are great help.
What I had learned was
1. make sure prepare your AS400 per IBM apar for SAP, have all require ***, data, hyper...in place.
2. Next is, for my situation because I am installing with Sol Magr SR1, so I need to patch ISERPACK8, nw04scontrolsr1, which you might not need if you are installing with Sol Mgr Sr2.
3. DO NOT edit/change master password at sumary page. We changed at parameter summary page and this caused problem.
4. if you got stuck with Java phases, install latest SAPJ2EE and DW patch.
5. oh yah, per recommandation, make sure to get the latest IBM JDBC driver from IBM website, I think it's JTOpen level 5.3
Other than that, the installation went very smooth.
I hope the info helps.
Good luck.
Elizabeth.

Similar Messages

Problem during installation of Solution Manager

Hi All,
I am facing problem during the installation of solution manager. it shows following error during installation
ERROR 2010-05-21 14:39:24
FJS-00003 TypeError: this._name has no properties (in script NW_Doublestack_SCS|ind|ind|ind|ind, line 5140: ???)
ERROR 2010-05-21 14:39:25
FCO-00011 The step collect with step key |NW_Doublestack_SCS|ind|ind|ind|ind|0|0|NW_GetSidNoProfiles|ind|ind|ind|ind|1|0|collect was executed with status ERROR .
Please also let me konw how much space do we require for installating the Solution manager as a central system on one drive?

Hi Chandan,
Well may be below SDN thread will help you... out ! try out with Curd Abstoss Response !!
Inst. SAP NW 2004s Java SP9 - Error FJS-00003 this._name has no properties
Hope it will work for you..as well !

Error in Phase Import ABAP by Installation of Solution Manager 4.0

Hello,
i have started Installation of Solution Manager 4.0 (Win,MaxDb).An Error occurred during phase Abap Import. From 18 Jobs only 13 was completed, 5 failed. After retry next 3 jobs was completed, but the last 2 will not completed (i have tried 3 times).
Messages from logs:
import_monitor.log
TRACE: 2007-06-09 15:40:49 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is started.
TRACE: 2007-06-09 15:40:49 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0' import package into database:
D:\usr\sap\SM2\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -nolog -c 0
ERROR: 2007-06-09 19:04:59 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is interrupted with R3load error.
Process 'D:\usr\sap\SM2\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -nolog -c 0' exited with return code 2.
For mode details see 'SAPAPPL0.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
SAPAPPL0.log
(IMP) INFO: import of LISCOMDES completed (0 rows) #20070608172145
(RDI) ERROR: missing attribute description for table "LISDOMAIN" in DB independent control file "E:\install_dvd\export\EXP3\DATA\SAPAPPL0.STR"
(DB) ERROR: DDL statement failed
(ALTER TABLE "LISDOMAIN" ALTER PRIMARY KEY ( "DOMNAM", "STATE" ) )
DbSlExecute: rc = 103
(SQL error -942)
error message returned by DbSl:
(IMP) ERROR: LOCK TABLE failed for table LISDOMAIN
(RDI) ERROR: missing attribute description for table "LISDOMAIN" in DB independent control file "E:\install_dvd\export\EXP3\DATA\SAPAPPL0.STR"
Have anybody any ideas or sugestions?
Regards
Bogdan Rokosa

Hello,
problem solved. After installation stop and system restart, phase ran without errors.
Regards
Bogdan Rokosa

Error in Installation of Solution Manager on Virtualbox centOS

Error in Installation of Solution Manager on Virtualbox centOS .
I tried as per the solution given in the error.
Please go through attachment for error and my /etc/hosts file.

Hi,
I guess you added the entry in /etc/hosts after you got the error.
That being true, stop and start your sapinst again. This will allow you to continue. The information is cached and the only way is to stop and start sapinst.
Cheers,
Amerjit

CPS Installation in Solution Manager 7.01

Hi everyone,
I know the CPS installation documentation states that SAP recommends that you install CPS into it own stand-alone java (nw7) environment, however I was wondering if anyone has installed it directly into their solution manager 7 environment?
Whats the pros and cons?
I'm not a fan of having a dozen various java environments floating around, and given Solution Manager is meant to be the central point for system monitoring and management, why not just install CPS into this environment also??
Cheers
Shaun

Hello,
Yes this is indeed an attractive solution for most administrators that first encounter SAP CPS. However there are some considerations why you want to install SAP CPS on a dedicated server instead.
The main reason is the sharing of resources on the shared box. When you have multiple application running on the same server sooner or later they will be impacted by one another somehow. Either an one of the applications takes most of the resources of the machine making the other application run slow or even worse, maintenance on one of the applications might cause a reboot of the server causing unnecessary downtime for the other applications as well.
This is the main reason you don't want to install SAP CPS on a Solution Manager machine since Solman is most of the time NOT mission critical and has a lot of updates causing downtime on SAP CPS which most of the time IS mission critical (when down NO jobs run in any target system).
This is also the reason why you want to think twice about installing SAP CPS in a portal system, Portal systems are pretty stable but often have peak loads causing performance problems on other applications as well.
Regards Gerben

I got errors while installation of solution manager 4.0 sr2

I faced the errors below while installing Solution Manager 4.0 sr2.
How can I solve these problems?
Thanks.
ERROR 2007-03-13 17:30:12
FSL-00001 System call failed. Error 13 (Permission denied) in execution of system call 'openU' with parameter (/opt/cdler/CD2/IM_HPUX_PARISC/COMMON/INSTALL/JDBCCONNECT.JAR, O_RDONLY), line (368) in file (syuxcfile.cpp).
ERROR 2007-03-13 17:30:12
FSL-02015 Node /opt/cdler/CD2/IM_HPUX_PARISC/COMMON/INSTALL/JDBCCONNECT.JAR does not exist.
ERROR 2007-03-13 17:30:12
MUT-03025 Caught ESyException in Modulecall: ESAPinstException: error text undefined.
ERROR 2007-03-13 17:30:12
FCO-00011 The step copyScripts with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_Unpack|ind|ind|ind|ind|8|0|copyScripts was executed with status ERROR .

Hello Cemil,
The errors you are recieving are most likely user or permissions
related.
Can you please verify that there are 777 permissions on the
installation directories? Also are you installing as User Root?
Are you installing from an NFS Mount or network drive? If so it could be
possible that the user does not have enough permissions on this. If
so I recommend copying the installation files to a local directory and
retrying the installation from there.
Best regards,
Dolores

Installation Sap Solution Manager

Hello,
I have installed a Sap Solution Manager 4.0 SR (Central System Installation), it was my first installation. The OS is a Windows 2003 Server and the Database is 10.2.0.2. After the installation I see in the MMC 2 instances (as shown on the picture) , but I would have expected only one.
Besides I cant Logon with Standard user Sap* .
[http://img185.imageshack.us/my.php?image=ssmpg3.jpg]
Thanks
Carsten

Hi carsten ,
from solman 3.2 onwards they separated enque and message server and put them in central instance.
you need both CI and database instance.
in the logon pad in the user defined tab enter application server as ssm and SID as S12 , system number as 00. hope it will help you to login. use ddic user to login or change the profile parameter to login using sap*.
thanks,
sandeep.

Installation of Solution Manager 7.00 EHP1 on Windows Server 2008

Dear Experts,
We are installing Solution Manager 7.00 EHP1 on Windows Server 2008 Enterprise Edition 6.1 on a 64 bit platform. When running the pre-requisite checker it shows that the OS build 6.1 is not supported. Does anyone know which version of OS WIN 2008 server is supported or whether the Solution Manager can be installed on Build 6.1. Kindly suggest.
Regards,
Rohan

Found this note: [Note 1383873 - Windows Server 2008 R2 Support|https://service.sap.com/sap/support/notes/1383873]...
and also this forum thread: [Is Windows Server 2008 R2 Enterprise Supported]
Hope it is helpful...
Hector Asiain
Map-h

QADB Installation into Solution Manager

Hello, Please help me to find out the QADB for different SAP modules, and please guide me how to install it into the solution manager.
Thanks,
Joby

The portal is a big resource consuming application, SolMan comes with a J2EE engine but this is used for SolMan Diagnostics.
You can install a portal on the system in the same database (using MCOD) or install a second database and use the Netweaver CDs to install it. However, make sure you are using a box, that has enough memory to support all that.
Markus

Installation Problem: Solution Manager 4.0 SR2 on SLES9 MaxDB7.6

Hello altogether,
when performing an Installation of SolMan 4 on SLES9 with MaxDB7.6, it crashes on Phase 40 of 47 with the following hints:
ERROR 2007-04-18 10:31:21
 CJS-30156 SDM deployment failed for at least one of the components to deploy. SOLUTION: Check '/tmp/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS/callSdmViaSapinst.log' for more information.
ERROR 2007-04-18 10:31:21
 FCO-00011 The step redeployForJSPM with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|4|0|redeployForJSPM was executed with status ERROR.
(typed it from screen, maybe there are type-errors).
The "funny" thing about it:
 the file "callSdmViaSapinst.log" is looking just fine:
 Apr 18, 2007 8:31:05 AM Info: Start logging to console
 Apr 18, 2007 8:31:05 AM Info:
 Apr 18, 2007 8:31:05 AM Info: ==============================================
 Apr 18, 2007 8:31:05 AM Info: = Starting to execute command 'jstartup' =
 Apr 18, 2007 8:31:05 AM Info: ==============================================
 Apr 18, 2007 8:31:05 AM Info: Starting SDM - Software Deployment Manager...
 Apr 18, 2007 8:31:05 AM Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0010.20061019070020.0000
 Apr 18, 2007 8:31:06 AM Info: SDM operation mode successfully set to: Integrated
 Apr 18, 2007 8:31:07 AM Info: Initializing Network Manager (50017)
 Apr 18, 2007 8:31:07 AM Info: Checking if another SDM is running on port 50018
 Apr 18, 2007 8:31:07 AM Info: Operationmode for JStartupFramework has already been set to "integrated".
 Apr 18, 2007 8:31:07 AM Info: Successfully executed. Return code: 0
Retrying as well as new Starting do not help.
Will be greatful for any help that solves this special error. Thx in advance.
Greetz,
 Dirk
Message was edited by:
Dirk Malas

..well, I "solved" the issue myself: although not explicit recommended, I switched the corresponding status from "ERROR" to "OK" in the keydb.xml file.
This completed the installation and I am looking forward to consequential damages.. <img src="http://www.cheesebuerger.de/images/smilie/konfus/a025.gif">

Installing the License Key for Solution Manager installation

Hi,
Any Idea how can I get License Key for solution manager installation? Solution manager installation do not requires a key of Solution Manager.
When I want to download a new license file form the SAP market place.SAP I ask for a key of Solution Manager.
Thanks

I guess it is hardware key. Go to the Tcode slicense and there you will be able to find out the active hardware key. Take it!!

Add sap R/3 enterprise system in solution manager SLD

Dear All
Required solution manager configuration documents.
We have DEV QAS and PRD server on SAP mySAP ERP 4.7 ( SAP R/3 Enterprise )
And during the installation of solution manager I select u201CConfigure a Local SLD u201C
Which steps I follows to connect or configure my sap system with solution manager ( SLD ) then I will configure central monitoring, TMS management, Helpdesk etc
Who to Configure SLD Bridge ( in SLD Server ) ?
in which system Run Transaction RZ70 ( In SAP R/3 Enterprise ) ?
and how to Verify that my system is connected and working fine With SLD
Please help me regarding u201C configuration solution manager u201C
Regards
Shahid

Hi
Visit for step by step details of Standard Configuration of Basic Settings
http://service.sap.com/rkt-solman-->SAP Solution Manager 7.0->Technology Consultants & System Administrators->Technical Configuration->just drill out there you can find lot of simulator how to install and configure solution manager
http://www.wilsonmar.com/sap_solution_manager.htm
/people/federico.babelis2/blog/2006/04/14/service-desk-configuration-guide-for-dummies
Regards
Uday

Install ECC 6.0 and Solution Manager on same server Error (MaxDB/Linux)

I have installed Solution manager on one server and then ECC 6 also in the same server with another SID. during the installation it errored out at phase "SLD configuration" with UME error , J2EE_ADMIN locked etc..we checked the user id and noticed it got locked in ECC 6 system and we unlocked it.
But after the ECC installation the solution manager java engine is not coming up error with "com.sap.security.core.ume.service failed" error. Prior to the ECC installation the Solution Manager J2EE was working.
thanks in advance
Mathew

error in the /j2ee/cluster/server0/log/defaultTrace.1.trc
is as follows
#1.5#00137256A483001E0000001700006F190004163784D40864#1150327614343#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_61##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
When I looked at using jcmon the dispacher is up and the server0 and SDM is down

Monitoring of Standalone EP 7.0 system in Solution Manager 7.0

Hi Experts,
I need to configure Solution manager 7.0 for monitoring EP 7.0 (Stand alone ) system.
Can you share documents related to configuration of Solution Manager 7.0 for monitoring EP 7.0 system?
Thanks,
Anit

Hi,
EP Monitoring is done by Solution Manager Diagnostics.
Some Basis steps for ref
1. Definition of EP system thru SMSY in solution manager system
2. SMD agent installation in EP system with CCMS ping cofiguration in both solman and EP system
3. Wily Introscope Enterprise manager installation in solution manager system
3. From SMD wizard, you can configure the list of activities to be monitored for a EP system.
For detailed info check SMD installation guide
Regards
KT

Error importing SP in Solution Manager System (phase XPRA_EXECUTION)

Dear community,
I have a fresh installation of Solution Manager System 7.1 (central system) in a test environment.
During post-installation I wanted to apply SP (user DDIC, client 000), but my update queue via SPAM failed in phase 23 (XPRA_EXECUTION) and I have no idea how to handle that. Error message:
- Error in phase: XPRA_EXECUTION
- Reason for error: TP_STEP_FAILURE
- Return code: 0008
- Error message: OCS Package SAPK-70203INSAPBSFND, tp step R, return code 0008
To check the cause of the error it is recommended to choose Goto -> Log -> Queue.
Choosing Goto -> Action Log, I find:
Error during executing the tp command 'tp XPA ALL SOL ...'
tp return code: '0008' , tp message: 'A tool used by tp produced errors', tp output:
Choosing Goto -> Import Logs -> tp system logs, I find:
START EXECUTION OF REPORTS SOL R      20120104111325              DDIC         biss-labor01
START tp_getprots          SOL R      20120104111325              DDIC         biss-labor01
ERROR SAPK-70203INSAPBSFND SOL R 0008 20120104111331 SAPBSFNDUSER DDIC         biss-labor01
ERROR SAPK-70204INSAPBSFND SOL R 0008 20120104111331 SAPBSFNDUSER DDIC         biss-labor01
ERROR SAPKITL701           SOL R 0008 20120104111335 STUSER       DDIC         biss-labor01
STOP tp_getprots          SOL R      20120104111338              DDIC         biss-labor01
STOP EXECUTION OF REPORTS SOL R      20120104111338              DDIC         biss-labor01
An excerpt (3 lines) from ulog:
APServiceSOL 20120104122229 RFC: tp SHOWPARAMS SOL pf=
biss-labor01sapmnt     rans inTP_DOMAIN_SOL.PFL -Dtransdir=
biss-labor01sapmnt     rans (pid=6232)
APServiceSOL 20120104122229 RFC: tp CONNECT SOL pf=
biss-labor01sapmnt     rans inTP_DOMAIN_SOL.PFL -Dtransdir=
biss-labor01sapmnt     rans (pid=6232)
APServiceSOL 20120104122231 RFC: tp XPA ALL SOL pf=
biss-labor01sapmnt     rans inTP_DOMAIN_SOL.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dbatch_proc=1 tag=spam -Dtransdir=
biss-labor01sapmnt     rans (pid=6232)
What I already tried:
- retry importing
- stop and start the system, then retry importing
- check for background jobs (rdd* ) that failed via transaction SM37, but there are none that have been canceled
- reset buffers via transaction /$sync
Any input, suggestions or help is highly appreciated!
Regards
Sönke

Hi Sönke,
it seems we are making progress at last.
I'm afraid I didn't make my suggestion about splitting items very clear. I meant to say try applying your SPAM queue in several parts splitting up the packages affected so they are applied individually.
SAPK-70203INSAPBSFND
SAPK-70204INSAPBSFND
SAPKITL701
SAPKB70207
I think default behaviour for SPAM/SAINT is to calculate the entire queue automatically based on EPSIN but you can override this behaviour and choose to split your queue into shorter ones, you simply choose carefully the last package, apply this queue, then choose the next queue and so on until you are done. There used to be special notes which had recommended split points for package queues
EDIT: I checked your link and I don't think it is helpful unfortunately.
Best regards,
Mark.
Edited by: Mark Birch on Jan 11, 2012 2:07 PM

Installation of Solution Manager

Similar Messages

Maybe you are looking for