Regarding SMD --for Portal Monitoring

Hi,
Is there any advanced configuration for exclusive portal monitoring usin SMD??
Edited by: kris B on Mar 19, 2008 12:38 PM

>
kris B wrote:
> Hi,
>
> Is there any advanced configuration for exclusive portal monitoring usin SMD??
>
> Edited by: kris B on Mar 19, 2008 12:38 PM
*Is there no such thing as dedicated portal monitoring, or nobody has worked on it??*

Similar Messages

Enterprise portal monitoring

Hi,
We have implemnted EP7.0 , we need to monitor each and every task in Portal.
Is there is document which gives moniroring setup?
- Kristene

Hi Kristene,
For Portal Monitoring there are good blogs.u cn have a look at these....
u can monitor tasks using portal activity reports...
Mysteries of the Portal Activity Report
Mysteries of the Portal Activity Report II
Mysteries of the Portal Activity Report III
In portal u follow these path
System Administration
Monitoring
Portal
Activity Reports
Regards
Bhargava
award points if it helps

Tool for portal server monitoring

hi
'm new to portal administrator. can anyone pls tel how to monitor portal server whether there is any tool for portal server monitoring..
regards
raj

Hi,
there are many tools for monitoring different stuff on portal in different ways, but as you said you are new i would suggest you to go with manual stuff so that more things can be viewed.
please check below links for more details:
http://help.sap.com/saphelp_nwce10/helpdata/en/2e/30e93adccb444b871f3d4e7f905b84/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/7b/86eb3f0c49f106e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/en/5a/84b83b3683094be10000000a11402f/content.htm
/people/daniel.wroblewski/blog/2007/01/02/mysteries-of-the-portal-activity-report
/people/daniel.wroblewski/blog/2007/01/17/mysteries-of-the-portal-activity-report-ii
/people/daniel.wroblewski/blog/2007/01/23/mysteries-of-the-portal-activity-report-iii
Regards,
Pavan
Edited by: Pavan Kumar on Jul 22, 2009 12:38 PM

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

Alert Mail configuration in Solution Manager 7.1 for Portal Runtime errors

Dear Friends,
We have EP7.01 SP5 installed on windows environment with Oracle DB. Also we have SAP EHP 1 for SAP Solution Manager 7.0.
Please help to provide steps to configure
proactive mail alert configuration ,
GRMG for High availability
Any portal runtime errors
for PORTAL services in Solution Manager.
Regards,
Venkat.

Hello Venkat,
You will have to include the Portal system in the Central System administration of your Solution Manager.
As the EP system will be monitored by a sapccmsr running with -j2ee option this one can be configured separately. The agent will be started using the monitoring segment of the J2EE instance and therefore can be started more than once.
Here you should also use the latest sapccmsr agents.
The following link provides details on the required agents:
http://help.sap.com/saphelp_nw2004s/helpdata/en/ca/118110ff542640b7c86b570cc61ae3/frameset.htm
Please refer the below notes.
214247 RZ20: Questions on configuration of monitoring data
704349 Activating the CCMS monitoring for TREX 6.1 (NW2004
Note the EP system can only be monitored by using the SAPCCMSR agents. and then by implement a central autoreaction method you can generate e-mails from CCMS.
Automatic emails will get generated when certain thresholds are met. You must configure the thresholds from the central monitoring system for the nodes that you want email to be generated.
Please follow the steps in the note to configure central auto reaction.
429265 CCMS monitor architecture: Central auto-reaction
In the central monitoring system ( Solution Manager in your case ), Goto RZ20, choose the monitor for the nodes that you are monitoring. Select the node, click properties, & check the threshold values.
Also refer to the following notes:
547024 - Transfer the EP 5.0 Monitoring-Data to SAP CCMS
644783 -P 6.0 Monitoring via CCMS / SolMan
Also, check the following link that has information on portal monitoring :
http://service.sap.com/~sapidb/011000358700002004322004E
I guess this is a whole lot of information to assimilate and will be helpful to you to setup what you intend to.
Regards
Amit

Portal monitoring and alerting - Industry standard

Hi All,
We wanted to put up alert system for Portal. We have the standard set of alerts set which is being taken care by CCMS, also have the solution manager diagnostics set for portal and other systems. What we want is the client side monitoring which could be http response time and if it exceeds the threshold will alert us. Remember the alerting is major criteria here else the monitoring can be performed by diagnostics which we are doing on regular basis.
Is there a indusrty standard available for portal for such alerts? I am currently analysing 2/3 other products for the same. I want to take an advise from you all that what product is being used at your end and what are the benefits over Solman and CCMS.
Please let me know.
Regrdas,
Pankaj

Hello Pankaj
You might want to look into EEM (End-user Experience Monitoring) for SAP Solution Manager which has lots of information available (demo, video) on SAP SDN on the following URL:
[http://wiki.sdn.sap.com/wiki/display/EEM/Home]
In short it enables you to record actions of end-users and then monitor those actions (response times and so on) of what your users normally perform during daily tasks and by doing that getting the technical view on what users are experiencing to be slow.
Kind regards
Tom

Apply Settings for EWA Monitoring missing

Hi all,
we are adding a SAP HANA Technical System on Solution Manager, but we found problems on EWA:
We followed the note http://service.sap.com/sap/support/notes/1542651 for using Early Watch Alerts on HANA Standalone (without Netweaver ABAP) and then followed the note http://service.sap.com/sap/support/notes/1747682 for add an HANA Technical System on Solution Manager.
The fact is that in step 6 of "Managed System Setup" we don't found "Apply Settings for EWA Monitoring":
In attached image you can see only 4 activities instead of five: the follow image is taken from another Solution Manager (SPS10, but SPS7 works the same)
We have SAP HANA 1.0.69 and Solution Manager SPS8.
Why "Apply Settings for EWA Monitoring" is missing? How can i apply this settings?
Best regards,
Roberto

After 19 hours of this problem, it is now resolved on the management portal. There was no mention of it being a problem on the Azure Status page.

"No CEN system configured for CCMS monitoring" message

Hello,
When I want to use the reports option on central mode I receive this message:
"No CEN system configured for CCMS monitoring"
Can someone please guide me through this configuration?
Thank you in advance,
Roy

Hi Roy,
Monitoring Setup Guide will tell you how to setup CEN
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/43f30e51-0a01-0010-f59a-fecea2b95b2c
Regards
Juan
Please reward with points if helpful

Unable to process EWA service session for portal instances

Hi Guru,
I am in process of generating EWA reports for portal ,below are the steps I have completed successfully.
1. SMD agent installation on portal.
2. Defined portal system in SMSY.
3. completed SOLMAN_SETUP.
4. Completed Setup Wizard for managed system.
5. Deploy IS agent via SDM in Solman.
6. Introscope agent setup done for managed system
7. Managed system data is visible in IS Enterprise Manager.
I have created EWA service session for portal but I am unable to process the service session in DSWP ,I have ran SM:EXEC SERVICES job but still I am unable to process the session data.
System Configuratoi: SAP EHP 1 for SAP Solution Manager 7.0 and portal is netweaver 7.0
Thanks
Abullais

Hi,
I have exactly the same problem as this and have performed all the checks as specified but still my Java only NW 7 system shows "Dates for this session are overdue".
My Solman system is Ehp1 SPS 20 and all the managed system setup using the wizard has completed successfully. In Root Cause analysis I can see the data that the extractors have gathered on the J2EE system and in Enterprise Manager I can see the Introscope data also.
The only thing I can think of that may be affecting the EWA session is that after I added the system into the logical component that is part of the Production solution landscape the scheduled EWA session that then appeared for the J2EE system in the list of sessions had a date set for the next scheduled EWA run (29th March). To test the EWA report for my J2EE only system I used the "change date" option after clicking on the J2EE session and set it to 25th March (this changed on 24th March). The session date then reflected the EWA session for the J2EE only system woul run on the 25th.
Checking the session this morning I have the red flag with "Dates for this session are overdue" status.
The sessions for the ABAP based systems are working fine, it's only this one system that is J2EE only that I have a problem with.
Any pointers ?
Regards,
Brian.

Error in Schedule Background Job for Deadline Monitoring of swu3

While Auto Customization swu3 i am getting error message 'Output device "" not known' in 'Schedule Background Job for Deadline Monitoring'
Please advice what could be cause of it

the earlier problem of background job was solved by changing the output device assigned to user wf-batch .
regarding the transport request :
when i was trying to execute the step : "Schedule bakgrd for missed deadlines " MANUEL it was giving me an option of SAVE AND SCHEDULE . which was creating the transport request . but when i executed it automatically it worked fine without asking a request to me ... i don't know why )-: ... probablly we can specify a different interval then the standard of three minutes and which will be transported (it's just a guess) . i have executed it automatically ...
well thanks all for u r help

Help, need to change IP address on host database for Portal

Hi folks,
Rather urgent assistance (as usual) needed. I have an installation working correctly on a pair of Win2k machines, one as the 9i database, one as the 9iAS/Portal. The app server has 2 NIC cards, one with public IP address (which is ok), one on the LAN. I need to reconfigure the LAN addresses on both the machines. Initial Portal install done without DNS, i.e. actual server/host addresses entered in the configuration.
I have tried changing all of the TNS/Listner settings and the NIC card IP addresses and restarting the machines. The likes of SQLPlus work ok, with the TNS connect name allowing over the LAN access into the database with the new LAN addresses. I cannot seem to get the 9iAS/Portal to find the repository with the new addresses.
Can someone help please? I can't find the answer in any documentation or other postings.
Thanks in advance
Rob

There are other modes of operation for the plasst as well. I am listing them below but the formatting will make it difficult to read. If you like I can email it to you.
Bill G...
Configuring Portal when the HTTP server host name of the Infrastructure is changed
Run the following from the $ORACLE_HOME/assistants/opca dir
ptlasst.bat -mode SSOPARTNERCONFIG -i typical -sdad portal -host myApache.domain.com -port 7777 -silent -verbose
NOTE:
(1) This command would create a new Portal partner application in the SSO to reflect the changes of the Infrastructure. Before running this command please ensure to configure the SSO with the correct hostname by running the ssocfg.bat script located in the Infrastructure install (<infra_home>\sso\bin).
The value for -host parameter will be the IP address of the infrastructure server and -port will be the port where the infrastructure http server is running on.
Configuring Portal when the HTTP server host name of the Middle tier is changed
ptlasst.bat -mode MIDTIER -i typical -host myApache.domain.com -port 7777 -ldap_h myOID.domain.com -ldap_p 389 -ldap_w welcome -pwd secret123 -portal_only -oh /home/oracle -chost myHostname.domain.com -cport_i 8001 -cport_a 8000 -wc_i_pwd invalidator -mc false -mi true -silent -verbose
NOTE :
(1) The -host value should match the serverName value of the httpd.conf
(2) The -chost should be updated with the correct webcache hostname. In a default iAS midtier install the -host is same as the -chost.
The value for -host parameter will be the IP address of the midtier(portal) server and -port will be the port where the portal is running on.
Parameter Description Default Value Mandatory
-i install_type Installation Type
In the typical mode, the OPCA would get the Infrastructure information like the Portal schema name, Portal schema password, connect string to the Portal repository, SSO Partner application schema and password, SSO Password store schema and password and connect string to the SSO repository from the Repository Access API's.
In the custom mode, the OPCA would take whatever is passed as the command line arguments.
CUSTOM
-mode mode The different install modes are : PORTAL, SSO, SSOPARTNERCONFIG, LANGUAGE, MIDTIER, ALL, SYSOBJECTS , DEINSTALL
-s portal_schema Oracle Database schema for Portal database objects. In an iAS 9.0.2 install
the default Portal schema name is portal portal
-sp portal_password Password for Portal schema. In an iAS 9.0.2 install the portal schema password is randomized by default. Refer to the note "How to get the Portal schema password of the Infrastructure database ?" for details. <portal_schema>
-c portal_connect Connect string to connect to the Portal repository <hostname>:<port>:<sid>
-p sys_password The Oracle Database password for the Oracle SYS user MANDATORY
-sdad portal_dad DAD for the Portal schema. Create the DAD to the Portal repository through the OEM. Refer to the note "How to create and manage the Portal and SSO DAD ?" for details. <portal_schema>
-host portal_host Hostname of the HTTP server for Portal. This should match byte to byte with whatever is present in the ServerName attribute in the $OH/Apache/Apache/conf/httpd.conf file of the midtier. MANDATORY
-port portal_port Port of the HTTP server for Portal. The Port attribute in the $OH/Apache/Apache/conf/httpd.conf file of the midtier would provide the value. 7777
-ldap_h oid_host_name Host name of the OID server MANDATORY
-ldap_p oid_port_number Port number of the OID server 389
-ldap_d oid_admin_DN Admininstration DN cn=orcladmin
-ldap_w oid_admin_pw Password for DN welcome
-pwd initial_password Initial Password for seeded OID users. In iAS 9.0.2 install this is defaulted to the iAS instance password of the midtier installation. MANDATORY (for ALL or MIDTIER)
-das_public Add Portal Groups to DAS Public Groups. The values could be Y or N. The default is Y. The setting publishes the Portal groups that the user can add to when creating the new user in OID. Y
-u default_tablespace Install Portal objects in this tablespace. The default tablespace selected should have atleast 75 MB of free available space and should have autoextend on. Refer to the note "What are the recommended tablespace size required for Portal installation ?" for details. The default tablespace selected by default is users tablespace. users
-t temporary_tablespace Use this tablespace for temporary objects. The temporary tablespace selected should have atleast 20 MB of free available space and should have autoextend on. Refer to the note "What are the recommended tablespace size required for Portal installation ?" for details. The temporary tablespace selected by default is temp tablespace. temp
-d document_tablespace Install Portal document table in this tablespace. The document tablespace selected should have atleast 4 MB of free available space and should have autoextend on. Refer to the note
"What are the recommended tablespace size required for Portal installation ?" for details. The documented tablespace selected by default is users tablespace. <default_tablespace>
-l logging_tablespace Install Portal logging tables in this tablespace. The Logging tablespace selected should have atleast 4 MB of free available space and should have autoextend on. Refer to the note "What are the recommended tablespace size required for Portal installation ?" for details. The Logging tablespace selected by default is users tablespace. <default_tablespace>
-in index_tablespace Install Portal index in this tablespace. The Index tablespace selected should have atleast 20 MB of free available space and should have autoextend on. Refer to the note "What are the recommended tablespace size required for Portal installation ?" for details. The Index tablespace selected by default is users tablespace. <default_tablespace>
-lang language Abbreviation for the language to install us
-m language_mode Specifies the mode for language installation
if sso, translations only for Login server.
if portal, translations only for Portal.
if -m not specified, translations are installed for Both
-demo Install Portal webview demos
-silent Run mode for Portal Configuration Assistant. There is no UI provided by OPCA in the iAS 9.0.2 install. Use -silent option always
-verbose Log mode for Portal Configuration Assistant. If this parameter is not set, logging information would be in brief and the OPCA would abort the install if it encounters any errors of kind
ORA-, PLS- or SP2 errors.
-report Install reports integration with Portal
-owa Install OWA packages along with Portal This option behaves the same as the SYSOBJECTS mode.
-sso_only Configure only SSO in mid-tier mode
-portal_only Configure only Portal in mid-tier mode
-available Language will be available for user translation
-chost cache_host Cache host for Web Cache <hostname>
-cport_i cache_inv_port Cahe port for Web Cache Invalidation 1100
-cport_a cache_adm_port Cahe port for Web Cache Administration 1000
-wc_i_pwd wc_inv_passwd Web Cache invalidator password invalidator
-wc wc_on_off_flag Web Cache ON/OFF flag to enable or disable WC. The default is ON. If set to OFF Portal would not use Webcache though Web Cache may be up and running. on
-o sso_schema Oracle Database schema for Login Server objects. In an iAS 9.0.2 install the default SSO schema name is orasso orasso
-op sso_password Password for Login Server Schema. In an iAS 9.0.2 install the SSO schema password is randomized by default. Refer to the note "How to get the Portal schema password of the Infrastructure database ?" for more details. Use similar steps to get the password of the orasso. MANDATORY for the following modes:
-MIDTIER: except when '-portal_only' is specified
-LANGUAGE: except when '-m portal' is specified
-DEINSTALL: except when '-drop PORTAL' is specified
-odad sso_dad DAD for Login Server objects. Create the DAD to the SSO repository through the OEM. Refer to the note "How to create and manage the Portal and SSO DAD ?" for details. <sso_schema>
-sso_c sso_connect Connect string to connect to the SSO repository If the Portal and SSO use the same database this option need not be passed and would default to the -c argument. <hostname>:<port>:<sid>
-sso_h sso_host Hostname of the HTTP server for the SSO. If Portal and SSO use the same HTTP server this option need not be passed. It would default the HTTP server used for the Portal.
-sso_p sso_port Port of the HTTP server for the SSO. If Portal and SSO use the same HTTP server this option need not be passed. It would default the HTTP port used for the Portal.
-pa papp_schema SSO Partner Application Registration Schema. In an iAS 9.0.2 install the default Password store schema name is orasso_pa <sso_schema>_PA
-pap papp_password SSO PA Schema Password. In an iAS 9.0.2 install the SSO schema password is randomized by default. Refer to the note "How to get the Portal schema password of the Infrastructure database ?" for more details. Use similar steps to get the password of the orasso_pa <papp_schema>
-ps pstore_schema Password Store Schema. In an iAS 9.0.2 install the default Password store schema name is orasso_ps <sso_schema>_PS
-pp pstore_password Password Store Password. In an iAS 9.0.2 install the SSO schema password is randomized by default. Refer to the note "How to get the Portal schema password of the Infrastructure database ?" for more details. Use similar steps to get the password of the orasso_ps. <ptore_schema>
-pd pstore_dblink Database link from Portal schema to Password store. If the Portal and SSO use the same database this option need not be passed. <portal_schema>_DBLINK
-p_tns pstore_tns TNS connect string to Password Store. If the Portal and SSO use the same database this option need not be passed. The tnsalias should be created in the iAS 9.0.2 Portal middle tier.
-s_tns portal_tns TNS connect string to Portal
-ssotype ssotype SSO install type. Valid values are repository, midtier, all Repository
-ultrasearch Ultrasearch configuration
-drop drop_obj Drops either PORTAL or SSO or ALL (Both)
if PORTAL, drops Portal schema and OID entries.
if SSO,drops Portal schema and OID entries.
if ALL, drops Portal and SSO schema and OID entries
-oh oracle_home Oracle Home
-mi midtier_install Midtier Installation
-mc midtier_config Midtier Configuration
-ssl Use SSL protocol for configuration. Pass this parameter only if SSL configuration is required. If this parameter is passed the -port passed should also be the SSL port of the HTTP server. Bt default this is not passed.
-emhost em_host Enterprise Manager host for monitoring <hostname>
-emport em_port Enterprise Manager port for monitoring 1810
-iasname ias_name Name of the iAS instance that the install is installing on

What are the pros and cons of installing java+abap stack for portal?

Hi all,
1.What are the pros and cons of installing java+abap stack for portal?
2.what effect it does on the ume options to be choosen??
3.for the purpose of integration of r3,bw and crm on portal and crm 4.0 60.2.3 business package which option of stack(java or abap or both)will be good option and which ume option while installation should be choosen?
regards
Rajendra

Hi Rajendra,
The NetWeaver Installation Master Guide offers some good scenarios on the pros and cons:
https://websmp201.sapag.de/~sapidb/011000358700005412792005E.pdf
In a nutshell:
ABAP+JAVA
Pros
- Decrease # of servers required to administer the portal
- Less costly
Cons
- Upgrades could be dependent on ABAP and Java release level
- Additional load on the server due to ABAP stack
- Limited scalability
JAVA and ABAP on separate server
Pros
- Improved performance
- Allows each system to be single-use purpose therefore downtime does not affect other components
- More scalable
Cons
- Adds complexity to landscape
- Additional costs
Regards,
Thomas Pham

Solution Directory -- Create System for Solution Monitoring

Hi Experts,
I created an ERP solution in SolMan but I don´t know how to create systems DEV, QAS and PRD as graphics for process monitoring.
I allready configured in SMSY the systems, RFCs and logical component.
Regards.

Hi,
I would suggest to go through http://service.sap.com/rkt-solman for your Solution Manager release.
It provide complete details regarding benefits and configuring solution manager services including Solutin Monitoring as well.
Hope it helps.
Regards,
Srikishan

Ewa report not good. how to get ewa report to show all server for portal

hi experts
i am using solman sp23 but server for portal not showing all instance
only 1 out of 5 showing on report.
thank u
sunil

Hi Sunil,
Please check that you have run the Managed System Configuration using solman_setup. This step is important, especially if you had just updated your Solution Manager system.
Do you have the correct data in the Workload Analysis?
Regards,
Jared

Solution manager for performance monitoring

Hi,
We have implemented solution manager in our project.Can anyone tell me how is this useful for performance monitoring and how can we check expensive sql statements using this.
It would be helpful if anyone can provide me some documentation on this.
Thanks

Hi
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ce89c290-0201-0010-5985-dd64605111fd
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/media/uuid/3f99cc89-0701-0010-9c86-eae847ae6cd2
refer above threads,
Thanks
Syf

Regarding SMD --for Portal Monitoring

Similar Messages

Maybe you are looking for