SOLMAN_SETUP transaction

I've just installed Solution Manager 7.0 EhP 1 on a Windows server with MS SQL Server 2005.
The install went fairly smoothly (only a coulple of memory issues), although my practise server does not have a Fully Qualified Domain Namae (FQDM) or a connection to SAP to be able to download correction notes, patches, etc.
My questions is related to traying to set it up, with transaction SOLMAN_SETUP. When I first tried I received the SYSTEM_SHMCONSTR_LOGON_FAILED short dumps. I found note 1318269 that helped me start a web dynpro application that started the shared memory.
But now when I run the transaction SOLMAN_SETUP, I get to a log on screen but it doesn't recognize the user. After 3 tries I get the I get the Error "Client, name, or password is not correct; log on again" message.
I've already logged onto the system (SAP GUI) with this user to run the transaction, so it seems a little funny to me.
Any suggestions on where to look or how to fix this problem?
Ken

Hi Ken, a little late answer, but anyway...
When running the TA= SOLMAN_SETUP You're calling a webdynpro. And as You and others in this thread are aiming at, You need to have FQDN for Your host to be able to run webdynpro's.
You can have a further look into this link at SAP Help: http://help.sap.com/saphelp_tm70/helpdata/en/67/be9442572e1231e10000000a1550b0/content.htm
and also "note 654982 - URL requirements due to Internet standards".
However, You can try a little trick on Your host file by adding a dummy domain like "<solmanserver>.acme.local" and point it to Your Ip-adress. And also adding the FQDN in SAPLOCALHOST, SAPLOCALHOSTFULL and icm/host_name_full in RZ10. Also remember to add it to your own hostfile on the client you're logged on with SAPGUI. It might just solve Your problem. Have a go!
Regards Kurt

Similar Messages

SOLMAN_SETUP transaction not working

Hello Guru,
For 6 weeks I installed the SOLMAN 7.0 EHP 1 and I upgrated it to the latest Package 20.
I also configured everything alone and connected myERP system with the solman system.
I upgraded both systems to the highest level using maintenance optimizer.
Now, I'm wondering how and why should I use the SOLMAN_SETUP.
So, one day I decided to started the transaction but unfortunately I get "500 connection time out" on the SAP Web Application Server.
How can I resolve the issue.
I'm also aware that I need to do this, to get an automactic maintenance certificat from SAP, which will be propagated to all other system without having the need to do it manually.
Thanks for your Respond.
Best Regards,
Kais

The first time you run SOLMAN_SETUP it has to compile all the web dynpros, which takes a lot of time.
In Solution Manager run transaction SMICM and choose Goto -> Services.
Choose the HTTP service and then choose Service -> Change from the menu.
Change the Max Processing Time setting from the current value (default = 60) to 6000 and save.
Then run SOLMAN_SETUP.
When you're done, you can reset the HTTP service timeout, and when your restart the Solution Manager system it will also reset.
Rich

500 Internal server error when running SOLMAN_SETUP

Hi experts,
I'm configuring our solution manager with the SOLMAN_SETUP transaction. In the "initial Configuration", step "j2ee configuration", I click the "Start SLD configuration" button and appears an Internet explorer. After loggin with an administrator user/password, the following error appears:
500 Internal Server Error
SAP NetWeaver Application Server 7.00/Java AS 7.00
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
   java.lang.NullPointerException
    at com.sap.tc.lm.ctc.ccl.wd.TemplateInstallerCompController.getSelectedForSkipActions(TemplateInstallerCompController.java:741)
    at com.sap.tc.lm.ctc.ccl.wd.ScenarioTemplateViewController.actionReexecuteSelectedTemplate(ScenarioTemplateViewController.java:141)
    at com.sap.tc.lm.ctc.ccl.wd.ScenarioTemplateViewController.init(ScenarioTemplateViewController.java:115)
    at com.sap.tc.lm.ctc.ccl.templateinstaller.ScenarioTemplateView.wdDoInit(ScenarioTemplateView.java:106)
    at com.sap.tc.lm.ctc.ccl.templateinstaller.wdp.InternalScenarioTemplateView.wdDoInit(InternalScenarioTemplateView.java:475)
    ... 37 more
See full exception chain for details.
Our solution mananger release is 7.0 EHP1.
Do you have any idea of what the problem is, please?
Thanks and best regards,
Ana

Hi,
The E:\usr\sap\SOL\DVEBMGS00\j2ee\cluster\dispatcher\log\defaultTrace.0.trc last entries are:
#1.5 #000C298948DC001C0000000200000FA80004765AE7A68A56#1256032712398#com.sap.engine.core.configuration##com.sap.engine.core.configuration#######SAPEngine_System_Thread[impl:6]_27##0#0#Error#1#/System/Server#Plain###Exception in ConfigurationChangedListener:
null
=======================================================
java.lang.NullPointerException
+     at com.sap.engine.services.monitor.common.MonitorConfigurationHandler.configurationChanged(MonitorConfigurationHandler.java:1105)+
+     at com.sap.engine.core.configuration.impl.event.PathEventProcessor.sendEvents(PathEventProcessor.java:138)+
+     at com.sap.engine.core.configuration.impl.event.EventProcessor.processEventListeners(EventProcessor.java:121)+
+     at com.sap.engine.core.configuration.impl.event.QueuedEventProcessor.run(QueuedEventProcessor.java:48)+
+     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)+
+     at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:80)+
+     at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:150)+
#1.5 #000C298948DC001F0000001D00000FA80004765B772CB455#1256035120366#com.sap.engine.core.thread.impl6.ThreadManagerImpl##com.sap.engine.core.thread.impl6.ThreadManagerImpl#######Thread[Thread-30,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:6]_ThreadManager:
Thread[SAPEngine_System_Thread[impl:6]_37]
Task: com.sap.engine.core.thread.impl6.ActionObject - Processing Task [classname: com.sap.engine.services.log_configurator.archive.ArchivingThread | toString: [email protected]7a6dd8e1] with classloader [[email protected]2254d@service:log_configurator]#
#1.5 #000C298948DC001F0000001D000003680004765BBE6F6136#1256036315718#com.sap.engine.core.thread.impl6.ThreadManagerImpl##com.sap.engine.core.thread.impl6.ThreadManagerImpl#######Thread[Thread-1738,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:6]_ThreadManager:
Thread[SAPEngine_System_Thread[impl:6]_12]
Task: com.sap.engine.core.thread.impl6.ActionObject - Processing Task [classname: com.sap.engine.services.log_configurator.archive.ArchivingThread | toString: [email protected]3f6a5bcb] with classloader [[email protected]0d8e1@service:log_configurator]#
And the E:\usr\sap\SOL\DVEBMGS00\j2ee\cluster\server0\log\defaultTrace.8.trc entries related to the error message are:
#1.5 #000C298948DC00540000033C00000F1400047684AAF47374#1256212082608#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#SISTEMAS#104##crosol203_SOL_2722150#SISTEMAS#bf43cb51bf0011de8147000c298948dc#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Server/WebRequests#Plain###application [webdynpro/dispatcher] Processing HTTP request to servlet [dispatcher] finished with error.
The error is: java.lang.NullPointerException: null
Exception id: [000C298948DC00540000033A00000F1400047684AAF47077]#
Thanks and best regards,
Ana Abad

SOLMAN_SETUP - managed system configuration

I am attempting to use the SOLMAN_SETUP transaction to establish the managed system connections to my ABAP ECC systems. I enter the required user/password info and execute it. I get one error message in the log that says "Cannot get fully qualified name of the server as400q3". The as400Q3 server is the host where the managed system resides. I do not know where to fix this issue.
Best regards,
Russ

Hi ,
You have to mention it in Txn. SMSY- Server->as400q3->Fully qualified host name.
Also, Please make sure the host file entries are maintained correclty on your solman server.
Hope this helps.
Kindly revert if you face any issues.
Thanks,
Jagan

SOLMAN_SETUP tcode error

Hi experts,
I am new to the basis, I want to configure basic configuration settings in Solution Manager.Already i created HTTP connection to Solman. When i tried the SOLMAN_SETUP transaction code, It is not getting open.Please help in this.Thanks in advance.
Regards,
Patan Thavaheer.

Hi Patan,
Have you maintained the IP address in /etc/hosts as <IP address of Solman System> <Hostname> <fully qualified domain name>.
Also check and add the following profile parameters
login/create_ss02_ticket=2
login/accept_ss02_ticket=1
icm/host_name_full = fully qualified server name
icm/server_port_1 = PROT=SMTP,PORT= <> 0
icm/server_port_0 =PROT=HTTP,PORT=5$(SAPSYSTEM)00,TIMEOUT=60,PROCTIMEOUT=800
Regards,
Anitha

Solman_setup is not working

hi Gurus,
Solman_setup tcode is not working. I have set the below parameters.
login/create_sso2_ticket = 2
login/accept_sso2_ticket = 1
icm/host_name_full = host name
icm/server_port_1 = PROT=SMTP,PORT = 25$$0
login/no_automatic_user_sapstar = 0
icm/conn_timeout = 20000
icm/keep_alive_timeout = 240
SAPLOCALHOSTFULL = host name
The error is like this
500 Connection timed out
Error: -5
Version: 7000
Component: ICM
Date/Time: Sat Aug 14 12:04:38 2010
Module: icxxthr.c
Line: 2698
Server: chnmct211397d_SM2_02
Error Tag: {-}
Detail: Connection to partner timed out after 240s
please help me

Hi Lata,
I hope u haven't executed the SAP Load generator(SGEN) even once. Actually what happens in ur case is that, the system tries to load the SolMan_Setup transaction in a web browser and it is not able to load that within 240s as mentioned in the parameter icm/keep_alive_timeout. So the session gets terminated(timed out).
icm/keep_alive_timeout = 240
Increase the value of this parameter using the tcode RZ10 (In our case I've set this as 600) and restart the SAP instance once and then try to execute the tcode solman_setup once again.
Also make sure that the value of the following are FQHN (hostname.domain).
icm/host_name_full = host name
SAPLOCALHOSTFULL = host name
Regards,
Varadharajan M

Issue in ruuning the SOLMAN_SETUP

Hello,
We have solution manager 7.0 EHP1 with SP23 in our landscape which is newly installed
When i run the Tcode solman_setup it tries to open the webpage and it fails
It doesnt give any error message also.
Please let me know if you need more info to troubleshoot this issue.
Appreciate your quick response
Thanks & Regards,
Vadi

>
Vadivambal Paramasivam wrote:
> Hello,
>
>
> We have solution manager 7.0 EHP1 with SP23 in our landscape which is newly installed
> When i run the Tcode solman_setup it tries to open the webpage and it fails
> It doesnt give any error message also.
> Please let me know if you need more info to troubleshoot this issue.
> Appreciate your quick response
>
> Thanks & Regards,
> Vadi
Dear Vadi,
Can you please check with your network administrator if you can access the URL, because you maybe using proxy which stop you from doing so.
If this is not the case then the best solution is as follows:
Can you try executing the HTTP services within IMG Activity(via TRX 'SPRO' -> SAP Referance IMG ->
SAP Solution Manager -> Basic Settings - HTTP Services). The documentation is available as well in IMG.
Once this step is done try the Solman_setup transaction and it should work.
Regards
Amit

SOLMAN_SETUP - missing view

Hi all,
i just upgraded my SM from 7.0 to 7.1 SP11 (MSSQL 2012).
After the post activities i started the SOLMAN_SETUP transaction in order to execute the initial and basic configuration and as you can see the central view is missing.
The same thing happens to every other step.
Tried with IE, Firefox and Chrome. Same behaviour.
Looking for notes without any success.
Any clue?
Regards.

Hi,
solved!
Found SAP Note 2002333 and 1972327.
Let me explain. The first note is related to a dump in CL_SISE_SCOPE_ACCESS==========CP program, not exactly my problem.
I have the same dump in ST22 (occurred during switching between SOLMAN_SETUP steps) but related to another program (/1BCWDY/0O2TR6GL1KI9XCB5HA24==CP).
Don't ask me the relationship with my problem but after note 1972327 has been applied the view missing problem is solved!
Regards.

Error while scheduling data collector: Error adding routine 'SAPTOOLS.DBH_FWK_CLEANUP' to task scheduler

Error Detail
Exception CX_DBA_ADBC in program RAGS_SISE_ACTIVITY_JOB line 0
Kernel Error ID:
WP ID: 23
WP PID: 28977
SYSID: CR5
SY-SUBRC: 0
SQL statement:
Database: CR5
caused by
Exception CX_SQL_EXCEPTION in class CL_SQL_STATEMENT
Kernel Error ID:
DB Error: Yes
SQL Code: 444-
SQL Message: SQL0444N Routine "*TASK_ADD" (specific name "SQL140704080729140") is implemented with code in library or path "...ib/function/SYSPROC.ADMIN_TASK_ADD", function "*" which cannot be accessed. Reason code: "4". SQLSTATE=42724 row=1
DB Object Exists: No
Duplicated Key: No
Internal Error: 1
Invalid Cursor: No
Unknown Connection: No
Connection Closed: No
System Detail:
Solman 7.1
ST    710    0010    SAPKITL710    SAP Solution Manager Tool
SAP_BASIS    702    0013    SAPKB70213    SAP Basis Component
Managed system:
SAP CRM ABAP 7.0
SAP_BASIS    701    0005    SAPKB70105    SAP Basis Component
SAP_ABA    701    0005    SAPKA70105    Cross-Application Component
PI_BASIS    701    0005    SAPK-70105INPIBASIS    Basis Plug-In
ST-PI    2008_1_700    0008    SAPKITLRD8    SAP Solution Tools Plug-In
CRMLOY    700    0005    SAPK-70005INCRMLOY    CRM Loyalty Management 700
SAP_BS_FND    701    0005    SAPK-70105INSAPBSFND    SAP Business Suite Foundation
SAP_BW    701    0005    SAPKW70105    SAP Business Warehouse
LCAPPS    2005_700    0007    SAPKIBHD07    LC Applications (LCAPPS) 2005_700
Database DB2
db2level
DB21085I Instance "db2cr5" uses "64" bits and DB2 code release "SQL09016" with
level identifier "01070107".
Informational tokens are "DB2 v9.1.0.6", "s081007", "U817474", and Fix Pack
"6".
Activity detail:
We are performing managed system configuration for CRM into Solman by using solman_setup transaction. While performing the Database Extractor Setup in step 8 we have observed above error.
Action take at our end:
1. Clean the LMDB and restart the configuration. - no luck
2. Upgrade the hostagent at CRM - No luck
3. Update the SLD for CRM entry - no luck
4. implemented SAP notes:
875986    Note Assistant: Important notes for SAP_BASIS up to 702
1246964    Note Assistant: Master language of notes incorrect
1262653    SPAU: New object is deleted after note is reset
1309424    DB6: DBA Cockpit Correction Collection SAP Basis 7.01 / 7.11
1335017    DB6:"Remove Redundant Restrictions" can return wrong results
1349277    Note Assistant: Method cannot be implemented
1365677    Note Assistant: Runtime error MOVE_CAST_ERROR during implmtn
1372652    DB6: Short dump when viewing diaglog due to NULL bytes
1373957    DB6: CX_SY_CONVERSION_OVERFLOW in new EXPLAIN
1376543    DB6: OPTIONS parameters for backup jobs in DB13
1378499    DB6: CLI error CLI0112E with "REORGCK_ALL" job
1379260    DB6: Add BW query name as comment to SQL statements
1379346    DB6: Scheduling of data collectors fails
1381179    DB6: Incorrect values for 'number of objects in tablespace'
1382634    DB6: Unable to create view 'SAPTOOLS.DBH_TABCLASS'
1382996    DB6: Update of DPW Back-End in Monitored DBs does not work
1384238    DB6: Defect scheduler on DB2 9.1 FP7/FP8 for LUW on Linux
1387022    DBA Cockpit: Month displayed incorrectly in DB13C
1387297    DB6: SQL-Fehler 901 during RUNSTATS and REORGCHK
1397709    Ignore Dynpro element fields AGLT and ADEZ in SNOTE/CWB
1398258    DB6: Job REORGCK_ALL places load on package cache
1400843    DB6: Incorrect display of key fields in EXPLAIN
1412719    SNOTE: error when implementing enhancement implementations
1413008    DB6: SQL0206N in function module DB6_PM_LOCKSNAP
1414624    DB6: Performance views if database monitors are deactivated
1414626    DB6: Incorrect display of file system sizes of containers
1415680    Note Assistant: Incorrect status in subsequent systems
1421157    DB6: SQL error 204 when accessing table DBSTATC
1425487    SE24: Error regarding READ-ONLY for complex attributes
1426092    DB6: Incorrect DROPPED TABLE clause for tablespaces
1426480    DB2: Incorrect display of registry values for DPF systems
1427030    DB6: Container specifications for tablespaces not changeable
1429082    DB6: No REORG after deactivating compression
1429687    DB6: SQL cache performance
1438168    DB6: REORGCHK recommendations for indexes are missing
1444373    DB6: Loading the package cache with monitor functions
1449482    DB6: Error message 'Command LIST_DB2DUMP failed'
1451958    DBA Cockpit: Incorrect start time for jobs
1452197    DB6: SQL error 100 in job REORGCK_ALL
1452502    DBA Cockpit: Jobs are missing in central planning calendar
1455897    DB6: Display of data classes is not updated
1456379    DB6: No display of indexes in data classes
1460895    DB6: SQL0104N during creation of WLM threshold
1462415    DB6: SQL -444 error messages in system log
1462855    DB6: Incorrect database name in HA environment
1464800    DB6: SQL Commands executes automatically on system change
1464858    DB6: COMPUTE_BCD_OVERFLOW during EXPLAIN Test Execute
1469515    DB6: Runtime error GETWA_NOT_ASSIGNED_RANGE in SAPLSDB6MON
1485313    DBA Cockpit: Incomplete system entries after SLD import
1486972    DB6: Parameters for DB/DBM configuration cannot be changed
1489968    DBA: DBA Cockpit WebDynpro does not care about HTTPURLLOC
1496515    DB6: SQL error 1428N when starting the DBA Cockpit
1501130    DB6: SQL error 802 in DB6_DIAG_COUNT_TABLE_ENTRIES
1508074    RZ20: 'Connection' attribute does not report alerts
1509121    DBA Cockpit: Endless loop occurs when starting DBA Cockpit
1511803    DB6: DB_TABLE_DATA_READ does not return data
1521525    DB6: Table display is not sorted
1522617    DB6: Availability of BW-specific functions in DBA Cockpit
1532114    DB6: Too many locks when collecting table history
1536787    DBA Cockpit: WebDynpro Explain - LOADDATA requires a model
1542311    DB6: Runtime error BCD_OVERFLOW in auto maintenance display
1546866    DB6: Runstats_DBSTATC interprets runtime param. incorrectly
1551729    DB6: Incorrect number of key fields in EXPLAIN
1552812    DB6: Use of db2sap functions
1559699    DB6: Missing data in SQL cache display
1559967    DB6: SQL error 206 when collecting the table history
1563327    DB6: SQL error SQL0551N when accessing SYSSTAT.TABLES
1568800    DB6: Error when deleting alert messages
1569592    DB6: SQL error SQL0433N in EXPLAIN
1569669    DB6: Incomplete history for performance data
1571365    DB6: SQL error SQL0443N in alert monitoring of DPF system
1576094    DB6: Database error SQL1751N in partitioning wizard
1597281    DB6: Incorrect compression displays for tables
1599764    DB6: SQL error 1428 when calling transaction SM50
1602403    DB6: No VOLATILE attribute after RUNSTATS or REORG job
1613270    DB6: Runtime error DYNPRO_FIELD_CONVERSION in DBA cockpit
1615698    DBA Cockpit: Incorrect date selection in DB13C
1619084    DBA Cockpit: Runtime err MESSAGE_TYPE_X when alert displayed
1619636    DBA Cockpit: Daily scheduling is not deleted
1624436    DBA Cockpit: Errors when accessing SHM area CL_DBA_SHM_AREA
1639631    DBA Cockpit: Failed schedulings in DB13
1720495    Invalid deimplementation of obsolete notes by Snote tool
Kindly suggest the correct solution to fix the issue.

Dear Deepak
Thanks for quick response.
Note 1462415 - DB6: SQL -444 error messages in system log ( SAP_BW 701 SP7 suggested)
This is already implemented and updated in my 1st message.
Note 978319 - DB6: Incorrectly cataloged table functions
This note can not be implemented due to version issue.
Kindly suggest some more hints on top of what I already did.
Regards
Bipin

Solution Manager Diagnostics don't display data

Hi,
I'm setting up Solution Manager Diagnostics at Solution Manager SP 22. I've installed Wily Introscope Enterpise Manager at Solution Manager Server, and Wily Introscope Agents at Solution Manager and Satellite systems as well.
Wily Introscope is working properly, I receive statistics from all agents, and also I can see most of the graphics. BUT, after I install SMD Agent, I can't receive any data in Root Cause Analysis Workcenter -> End-To-End Analysis -> system -> Workload Analysis.
Here I can see a plot with all values at 0. If I try Enterprise Portal tab -> Portal Activity Reporting, I don't have any data.
At Aplication Server Java tab -> J2EE Engine, I only can see forms like:
     E2E CV PPMS ID Variable
     E2E Installation Number Variable
     E2E SID Variable       <SID>         <SID>
     E2E Metric Type Variable(multiple values)
               SERVLETS
               WEB DYNPRO APPLICATI ONS
               JCO CALLS
              SQL STATEMENTS
InfoProvider
              0SMD_PE2H
              0SMD_PERH
But if I execute or check this form, I receive this message:
Value "SERVLETS" for variable "E2E Metric Type Variable(multiple values)" is invalid.
I've also followed SAPNote 1435043 - E2E Workload Analysis - No applicable data found, and checked prerequisites, RFC's, Jobs, Extractors and executed SOLMAN_SETUP transaction.
I've followed all guides I've found for Diagnostics, but I don't know how can I solve this.
Please, could you help me?
Thanks in advance and regards.
Tomas.

Hi Tomas,
I have exactly the same problem, I am on Solman SPS22, LMSERVICE SP06 patch2.
and the satellite system pre-requisites and definition in SMSY are correct, also the MDX PARSER RFC is wrking fine.
any idea on why is the Portal activity reporing is blank, while i get data under all the other tabs.
Also, the agent application .log file shows the below warning
"PadcService@1cbd1cbd: file portalActivity_6057051_1278074505498.txt could not be deleted"
but i could not find the file in the satellite system.
Regards,
kaustubh.
Edited by: Kaustubh Krishna on Jul 12, 2010 11:21 AM

Step E2E RFC Details

Dear Experts,
I am configuring the managed system on SOLMAN_SETUP transaction and in the step - Configure Diagnostics, I got this error message:
The definition of the READ RFC to the managed system could not be found. Please make sure to run the RFC creation assistant in SMSY, as described in setup documentation
!! Exception : CANNOT_GET_RFC_DEST
I have already checked the RFC_READ user roles and it has SAP_SATELLITE_E2E(role)/S_AI_SMD_E2E (Profile).
Have you guys ever faced that?
Regards,
Má

Hi Má,
Make sure that you have performed the step 1 of the managed system configuration or create the RFC in the transaction SMSY with the RFC Wizard.
To ensure that the READ RFC exists, go to the transaction SM59 and check if you can find the following RFC under the ABAP connections:
- SM__READ
SID - Is the system ID of the managed system
client_number - Is the client number of the maanged system
I hope this helps.
BR,
Allam

How to create a new solution for portals?

Hi all,
In order to makde goinglive sesions for portals, I´ve updated SAP Solution Manager (SSM) to 7.0 EHP1-SP19.
Portals have two servers:
- Win 2003 for main application (NETWEAVER 7.0 2004s)
- HPUX 11.23 for database (Oracle 10.2.0.2.0)
I haven´t worked with solution manager until this update, and of course, I haven´t configured before.
I´ve a mix of terms, possible configurations:
- run SOLMAN_SETUP transaction after update ¿?
- install SMD ¿?
- install/configure SLD (we haven´t configured) ¿?
- create new solution, system components, logical components,...
I´ve tried to create a server, database, system, but I don´t know what is the right procedure.
I´ve seen that there is a transaction called "SOLMAN_SETUP" that I suppose I´ve have to run to configure the new version, but the EWAs configured before de update, runs properly.
Do you know the steps as more detailed as possbible to create the new solution for portals after update?
Does any of this steps/procedure impact into our configured and running EWAs and Goinglive sesions?
Thanks in advance.
Best Regards
Chema
Edited by: tsunix on Mar 29, 2010 9:26 AM

Hello,
Are you trying to get the EWA working for Go-Live check or Solution Manager? Based on my understanding you are trying to get your Solution Manager setup to be able to generate these reports. However, I will provide notes for both incase I am misunderstanding you.
Please review the following notes for getting your system prepared for Go Live checks:
207223    SAP EarlyWatch Alert processed at SAP
1095227 FAQ: SAP Hosting - Early Watch Alerts
207223    SAP EarlyWatch Alert processed at SAP
Also, you can visit http://service.sap.com/earlywatch for more help/documentation on this.
If you are trying to setup your EarlyWatch on your Solution Manager system, then please visit the following URL:
http://service.sap.com/ewa
You may also want to visit this note to see if it helps.
1257308   FAQ: Using EarlyWatch Alert
Thanks,
Mark

Http wrong client redirect

Hello guys,
i´m facing a problem when i start solman_setup transaction in client 001.
it opens a new windows but everytime with client 100 by default(as you can see in pictures bellow), well i don't have client 100 on my machine, but i suppose that happens because a configuration error, i already searched for this error but i'm not finding where can i correct this, and have 001 as default in client.
can you help?
Thanks
Oscar

Hello Oscar,
Check the link that is being fired up when you execute solman_setup transaction.
locate that service in your ABAP stack in SICF, check logon data section and see if there is any hard coding of client.
I don't have a recent version of solman with me so don't know which service is being called at your end for comparison.
Good luck
Regards,
Siddhesh

CUPOSS = EWA not available

Hi,
Last week I have received mail from SAP stating that update RFC's and 2000132 note was mentioned.
As per note I have update some of RFC's but few RFC's were not available in my systems.
CUPOSS => EWA
OSSNOTE => 1_PUBLIC
SAP-OSS => 1_PUBLIC
SAP-OSS-LIST => 1_PUBLIC
SM_SP_<customer number> => 1_PUBLIC
Is above RFC's are compulsorily? Should be there in our environment?
If yes
Kindly help us creating above RFC.
Best Regards
Satya

Hi Satyanarayana,
1.-
SM_SP_<customer number> are for ISV and VAR scenario, you don't need to create it if you don't need, to check it user transaction SM_CONFIG_RFC.
2.-
SAP-OSS-LIST is created on solman_setup transaction, that is used to sync messages/incident between SAP and Solution Manager service desk/ITSM. you can create it on IMG: "SAP Solution Manager" -> "Basic Settings" -> "Connection to SAP" and:
solman_setup -> IT Service Management -> check prerequisites -> Check Connection To SAP Backbone.
Regards,

RABAX_STATE error in SOLMAN_SETUP step 6.6

Hi all,
I'm doing the Solman_setup, step "System Preparation" for a new Solution Manager 7.1 sp 14.
As I try to get into the task 6.6 "Connect Diagnostics" the system generates a short dump :
Category               ABAP Programming Error
Runtime Errors         MESSAGE_TYPE_UNKNOWN
ABAP Program           CL_WDR_MESSAGE_MANAGER========CP
Application Component BC-WD-ABA-RUN
Date and Time          20.06.2014 11:26:31
|Short text                                                                                        |
|    Message type "e" is unknown.                                                                  |
|What happened?                                                                                    |
|    Error in the ABAP Application Program                                                         |
|                                                                                                  |
|    The current ABAP program "CL_WDR_MESSAGE_MANAGER========CP" had to be                         |
|     terminated because it has                                                                    |
|    come across a statement that unfortunately cannot be executed.                                |
|What can you do?                                                                                  |
|    Note down which actions and inputs caused the error.                                          |
|                                                                                                  |
|                                                                                                  |
|    To process the problem further, contact you SAP system                                        |
|    administrator.                                                                                |
|                                                                                                  |
|    Using Transaction ST22 for ABAP Dump Analysis, you can look                                   |
|    at and manage termination messages, and you can also                                          |
|    keep them for a long time.                                                                    |
|Error analysis                                                                                    |
|    Only message types A, E, I, W, S, and X are allowed.                                          |
|    There is probably an error in the program                                                     |
|    "CL_WDR_MESSAGE_MANAGER========CP".
All the previous tasks were performed successfully.
It seems to be a program error, but I can't find any Oss Note for it.
Any advise ?
regards

Hi,
Please check the below link
http://www.saptechies.org/system-preparation-short-dump-step-66-connect-diagnostics/
Resyncronize the Solution Manager system with the SLD in the LMDB.
Execute the steps below for the Solution Manager ABAP and JAVA:
Go to the Managed System Configuration
Select the Solution Manager system
Select System Operations -> Maintain System
A new screen will open, select the option Advanced -> Resynchronize the System from SLD, as seen in the example below
Rg,
Karthik

SOLMAN_SETUP transaction

Similar Messages

Maybe you are looking for