Solution Manager upgrade issue on Linux

Hi Alll,
Need your inputs/thoughts on this issue.
We are planning for Solution Manager upgrade from 3.1 to 4.0 and for this the setup and plan is as below:
The production data of the solution manager has been copied as a VMX FILE(VM Player) file on to a test server and we have plans to upgrade that and check and then upgrade on the production system.
The test machine has got a different IP address and hostname. From the test machine when I start the sap instance its affecting the Production machine and dueto which the production will not work until I stop the SAP Instance on the test machine.
It cannot be a IP conflict or hostname conflict as we have them differently on the test machine. But still there is an issue. The IT dept says the issue is with the starting up of the instance and we dont know where to see what exactly is the problem.
I am new to upgradation stuffs, this is my 1st assignment and I am not sure from where to start!!
Can anyone of you tell me where to check for the details?
SOLMAN is installed on a unix machine with oracle 9.2 and we are planning to upgrade it to SOLMAN 7.0
any suggestions on where to look out for the possible issue?

Hi,
I did this a lot and know the side effects a little.
My recipe:
1. Start the copy without network and manage it from the VMWare Console. Change the IP address and make sure all references to the hostname (DNS and /etc/hosts) point to the new one. I hope you're working consistently with hostnames and no IP addresses.
2. Configure the firewall (iptables) on the copied system to block all requests from and to the original production server. If there is any communication with other SAP servers (like monitoring agents, SLD, or others) block this too!
3. Re-enable the network in VMWare.
Alternatively: Can't you simply put this in a VLAN or a real seperated network with just the server and a management workstation?
Hope that helps..
Nikolaus

Similar Messages

Solution Manager Upgrade Issue for "Business Process Monitoring"

Hello,
We had upgrade Solution Manager 7.1 SP08 to SP11.
Earlier our BP Monitories were working fine which are not working now, also we are not able to use function “Load Monitor”.

We are facing below major issues
1. No system in Logical Component
2. No RFC destination found
3. Unable to load Monitors
Also the BPMon configuration is not working post upgrade
Kindly help us to resolve these issues.

Solution Manager Upgrade to EHP1 7.01

Hi
Need some help. Could you please share upgrade doc/exp with me, we are planning for upgrade solution manager from sp17 to sp19.
Stack level 18 or 19 is the part of EHP1 of Solution Manager version 7.01.
What is the process to upgrade the support pack to sp level 19? i have no exp to upgrade to EHP1 level..Any difference ?
Thanks in advance
Amar

Hi Amarjit,
Solution manager upgrade to EHP1 is same like other stack upgrade. You can do it using SAINT/JSPM. But only thing you need is good preparation.
Check upgrade guide on http://service.sap.com/solutionmanager.
Also, check SAP Note 1276895 - Add. info. about Upgrading to SAP Solution Manager 7.0 EHP1 and SAP Note 1169247 - Enhancements to Solution Manager 7.0 EHP1 upgrade
Thanks
Sunny

Solution Manager Upgrade master media not found on download area

Hi All,
We have downloaded solution manager upgrade media from service marketplace. We are performing non-unicode upgrade.
From the download area, we cannot find Upgrade master dvd or media. Media found are:
51031485_1_SOLMAN4_UPGRADE
51031485_2_SOLMAN4_UPGRADE
Please advice.
Many Thanks,
Nischal

I have managed to get prepare going.

Solution Manager ChaRM Issues when Upgrading Satellite System

When upgrading a satellite system that is connected to Solution Manager's Change Request Management, is there anything that we need to be aware of?
Will Change Documents still be able to go to completion (Production status) if we modify the landscape from the time the Change Document is In Development to the time it is moved to Production?
1. Normal Correction (In Development) Development (ECC 5.0) -> Quality (ECC 5.0) -> Production (ECC 5.0)
2. Landscape is changed to Development (ECC 6.0) -> Quality (ECC 6.0) -> Production (ECC 5.0)
3. Normal Correction moved to To Be Tested -> Consolidated -> Production
Will the Normal Correction be in error because the landscape changed for the iBASE?
Are there any other lessons learned that anyone has experienced with Change Request Management or Implementation during and after an upgrade?
Thank You,
Carlen
Edited by: Carlen Yuen on Jan 13, 2009 1:50 AM
Edited by: Carlen Yuen on Jan 13, 2009 1:51 AM

Thanks Subhashini!
We had issues updating the Task List in the past. After we update the landscape and refresh the project and update the Task List, do you foresee any other problems?
Are there any additional items we should look out for? For example, we understand it is a requirement to release all transports prior to beginning the upgrade. However, since the release of the transport locks the change into the cycle for the next production move, this will present a problem if the change is not yet ready to be moved into Production. Do you have any further insight to any additional issues such as this?
Thanks again!
Carlen

Solution Manager Upgrade to SPS25

Hello,
We are preparing to upgrade our current installation of Solution Manager 7.0 to SPS25. Is there anything we need to do with our existing maintenance and implementation projects prior to installing the upgrade?
Thank you for your recommendations.

Hello Cynthia,
Exactly what Release and SP Level is the system now?
Usually upgrades are pretty seemless, its migrations that creates issues.
What I would suggest is you go to http://service.sap.com/instguides
Installation & Upgrade Guides > SAP Components > SAP Solution Manager > Release 7.0 EHP 1
Then click on #5 Upgrade Guides
You will need to locate the upgrade guide for your OS/DB, and then you will have detailed information about the process.
This should help a lot.
Regards,
Paul

Solution Manager upgrade

Hello experts!, I'm doing an upgrade of my current Solution Manager (7.01 linux+db2) to solution Manager 7.1
I created my maintenance transaction and downloaded upgrade files from SMP, but the SOLMANUP process is requesting to me the mount point containing "Export DVD for product CRM/SOLMAN", which one is that?
Hope can you help me
Thanks!

Hi Sirkam,
Besides downloading SP from MOPZ, you do need to download installation export, kernel and language DVD from SMP in order to upgrade solman.
Do download the upgrade guide and media list from SMP for better understanding.
Cheers,
Nicholas Chang

Solution Manager upgrade to enterprise Edition

Dear All,
We are running Solution Manager 4.0 in Win2k3 32 bit server
with Oracle 10.2.0.2 Non Unicode version and ST patch level 11.
The memory of the server is recently increased from 4GB to 12GB.
We do not have any Java Stack.
We have configured EWA / System monitoring in our Solman and
also we have huge (really large) no. of documents uploaded into it.
We want to upgrade our Solman to Solution Manager Enterprise edition.
Can this upgrade from NUC to UC is possible with 32 bit OS platform
or we need to change our OS to 64 bit? If we change our OS to 64 bit,
will it have any impact on our existing application?
Also, is it possible to migrate the system as it is to a HPUX 11.31 box
without loosing any documents?
Kindly provide your views.
Thanks & Regards
Sudip

I strongly recomment to go for 64 bit in any case, 32 Bit is history...
For the migration to 64 bti you need to perform a homogenious system copy (Windows 32 Bit / Windows 64 Bit), if your target platform is HP-UX, then you need to perform a heterogenious system copy, which is more complex. Documents will not be lost during systemcopy operations.
regards
Peter

Solution Manager Upgrade ST-PI and ST-A/PI

System Details:
SAP ERP 6.0 (BASIS 700) / SQL SERVER 2005
Windows
Hi
We are planning to upgrade our ST-PI from 2005_1_700(0006) to 2008_1_700(0000) in our ERP System and BW System.
Similarly we are also planning to upgrade ST-A/PI from 01K_ECC600 to 01L_ECC600.
In the process, I am planning to upgrade SPAM/SAINT as well as R3Trans and tp.
We are planning to implement this in
01) ERP --> DEV, QAS, and PRD.
02) BW --> DEV, QAS and PRD.
Should we also upgrade our Solution manager system. If so, how to find the prerequisities.
Thanking you in anticipation
Best Regards
Raghunahth L

Hi Uday,
Thanks a lot for replying again.
Infact, I had already gone throught the note 781448.
But what really fishy is, using Solution Manager you have to do a lot of work like
downloading latest patches, configuring EWA Alert etc and for everything you need to get connected with SAP Network.
Since ST-A/PI is the core software which plays the communication part with SAP Network,
and Solution Manager is the System playing the key role (as per SAP), but funny thing is
that they have released the latest Patch for all systems except Solution Manager System.
Even though it is being the fact, it is very hard to believe. Anyway thanks a lot for your time and your inputs were reassuring.
Best regards,
Raghunahth L

Solution Manager 4.0 Install Linux : UME phase 34 of 44 fails

I am trying to install Solution Manager 4.0 on Red Hat Enterprise 4 Linux with Oracle 10.2..... I am hung up at phase 34 of 44 of the installation where the UME is being set up...... I am running Java verion 1.4.2_12....
Any help is greatly appreciated....
Main error message is: CJS-30059 J2EE Engine configuration error.<br>DIAGNOSIS: Error when configuring J2EE Engine. See output of logfile umconfigurator.log: '
java.lang.ClassNotFoundException: com.sap.security.tools.UMConfiguratorLoad
     at com.sap.engine.offline.FileClassLoader.findClass
UMConfigurator log file:
java.lang.ClassNotFoundException: com.sap.security.tools.UMConfiguratorLoad
     at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)
     at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)
     at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)
     at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:79)
SAPINST Log file:
INFO 2007-02-28 16:36:14
Working directory changed to /tmp/sapinst_exe.10124.1172709349.
INFO 2007-02-28 16:36:14
Working directory changed to /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS.
INFO 2007-02-28 16:36:14
Working directory changed to /tmp/sapinst_exe.10124.1172709349.
INFO 2007-02-28 16:36:14
Working directory changed to /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS.
INFO 2007-02-28 16:36:15
Working directory changed to /tmp/sapinst_exe.10124.1172709349.
INFO 2007-02-28 16:36:15
Working directory changed to /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS.
INFO 2007-02-28 16:36:16
Working directory changed to /tmp/sapinst_exe.10124.1172709349.
INFO 2007-02-28 16:36:16
Working directory changed to /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS.
INFO 2007-02-28 16:36:17
Copied file '/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/inifile.xml' to '/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/inifile.12.xml'.
INFO 2007-02-28 16:36:17
Copied file '/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/inifile.xml' to '/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/inifile.13.xml'.
INFO 2007-02-28 16:36:32
Copied file '/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/keydb.xml' to '/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/keydb.7.xml'.
INFO 2007-02-28 16:36:32
Execute step runUMConfigurator of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|3|0|NW_UME_Configuration|ind|ind|ind|ind|1|0|NW_UME_Configuration_Doublestack|ind|ind|ind|ind|1|0.
INFO 2007-02-28 16:36:44
Working directory changed to /tmp/sapinst_exe.10124.1172709349.
INFO 2007-02-28 16:36:44
Working directory changed to /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS.
INFO 2007-02-28 16:36:44
Working directory changed to /tmp/sapinst_exe.10124.1172709349.
INFO 2007-02-28 16:36:44
Working directory changed to /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS.
INFO 2007-02-28 16:36:45
Removing file /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/umconfig.properties.
INFO 2007-02-28 16:36:45
Creating file /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/umconfig.properties.
INFO 2007-02-28 16:36:46
Account slnadm already exists.
INFO 2007-02-28 16:36:46
Account 0 already exists.
INFO 2007-02-28 16:36:46
Account 500 already exists.
INFO 2007-02-28 16:36:46
Account sapsys already exists.
INFO 2007-02-28 16:36:46
Effective group id set to 501.
INFO 2007-02-28 16:36:46
Account 0 already exists.
INFO 2007-02-28 16:36:46
Account 501 already exists.
INFO 2007-02-28 16:36:46
Effective group id set to 500.
INFO 2007-02-28 16:36:46
Removed environment variable SSH_AGENT_PID from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable KDE_MULTIHEAD from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable HOSTNAME from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable SHELL from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable TERM from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable HISTSIZE from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable GTK2_RC_FILES from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable GS_LIB from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable GTK_RC_FILES from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable WINDOWID from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable SAPINST_EXEDIR_CD from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable KDE_FULL_SESSION from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable USER from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable LD_LIBRARY_PATH from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable LS_COLORS from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable XCURSOR_SIZE from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable SSH_AUTH_SOCK from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable KDEDIR from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable SESSION_MANAGER from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable KONSOLE_DCOP from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable MAIL from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable DESKTOP_SESSION from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable PATH from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable INPUTRC from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable PWD from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable KONSOLE_DCOP_SESSION from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable JAVA_HOME from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable LANG from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable SAPINST_EXE_DIR from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable GDMSESSION from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable SSH_ASKPASS from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable HOME from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable SHLVL from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable XCURSOR_THEME from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable LOGNAME from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable LESSOPEN from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable DISPLAY from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable G_BROKEN_FILENAMES from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable XAUTHORITY from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable COLORTERM from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable HOSTTYPE from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable VENDOR from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable OSTYPE from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable MACHTYPE from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable GROUP from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable HOST from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable SUPPORTED from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable SAPSYSTEMNAME from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable DIR_LIBRARY from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable THREAD from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable dbms_type from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable dbs_ora_tnsname from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable dbs_ora_schema from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable ORACLE_SID from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable DB_SID from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable ORACLE_BASE from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable TNS_ADMIN from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable ORACLE_HOME from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable NLS_LANG from current process environment.
INFO 2007-02-28 16:36:46
Removed environment variable SAPDATA_HOME from current process environment.
INFO 2007-02-28 16:36:47
Creating file /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/umconfigurator.log.
INFO 2007-02-28 16:36:47
Output of /java/j2sdk1.4.2_12/bin/java -classpath /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/launcher.jar -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.security.tools.UMConfiguratorLoad /usr/sap/SLN/SYS/global/security/lib/tools/iaik_jce.jar:/usr/sap/SLN/SYS/global/security/lib/tools/iaik_jsse.jar:/usr/sap/SLN/SYS/global/security/lib/tools/iaik_smime.jar:/usr/sap/SLN/SYS/global/security/lib/tools/iaik_ssl.jar:/usr/sap/SLN/SYS/global/security/lib/tools/w3c_http.jar:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/lib:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib:/oracle/client/10x_32/instantclient/ojdbc14.jar -u ADMIN_USR=J2EE_ADMIN -u XXXXXX -u ADMIN_GRP=SAP_J2EE_ADMIN -u GUEST_USR=J2EE_GUEST -u GUEST_GRP=SAP_J2EE_GUEST -u ALL_GRP=Everyone -c CLIENT=001 -c COM_USR=SAPJSF -c XXXXXX -c ASHOST=localhost -c SYSNR=$$ -a setup -p abap -f /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/umconfig.properties is written to the logfile umconfigurator.log.
INFO 2007-02-28 16:36:47
Execution of the command "/java/j2sdk1.4.2_12/bin/java -classpath /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib/launcher.jar -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.security.tools.UMConfiguratorLoad /usr/sap/SLN/SYS/global/security/lib/tools/iaik_jce.jar:/usr/sap/SLN/SYS/global/security/lib/tools/iaik_jsse.jar:/usr/sap/SLN/SYS/global/security/lib/tools/iaik_smime.jar:/usr/sap/SLN/SYS/global/security/lib/tools/iaik_ssl.jar:/usr/sap/SLN/SYS/global/security/lib/tools/w3c_http.jar:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/lib:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib:/oracle/client/10x_32/instantclient/ojdbc14.jar -u ADMIN_USR=J2EE_ADMIN -u XXXXXX -u ADMIN_GRP=SAP_J2EE_ADMIN -u GUEST_USR=J2EE_GUEST -u GUEST_GRP=SAP_J2EE_GUEST -u ALL_GRP=Everyone -c CLIENT=001 -c COM_USR=SAPJSF -c XXXXXX -c ASHOST=localhost -c SYSNR=$$ -a setup -p abap -f /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/umconfig.properties" finished with return code 0. Output:
java.lang.ClassNotFoundException: com.sap.security.tools.UMConfiguratorLoad
     at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)
     at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)
     at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)
     at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:79)
ERROR 2007-02-28 16:36:47
CJS-30059 J2EE Engine configuration error.<br>DIAGNOSIS: Error when configuring J2EE Engine. See output of logfile umconfigurator.log: '
java.lang.ClassNotFoundException: com.sap.security.tools.UMConfiguratorLoad
     at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)
     at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)
     at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)
     at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:79)
ERROR 2007-02-28 16:36:47
FCO-00011 The step runUMConfigurator with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|3|0|NW_UME_Configuration|ind|ind|ind|ind|1|0|NW_UME_Configuration_Doublestack|ind|ind|ind|ind|1|0|runUMConfigurator was executed with status ERROR .

Hi Carol,
Check note 716604 to see if you are using the correct JDK version.
The problem seem to be that JVM cannot find a class to load. This class should be
available as part of the contents of
/tmp/sapinst_instdir/NW04S/SYSTEM/XXX/CENTRAL/AS/install/ .
The contents of this directory normally come via unpacking of the
J2EEINSTALL.SAR archive from the <Java DVD>/J2EE_OSINDEP/J2EE-INST
location.
Need to unpack J2EEINSTALL.SAR and copy any missing files into install
directory with correct permissions. Check J2EEINSTALL.log to see what
files were unpacked.
Hope this helps if not let me know.
Best regards,
Dolores

About Solution Manager upgrade from 3.1 to 4.0

Hi colleague,
I am in progress of finalizing a planning for an Upgrade project of Solution Manager from 3.1 to 4.0 release.
The current usage of the Solution Manager usage is the following :
- Only Blue Print and Implementation function used,
- No modification (no repair),
- Very few customizing : document type, key word,
- More than 300 User : BRIDGE Program at Schneider Electric customer that uses Sol Man as implementation enabler and tool is very huge, with many SAP component - ECC, CRM, BW, SRM, EP, APO, XI ; + scope is all SE business organization worldwide,
- We us Template approach (Template Project + Implementation Project per Roll Out),
- DE/EN/FR installed and FR supplemented with EN,
- Landscape is mapped,
- We use Blue Print, business structure, few project administration function, IMG activities linked to Project/Structure, Dev objects linked to Project/Structure, documentation linked to Project/Structure, customizing distribution,
- There are around 6000 documents stored in 2 used Project (one Template, other Implementation).
Current plan is to perform 2 upgrade :
- One on a SandBox Sol Man on which we will have before copied the Sol Man plateform used for project implementation task,
- Another on the Sol Man plateform used (final).
Strategy is in a first step to perform an upgrade without implementation of additional/new Sol Man functions (to see and qualify in a further phase) : iso functionality is the strategy.
Now my concern / question.
I did estimate roughly the upgrade duration and workload to 3 days (only for upgrade, not for preparation, pre-step, post-steps, validation, ...,
I would like to know if such estimation is realistic, and if I have to check and pay attention to particular concern (I already collected all relevant SAP Note like 892412, 914910, 834534, ...).
I expect to have after upgrade the same content, without any bad surprise.
Thanks for your collaboration.
Regards.
Philippe Boyer SAP France (Project Management Team)

Hi,
I guess by now you would have started your upgrade. Sorry for the delay. That's a realistic/achievable estimate, goahead. Any specific queries about upgrade? feel free to revert back.
--Ragu
Downloading and installation of patches would consume more time.
Message was edited by:
Raguraman C

Solution Manager RFC issues

Hi Folks,
We are facing problem with RFC connection from Quality to Solution Manager. It says " No authroization for trusted system" however the RFC connection from Solman to Quality is working fine.
in SMSY -> RFC connection test working fine and able to fetch the qas to solman system. We have give all required authorization including SAP_ALL, SAP_NEW and S_RFC_XX Objects also assigned.
It would be of great help if some one can help us on this.
Regards,
Vinod

Hi
Please check the "Troubleshooting in Trusted/trustng system" part in below link
[http://help.sap.com/saphelp_nw04/helpdata/en/22/042671488911d189490000e829fbbd/content.htm|http://help.sap.com/saphelp_nw04/helpdata/en/22/042671488911d189490000e829fbbd/content.htm]
Hope this help to fix the issue,
Thanks,
Jansi

Solution manager Authorization issue

Dear all,
We are maintaining a enterprise solution manager.
we maintain all our SAP clients issues which is posted in our solution manager.
Now the issue is if the clients login in to our solution manager to see the issue status, they are able to see all the clients issues which is posted.
but we want to restrict the authorization not to see other clients issues which is posted in our solution manager.
we want them to see the issues only which is posted by them.
Please give me if there is set of authorization to do this.
Regards
Prakash

HI,
From ur post, I think u have provided authorization to access the tcode crm_dno_monitor. In that case, u cannot restrict him to see all other messages. If u want to restrict the authorization, create a variant with necessary inputs which shows the result ur customer wants to see and assign that to his favourites. Only provide access to call that variant.
Rajeev.

Solution Manager - Post_installation issue

Hi -
I've finally been able to install Solution Manager 7 w/MaxDB on a Linux box. I am now on the post-install steps where it is asking me to logon to the Application Server. I am assuming I should be able to use Firefox or IE using the URL
http://<hostname_of_J2EE_Engine_Server>:5<Instance_Number>00
How do I figure out what the hostname of the J2EE engine server is?
Should simply be this correct?:
/usr/sap/OSM/DVEBMGS00/SDM/program
[root@atl-osm-01 program]# hostname
atl-osm-01
and my instance number should be 00 right?
However, when I put in http://atl-osm-01:50000 into internet explorer I just get an error message saying that "Internet Explorer cannot display the webpage".
Are there any logs I can look at? Or what is the solution to this? Am I putting wrong info into the URL?

Hello,
Have you set the profile parameter ICM/HOST_NAME_FULL
It needs to have the value of the fully qualified Host name.
This parameter is not set by default, so it needs to be maintained.
You can get more information on setting this parameter in SAP Note 434918.
Are you putting the wrong information into the URL.
What I see is not a Fully Qualified Domian Name
If you look at http://atl-osm-01:50000, all you have specified is the protocol - HTTP://
The Host name " atl-osm-01" and the port 50000
What iis missing is the company and the domain
So it should have the format http://host.company.domain:port
You need to use the fully qualified domain name, and you should also set the Parameter ICM/HOST_NAME_FULL
to the FQDN too, as this will help when accessing Business Server Pages (BSP)
Regards,
Paul

Pre-Steps for Solution Manager Upgrade

Hi Experts,
We are currently planning to upgrade the Solution Manager system from SM7.01 SP25 to SM7.1 SP03.
Can you please let me know the Pre-Steps that we need to consider in Solution Manager before Upgrading.
Awaiting for your response.
Regards,
Satish Dhanalakoti

Hi,
In addtion to the experts' suggestions above, please also check:
http://wiki.sdn.sap.com/wiki/display/SMSETUP/Home -> SolMan 7.1 Section.
Could be of help.
Regards,
Srikishan

Solution Manager upgrade issue on Linux

Similar Messages

Maybe you are looking for