Alert Connector Exception in uwl

Hi,
I get an error as while i clink on alert in uwl:-
(connector) : com.sap.mw.jco$Exception: Name or password incorrect(repeat login).
Any inputs?
Regards,
Anirban.

check whether all JCO connections and systems are working fine

Similar Messages

  • Enabling SCOM Alert Connector in SCSM

    Hi,
    Had a query regarding the Alert Connector in SCOM that forwards alerts in SCOM to SCSM (Service Manager) to create incidents.
    Currently, we had SCOM and SCSM at the same level i.e 2012 SP1. But, in future we might have to upgrade to R2 so is there any compatibility matrix for the SCOM and SCSM versions for the Alert Connector. Like if we had SCOM on Sp1 and SCSM on R2 would it
    affect or the vice-a-versa.
    Regards,
    Daya Ram

    Hi,           
    System Center 2012 – Operations Manager is supported by Service Manager and Service Manager SP1 for connectors and agents. However, only corresponding System Center versions are supported when you register a data source in the Data Warehouse
    workspace.
    System Center 2012 – Operations Manager agents were not supported with System Center 2012 – Service Manager. However, the agent that is automatically installed by System Center 2012 – Service Manager
    SP1 is compatible with System Center 2012 – Operations Manager and System Center 2012 – Operations Manager SP1. 
    More details:
    Operations Manager Considerations in System Center 2012 - Service Manager
    http://technet.microsoft.com/en-us/library/hh524312.aspx
    Regards,
    Yan Li
    Regards, Yan Li

  • SCOM Alerts Connector run as failed

    Hi
    I have setup the SCOM alerts connector in SCSM but after that i starts to get wernings in scom on servers there are in a difrent domain. 
    werning: 
    Description:
    The Health Service cannot verify the future validity of the RunAs account Domain1\SCOMAlertsConnectorUser for management group SCOMMG01. The error is Logon failure: the user has not been granted the requested
    logon type at this computer.(1385L). 
    SCSM and scom is in domain1
    the servers i got the werning on is in Domain2
    what can i do to fix this?

    The connectors runas account must be administrator in SCOM (as I recall). Is that the case for Domain2?
    Cheers,
    Anders Spælling
    Senior Consultant
    Blog:  
    Twitter:   LinkedIn:
    Please remember to 'Propose as answer' if you find a reply helpful

  • Error adding a SCOM Alert Connector

    I have a SCOM 2012 SP1 and SCSM 2012 SP1 environment in production. I have had a working CI connector for some time, but we decided to try to add an alert connector to the mix.
    At the point where I provide credentials for SCOM I get the following warning 
    "Found at least one other alert connector in Operations Manager. Alerts may not be routed as expected if multiple connectors subscribe to the same alert."
    Hmm. That's interesting because there are no other alert connectors. 
    I checked the SCOM side for any alert connectors and any configured subscriptions on the internal connectors and came up blank.
    I then ran the following queries on the SCOM and SCSM databases: 
    select DisplayName,IsInitialized,ConnectorID from Connector,BaseManagedEntity
    where Connector.BaseManagedEntityID=BaseManagedEntity.BaseManagedEntityID
    Neither shows an alert connector in place.
    I pressed on and created the connector. I then added my subscriptions to the SCOM side. 
    I can see my Connector run every 30 seconds, but it never retrieves any alerts. 
    The state never flips to initialized on the connector either. 
    I have removed and recreated the connector and always see the same error. 
    Aside from checking SCOM and the connector tables in the operational databases, where else can I look for this mysterious other alert connector?
    Thanks,
    Joe

    Dear Joe,
    hope these links will help you:
    http://social.technet.microsoft.com/Forums/systemcenter/en-US/3075bbb7-59db-4671-994d-7540871a2a23/scom-connector-to-multiple-service-manager-environments?forum=connectors
    http://www.thecloudbuilderblog.com/blog/2012/6/2/scsm-2012-connector-bugndashincidents-generated-from-rule-ba.html
    Regards
    Jreij12

  • Issue with SCSM to SCOM Alert Connector when AOI is Connected?

    Hello Azure Operational Insights forum,
    I'm trying to connect my Server Manager (SCSM) instance to my Operations Manager (SCOM) instance.  However, I get this warning message when I create the connection:
    "Found at least one other alert connector in Operations Manager.  Alerts may not be routed as expected if multiple connectors subscribe to the same alert."
    There "was" a connector previously, but I followed Kevin Holman's blog to remove it.  Now everything looks okay (at least as far as I can tell).
    At this point, I wonder if the System Center Advisor (now renamed Azure Operational Insights) connector is cause the warning message I listed above when setting up an Alert Connector in SCSM?  It's the only "Alert Connector" in the list.
    Has anyone else had this issue?

    I have also found this warning message. In my case, this is a new connector to a new SCOM Mgt group. the management group in SCOM is connected to AOI.
    Repo:
    1. Install new OM
    2. Configure AOI connection
    3. Create SCSM OM Alert Connector
    Warn appears after entering SCOM Server details and run as account and continues until Connector is created
    The warning does not appear to affect the operation of the connector based on initial tests performed.

  • SCOM Alert connector fighting with AD connector?

    I am experiencing some conflicts between the Operations Manager Alert connector and the Active Directory connector. They are both updating the same property values, but the values are not the same.
    Example:
    A User changes Department, and the Department property in Active Directory are modified with the name of the new Department
     The Active Directory connector modifies the value of the User Objects Department property in the Service Manager Configuration Management Database
     Then the Operations Manager Alert connector modifies the same property on the User Object with the old value.
    Have someone seen the same behavior?

    Perhaps correct the bad data in the Ops Manager system?
    In all seriousness, the problem with this behavior is that you have two systems that disagree on the value of a property of an object. the behavior you are seeing is them disagreeing. to quote microsoft, "This behavior is by design"

  • SCOM Alert Connector - not updating the start time and finish time

    When I am monitoring the status of connectors in service manager console, I found that for SCOM Alert Connector the Start Time and Finish Time are not updating. Previously it was updated daily. As of now, service manager is working fine but would like
    to check will it create any issues? Even I have cliked on Synchronize Now, but there is no update. Please guide me on this to trouble shoot further? Thanks.

    Hi,
    Based on my research, the Start Time and Finish Time values are not updated when an alert connector is synchronized. These values are only updated when alert data is transferred between Operations Manager 2007 and Service
    Manager.
    More details, please refer to the link below:
    http://technet.microsoft.com/en-us/library/hh495609.aspx
    In addition, here is a blog about troubleshooting for SCSM and SCOM alert connector:
    http://blogs.technet.com/b/servicemanager/archive/2010/04/14/troubleshooting-tips-for-your-scsm-scom-alert-connector.aspx
    Regards,
    Yan Li
    Regards, Yan Li

  • SCSM to SCOM Alert Connector Error

    Hello,
    Long story short, the SCSM admin created an Alert Connector between SCSM and SCOM, then uninstalled SCSM and started over.  That means I had an orphaned SCSM connector in SCOM.
    In order to set up a new connection, I followed the instructions found in Kevin Holman's blog post:
    http://blogs.technet.com/b/kevinholman/archive/2012/09/28/opsmgr-2012-how-to-delete-an-old-product-connector.aspx
    Now, when I try to re-create a new Alert Connector, I get this error:
    "Found at least one other alert connector in Operations Manager.  Alerts may not be routed as expected if multiple connectors subscribe to the same alert."
    I checked the SCOM server to make sure there were no orphaned connectors by running this SQL code against the OperationsManager database:
    Aside from the copious number of SCVMM connectors, there were six connectors.  Of those six, the previous SCSM connector is marked as "IsDeleted":
    Next, I checked the "Microsoft.SystemCenter.Notifications.Internal" management pack to verify that there are no orphaned subscriptions.  The ONLY alert referenced is for the "Advisor Data Connector".
    At this point, my questions are as follows:
    1) Will the System Center Advisor (now renamed Azure Operational Insights) connector cause the warning message I listed above when setting up an Alert Connector in SCSM?
    2) Is there another orphaned entry in SCOM that I need to check for and remove before setting up the SCSM alert connector? 

    Hi,
    I would like to suggest you remove the subscription that was orphaned. When remove a connector we should remove the subscriptions first.
    And here is a similar thread
    SCSM 2012 Cannot create SCOM Alert Connector        
    https://social.technet.microsoft.com/Forums/en-US/a5d0b921-bb0a-43b8-99ca-8b0112ab3bf0/scsm-2012-cannot-create-scom-alert-connector?forum=connectors                         
    Regards,
    Yan Li
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

  • Weblogic.connector.exception.WLRAConfigurationException

    Hi
    We have an application that is running fine in Weblogic 6.1 version. Now we are planning to move to 9.1 version of Weblogic.
    As part of this excercise, I tried to deploy the application (wallet.ear), which is running fine in Weblogic 6.1. But it is reporting WLRAConfigurationException while activating the deployment changes from weblogic administrator console.
    As I understood it is reporting this error with one third party (.rar) application we are using in our application. We are using an application named infranet.rar to provided O-R services to our application.
    Below is the stack trace recorded from the application server.
    An error occurred during activation of changes, please see the log for details.
    weblogic.connector.exception.WLRAConfigurationException: There are 1 nested errors: weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND C:\bea91\weblogic91\samples\domains\wl_server\.\servers\examplesServer\tmp\_WL_user\wallet\p1wa4\infranet.rar\META-INF\weblogic-ra.xml:50:4:50:4: problem: cvc-complex-type.2.4a: Expected elements 'rotation-type@http://www.bea.com/ns/weblogic/90 number-of-files-limited@http://www.bea.com/ns/weblogic/90 file-count@http://www.bea.com/ns/weblogic/90 file-size-limit@http://www.bea.com/ns/weblogic/90 rotate-log-on-startup@http://www.bea.com/ns/weblogic/90 log-file-rotation-dir@http://www.bea.com/ns/weblogic/90 rotation-time@http://www.bea.com/ns/weblogic/90 file-time-span@http://www.bea.com/ns/weblogic/90' instead of 'log-filename@http://www.bea.com/ns/weblogic/90' here in element logging@http://www.bea.com/ns/weblogic/90:<C:\bea91\weblogic91\samples\domains\wl_server\.\servers\examplesServer\tmp\_WL_user\wallet\p1wa4\infranet.rar/META-INF/weblogic-ra.xml:50:4> at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:231) at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:205) at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:143) at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:271) at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:240) at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:300) at weblogic.application.descriptor.AbstractDescriptorLoader.createDescriptor(AbstractDescriptorLoader.java:344) at weblogic.application.descriptor.AbstractDescriptorLoader.createDescriptor(AbstractDescriptorLoader.java:328) at weblogic.application.descriptor.AbstractDescriptorLoader.getDescriptor(AbstractDescriptorLoader.java:237) at weblogic.application.descriptor.AbstractDescriptorLoader.getRootDescriptorBean(AbstractDescriptorLoader.java:217) at weblogic.connector.configuration.ConnectorDescriptor.getWeblogicConnectorBean(ConnectorDescriptor.java:317) at weblogic.connector.configuration.DDUtil.getRAInfo(DDUtil.java:124) at weblogic.connector.deploy.ConnectorModule.loadDescriptors(ConnectorModule.java:747) at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.java:165) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:620) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:231) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:183) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:84) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:219) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:750) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1209) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:246) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
    VALIDATION PROBLEMS WERE FOUND C:\bea91\weblogic91\samples\domains\wl_server\.\servers\examplesServer\tmp\_WL_user\wallet\p1wa4\infranet.rar\META-INF\weblogic-ra.xml:50:4:50:4: problem: cvc-complex-type.2.4a: Expected elements 'rotation-type@http://www.bea.com/ns/weblogic/90 number-of-files-limited@http://www.bea.com/ns/weblogic/90 file-count@http://www.bea.com/ns/weblogic/90 file-size-limit@http://www.bea.com/ns/weblogic/90 rotate-log-on-startup@http://www.bea.com/ns/weblogic/90 log-file-rotation-dir@http://www.bea.com/ns/weblogic/90 rotation-time@http://www.bea.com/ns/weblogic/90 file-time-span@http://www.bea.com/ns/weblogic/90' instead of 'log-filename@http://www.bea.com/ns/weblogic/90' here in element logging@http://www.bea.com/ns/weblogic/90:<C:\bea91\weblogic91\samples\domains\wl_server\.\servers\examplesServer\tmp\_WL_user\wallet\p1wa4\infranet.rar/META-INF/weblogic-ra.xml:50:4>
    In case if any one of you aware of the root for this problem, please let me know
    Thanks in advance for your kind support
    regards
    Venkat

    This has been resolved

  • I always get FATAL ALERT: Fatal Exception everytime i try to hot sync

    i am trying to sync my tungsten E2 which i just bought refurbished. i installed my own software since my last tungsten E2 went kaput ( so i previously owned a tungsten E2 ). i always get FATAL ALERT: Fatal Exception everytime i try to hot sync. what is wrong? thank you.
    Post relates to: Tungsten E2

    As with most problems that occur on a Palm PDA, it is either software or hardware related and we have to determine which one.
    If your device is not locked up, the best method is to first make a complete backup of your unit to your SD card using the free "NVBackup" (available from http://www.freewarepalm.com) After the backup is complete, Hard Reset the unit, then test to see if full functionality returns.
    To perform a Hard Reset:
    While pressing and holding the Power button down, tap and release the Reset button in back and continue to hold the Power button down. When the grey Palm logo appears, you can release the Power button.
    You should now see the warning page in about 5 languages. Press the UP direction on the 5-way pad to complete the task. Your Palm will reset itself several times as it re-installs the original programs and erases all your previous data.
    DO NOT HOTSYNC YET! Test the unit before reinstalling any software. If the unit works correctly, your problem is being caused by a "drug interaction" of software - maybe one rogue program, or a combination of several. You'll have to reinstall the third-party programs one or a few at a time to find the problem one. To avoid re-installing a software issue, rename your /Backup directory in your Palm folder (on a PC it's found here: C/Program Files/Palm(One)/"your HotSync ID name truncated"/Backup) to something like "/BackupOLD". Now perform the HotSync, choose your HotSync name you've been using, and all your PIM data will return, but not the third-party programs. Test for functionality again. If all is good, start installing the old programs from your /BackupOLD directory one (or a few if brave) at a time.
    If the unit does not work after a Hard Reset is performed correctly, then it may be Hardware-related. (If it's a connection problem via either BlueTooth or Wifi, be sure nothing has changed on the unit you're trying to connect to!)
    Hope this has helped,
    Wyrenut
    I am a Volunteer here, not employed by HP.
    You too can become an HP Expert! Details HERE!
    If my post has helped you, click the Kudos Thumbs up!
    If it solved your issue, Click the "Accept as Solution" button so others can benefit from the question you asked!

  • Weblogic.connector.exception.RAOutboundException

    Hi All ,
    I have created an new data source and an new connection pool .While i am updating the DBAdapter , i am receiving the following error .Can please any one please suggest .
    weblogic.connector.exception.RAOutboundException: There are 1 nested errors: weblogic.connector.exception.RAOutboundException: Attempting to create a connection factory with a JNDI name that already exists: 'eb/DB/Raj'. at weblogic.connector.outbound.RAOutboundManager.createConnectionFactory(RAOutboundManager.java:453) at weblogic.connector.outbound.RAOutboundManager.initialize(RAOutboundManager.java:420) at weblogic.connector.outbound.RAOutboundManager.<init>(RAOutboundManager.java:121) at weblogic.connector.common.RAInstanceManager.initialize(RAInstanceManager.java:1217) at weblogic.connector.common.RAInstanceManager.<init>(RAInstanceManager.java:352) at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.java:197) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:507) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367) at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:43) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

    hi joe ,
    Can you please elaborate on this .It would also be great if you can advice how to proceed further.
    Regards ,
    Nagakiran E.V

  • Alert title displayed in uwl

    Hi, experts
    i found out that the alerts shown in the uwl on portal, it will display the technical key of the alert category at first, then after several minites it's refreshed to normal text .
    could you please tell me how to solve this?
    we dont want the technical key be shown.
    thanks and best regards.
    Jun

    yes i did.
    the text will show after 1-2 minutes, before that it will be displayed as the technical key.
    any clue?
    br.
    zj

  • RSA Authentication Manager connector exception with OIM 9.1.0.2

    Hi,
    I have installed RSA AM connector 9.1.0.7 on OIM 9.1.0.2 BP18 on Windows Server 2008 R2.
    When I run the RSA recon schedule task, I get the following exception:
    DEBUG,24 Feb 2012 12:11:13,227,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader:findClass - Data: loading class - Value: org.iscreen.impl.xml.PositionContext
    *ERROR,24 Feb 2012 12:11:13,229,[OIMCP.RSAM],====================================================*
    *ERROR,24 Feb 2012 12:11:13,229,[OIMCP.RSAM],oracle.iam.connectors.rsaauthmgr.usermgmt.tasks.RSALookupRecon : getGroups : An error occurred parsing the XML located at com/rsa/admin/SearchGroupsCommand_validators.xml. The location within the file is at /. The following was found that was in error: Unable to load/locate configuration file.*
    *ERROR,24 Feb 2012 12:11:13,229,[OIMCP.RSAM],====================================================*
    *ERROR,24 Feb 2012 12:11:13,230,[OIMCP.RSAM],================= Start Stack Trace =======================*
    *ERROR,24 Feb 2012 12:11:13,230,[OIMCP.RSAM],oracle.iam.connectors.rsaauthmgr.usermgmt.tasks.RSALookupRecon : getGroups*
    *ERROR,24 Feb 2012 12:11:13,230,[OIMCP.RSAM],An error occurred parsing the XML located at com/rsa/admin/SearchGroupsCommand_validators.xml. The location within the file is at /. The following was found that was in error: Unable to load/locate configuration file.*
    *ERROR,24 Feb 2012 12:11:13,230,[OIMCP.RSAM],Description : An error occurred parsing the XML located at com/rsa/admin/SearchGroupsCommand_validators.xml. The location within the file is at /. The following was found that was in error: Unable to load/locate configuration file.*
    *ERROR,24 Feb 2012 12:11:13,230,[OIMCP.RSAM],org.iscreen.impl.xml.XmlConfigurationException: An error occurred parsing the XML located at com/rsa/admin/SearchGroupsCommand_validators.xml. The location within the file is at /. The following was found that was in error: Unable to load/locate configuration file.*
    at org.iscreen.impl.xml.XmlParser.getInput(XmlParser.java:215)
    at org.iscreen.impl.xml.XmlParser.parse(XmlParser.java:116)
    at org.iscreen.impl.xml.XmlServiceFactory.registerInclude(XmlServiceFactory.java:117)
    at org.iscreen.impl.xml.XmlServiceFactory.loadConfig(XmlServiceFactory.java:285)
    at org.iscreen.ValidationFactory.buildFactory(ValidationFactory.java:120)
    Any idea what may be the issue???
    Thanks.

    As per given bug it is looking for jars which is missing
    have you install connector using deployment manager?? if yes it copy required jars at target location. verify if not there copy jars in Scheduled Task folder.
    Check the document if any external jars required and same put at ThirdParty folder

  • Process Chain alerts not visible in UWL

    I have carried out the weblog test that Ginger published at
    /people/ginger.gatling/blog/2005/06/16/integrating-alerts-into-uwl--its-no-problem
    and everthing worked fine.
    We are, however, trying to use Process Chain alerts from CCMS.  These alerts are visible if we run transaction RZ20 in the back end system but the UWL does not see them.
    Is there a guide or something showing how to configure this?
    Thank you

    Hi Bernard,
    I've checked out a couple of systems - you can create alert categories for process chain alerts, and once you have the category you can of course assign recipients.
    In fact you should see some existing categories in your system for process chains in transaction ALRTCATDEF.
    The UWL essentially reflects what is in the BSP ALRTINBOX as it is using the same/similar routines to derive the alert inbox worklist.   So if you don't have anything in ALRTINBOX then it is correct that nothing is showing in UWL inbox as well. 
    You need to set up the categories and recipients against your process chain alerts.
    I'm not all that familiar with BI Process Chains but a couple of minutes looking at the IMG in transaction SPRO showed that in transaction RSPC when you select a process chain you can use menu option Settings > Maintain Alert Categories to make the link between the process chain and the alert categories.  You'll probably know what to enter here better than I do.
    Regards,
    Jocelyn

  • Alerts not visible in UWL

    Hi All of u,
    I have registered the creted system in UWL and I wanna see the raised Alerts in it. but I could not where can be the problem was it with config if so how can it be done?
    Thanks in Advance

    Hi,
    Please follow the following link. It has been explained in detail:
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a3461636-0301-0010-3787-978f5ac8bd45
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/103e2cf0-ec95-2b10-d198-a2d5edfbd7f8
    Regards,
    Niraj

Maybe you are looking for