OSB - Creating SLA Alerts using WLST

Hi,
I'd like to create SLA Alerts on proxy services using WLST rather than via the service bus console.
The MBean described at:
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/javadoc/com/bea/wli/sb/management/configuration/ProxyServiceConfigurationMBean.html
only seem to allow enabling or disabling SLA alerts not creating them.
Can anyone point me in the right direction?
Thanks
Nick

Please refer -
http://blogs.oracle.com/MarkSmith/entry/osb_alerts_purging_is_essentia
From the blog -
The components that make up WLDF will be targeted to a single managed server in a clustered environment or to the Admin server in a single server environment. To establish what managed server this is, check to see where the WLI Aggregator application is targeted to. The WLDF data will be stored under this single managed server in the following location: //domain_name/servers/server_name/data/store/diagnostics/Check that on which server WLI Aggregator application is targeted and connect to that server from your script.
Regards,
Anuj

Similar Messages

OSB: API to create SLA alert on proxy

Hi,
does anyone know how to set an SLA alert for a large number of proxy services automatically ? I went through http://docs.oracle.com/cd/E21764_01/apirefs.1111/e15033/toc.htm but haven't found anything useful.
There is close to a hundred of proxies in my configuration and I need to set two SLA rules for all of them. Obviously, I don't want to do that through /sbconsole one by one. Additionally, I want to have sort of after-deploy-script to make sure that all deployed proxies have those SLA alerts set without checking anything manually.
Any idea?

Was looking at this and just realised the exact issue that is reported in this thread.
It would be really useful to have a way of executing a config file via the API to setup these SLAs.
Is there a place where I can vote for enhancements or see the release roadmap for OSB?
Many thanks
Murph

Create an alert using the currentime

Hi All,
How do i create an alert in CR9 using the current system/PC time. Thanks.

I don't have CR 9 installed any more since it's been out of support for a long time now but in CR 2008 click on Report Menu, Alert and use the wizard to create the formula. CR 2008 has a CurrentTime function which you then test against a value you enter.
I don't recall what CR 9 had for this functionality now, sorry...
Thank you
Don

How can i create slaes order using BAPI

hi all,
i didnt work on BAPIS .how can i create sales order using BAPI here i should pass Z values.
Moderator message : FAQ, search for available information. Thread locked.
Edited by: Vinod Kumar on Sep 13, 2011 12:22 PM

Hi!
There are a lot of answered threads regarding your question. Try searching first. Below is a sample link.
BAPI_SALESORDER_CREATEFROMDAT2
Regards,
Steph
Edited by: stephquion on Sep 13, 2011 8:25 AM

Purging OSB Alerts using WLST scripts

Hi,
I am using the below script to purge the OSB Alerts. I am connecting to the OSB managed server to purge the alerts.
*# Connect to server*
*     connect(weblogic,welcome,intdev:8011)*
*     # Calculate the start and end time for purging the alerts*
*     now=System.currentTimeMillis()*
*     startTime=0*
*     endTime=(now - days*3600*24*1000)*
*     # Purging the Alerts*
*     serverRuntime()*
*     print "Deleting records older than", days, "days from OSB Alerts"*
*     print cmo*
*     alsbAlerts = cmo.getWLDFRuntime().getWLDFAccessRuntime().lookupWLDFDataAccessRuntime('CUSTOM/com.bea.wli.monitoring.alert')*
*     numDeleted = alsbAlerts.deleteDataRecords(startTime,endTime,"")*
*     print "No. of Alerts deleted =", numDeleted*
*     # Disconnect from the domain*
*     disconnect()*
I am getting the below error while executing the script
Successfully connected to managed Server 'osb_server1' that belongs to domain 'soa_domain'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
Location changed to serverRuntime tree. This is a read-only tree with ServerRuntimeMBean as the root.
For more help, use help(serverRuntime)
Deleting records older than 60 days from OSB Alerts
+[MBeanServerInvocationHandler]com.bea:Name=osb_server1,Type=ServerRuntime+
Disconnected from weblogic server: osb_server1
Unexpected error: weblogic.management.ManagementException
Problem invoking WLST - Traceback (innermost last):
File "/home/soadev/WLST/FINAL/purging/purge_Alerts.py", line 41, in ?
weblogic.management.ManagementException:
at weblogic.diagnostics.accessor.WLSAccessorMBeanFactoryImpl.createDiagnosticDataAccessRuntime(WLSAccessorMBeanFactoryImpl.java:206)
at weblogic.diagnostics.accessor.AccessRuntime.lookupDataAccessRuntime(AccessRuntime.java:315)
at weblogic.diagnostics.accessor.DiagnosticAccessRuntime.lookupWLDFDataAccessRuntime(DiagnosticAccessRuntime.java:77)
at weblogic.diagnostics.accessor.DiagnosticAccessRuntime.lookupWLDFDataAccessRuntime(DiagnosticAccessRuntime.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.management.jmx.modelmbean.WLSModelMBean.invoke(WLSModelMBean.java:437)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447)
at weblogic.management.mbeanservers.internal.JMXContextInterceptor.invoke(JMXContextInterceptor.java:268)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447)
at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(SecurityInterceptor.java:444)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanServer.java:323)
at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11$1.run(JMXConnectorSubjectForwarder.java:663)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11.run(JMXConnectorSubjectForwarder.java:661)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder.invoke(JMXConnectorSubjectForwarder.java:654)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1427)
at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1265)
at java.security.AccessController.doPrivileged(Native Method)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1367)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
+Caused by: weblogic.management.ManagementException: [Diagnostics:320103]There was an error creating the DiagnosticDataRuntimeMBean instance with the given logical name CUSTOM/com.bea.wli.monitoring.alert.+
at weblogic.diagnostics.accessor.WLSAccessorMBeanFactoryImpl.createDataAccessRuntime(WLSAccessorMBeanFactoryImpl.java:228)
at weblogic.diagnostics.accessor.WLSAccessorMBeanFactoryImpl.access$000(WLSAccessorMBeanFactoryImpl.java:55)
at weblogic.diagnostics.accessor.WLSAccessorMBeanFactoryImpl$1.run(WLSAccessorMBeanFactoryImpl.java:201)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.diagnostics.accessor.WLSAccessorMBeanFactoryImpl.createDiagnosticDataAccessRuntime(WLSAccessorMBeanFactoryImpl.java:197)
+... 39 more+
weblogic.management.ManagementException: weblogic.management.ManagementException:
Please provide pointers to get rid of this issue.
Edited by: Chintan Parekh on Jun 1, 2011 2:41 AM

Please refer -
http://blogs.oracle.com/MarkSmith/entry/osb_alerts_purging_is_essentia
From the blog -
The components that make up WLDF will be targeted to a single managed server in a clustered environment or to the Admin server in a single server environment. To establish what managed server this is, check to see where the WLI Aggregator application is targeted to. The WLDF data will be stored under this single managed server in the following location: //domain_name/servers/server_name/data/store/diagnostics/Check that on which server WLI Aggregator application is targeted and connect to that server from your script.
Regards,
Anuj

Create durable subscribers, JMSAdapter JNDI and DBAdapter JNDI using WLST

Hi All,
I have developed some WLST scripts to create new JMS servers, JMS modules which includes queues, topics and connection factories, data sources, etc.
I can successfully create topics using WLST but I cannot see any option to create durable subscribers using WLST. Also, I can create JMS server JNDIs along with its modules but I am unable to create JMSAdapter JNDI ( under Deployments ) using WLST.
Can anyone please help me out?
Thanks in advance,
-Karan

Hi,
I have the same problem, and when I try to record it. The py file contains nothing.
I know sometime weblogic server doesn't record, such as outbound connection factory. I guess durable Subscribers is another one.
Anyone know know to do this?
Cheers,
Tim

How to create users and groups using WLST Offline with Weblogic 8.1.4

How to create users and groups using WLST Offline with Weblogic 8.1.4?
Any ideas?

Hi this is how i created a user using WLST Offline?
cd('/Security/' + domainName)
# Delete the default user name weblogic
# incase you want to remove the defualt user weblogic
delete('weblogic','User')
# Creating a new user defined
create(userName, 'User')
# Setting the password of the user you created.
cd ('/Security/' + domainName + '/User/' + userName)
cmo.setPassword(password)
Regards
Makenzo

How to set XPoweredByHeaderLevel to NONE using wlst

How to set XPoweredByHeaderLevel to NONE using wlst (by default the value is SHORT).
I mean, I have created a domain using wlst.
Now I want to set XPoweredByHeaderLevel of WebAppContainerMBean to NONE using wlst.
It will be helpful if a sample python(Jython) script is provided.
Please help.

Here is a quick Jython example of how to do what you want:
#assuming you already have correct imports for wlst module
#connect to the AdminServer using proper credentials and host information
wlst.connect(username, password, host_info)
#extract domain name
domainName = wlst.domainName
#start an edit session and navigate to the WebAppContainerMBean
wlst.edit()
wlst.cd("/WebAppContainer/" + domainName)
wlst.startEdit()
#set the value of the XPoweredByHeaderLevel attribute to "NONE"
wlst.cmo.setXPoweredByHeaderLevel("NONE")
#activate the change
wlst.activate()

Configuring and using SLA alerts and Monitoring in OSB.

Hi,
I am having a business service which logically represents composite endpoint URI. Now I want to enable Monitoring and generate an SLA alert if the composite URI that the business service is representing is DOWN for some reason and the proxy routing to the BS is not able to invoke it.
How do I do that? Pls suggest!

Hi Deb,
Please refer section "46.5 How to Generate Alerts Based on Endpoint URI Status" at below link -
http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15867/endpointurimgmt.htm#i1080465
Also refer -
http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15867/monitoring_ops.htm#i1108778
Please post OSB related questions in Oracle SOA Suite forum only -
SOA Suite
Regards,
Anuj

WLST Script for Disabling/Enabling Global SLA Alerting.

Hello,
I wanna find a way from the WLST to disable and enable the SLA Alerting which is under Operations-->Global Settings in the sbconsole. This is the global setting not per sercive!
I have found how to create a session and how to disable the alerts per service, but i cannot find which MBean is accessed when throught the sbconsole the global SLA alerting is disabled/enabled.
Can anybody point me to the right direction or help me to find how to do this from WLST.
Thanks.

Hi Ganesh,
I have finally created the script i was looking for.. I copy-paste it below as a sample... For sure you need all the lines of code until the comment i have put "#####you need this code above"
now the code you see below the comment is for disabling the global sla alerting... you have to write a bit to target a specific service that you want to disable.
Keep in mind that after you make your change you hava to include those lines in order to activate the changes and disconnect and exit..
sessionMBean.activateSession(sessionName, "enable SLA")
disconnect()
exit()
If you have access to oracle support search for wlst script for osb it has a lot and you can find how to target a specific service...
I hope that i help a little bit
import sys
import wlstModule
from com.bea.wli.sb.management.configuration import SessionManagementMBean
from com.bea.wli.sb.management.configuration import ALSBConfigurationMBean
#from com.bea.wli.sb.management.configuration import ProxyServiceConfigurationMBean
from com.bea.wli.sb.management.configuration.operations import OperationsConfigMBean
from com.bea.wli.config import Ref
from com.bea.wli.sb.util import Refs
# Connect (username, password, URL)
connect('weblogic', 'password', 't3://localhost:7001')
domainRuntime()
# Create a session name
sessionName =sessionName = String("SessionScript"+Long(System.currentTimeMillis()).toString())
print('... after session. Session is: ', sessionName)
# Get the session MBean and create a session
sessionMBean = findService(SessionManagementMBean.NAME,SessionManagementMBean.TYPE)
print('-debug-this is the sessionbean',sessionMBean)
print('SessionMBean is: ', sessionMBean)
sessionMBean.createSession(sessionName)
print(String('Session was created ... ').concat(sessionName))
#####you need this code above
domainCustom()
cd('com.bea')
#path='com.bea:Name=OperationsConfig.'+sessionName+',Location=AdminServer,Type=com.bea.wli.sb.management.configuration.operations.OperationsConfigMBean'
cd('com.bea:Name=OperationsConfig.'+str(sessionName)+',Location=AdminServer,Type=com.bea.wli.sb.management.configuration.operations.OperationsConfigMBean')
set('DomainSLAAlertingEnabled',java.lang.Boolean("true"))
# Now commit (activate) the changes
sessionMBean.activateSession(sessionName, "enable SLA")
disconnect()
exit()

Help creating project specific ALSB Customization file using WLST

I asked this question in August in another forum and was redirected here, but never followed up. I'm hopeful someone has done this...
Is it possible to create an ALSB CUstomization file for a single project using WLST?
If so, does anyone have an example they would be wiling to share. I've been beating my head against the wall for almost 2 days (well, months now...) , and I'm REALLy starting to get a headache from it now....
We're running WLS 9.2 MP2 and ALSB 2.6 RP1
Any help is greatly appreciated,
Brian

Brian, OSB specific questions are best directed in the SOA Suite forum:
SOA Suite
It looks like there is an ALSBConfigurationMBean with a customize method, but I have not worked with it and it does not sound like that will give you precisely what you want:
http://edocs.bea.com/alsb/docs261/javadoc/com/bea/wli/sb/management/configuration/ALSBConfigurationMBean.html#customize(java.util.List)

SLA alert doesn't display in the OSB console's dashboard

Greetings,
I defined several SLA alerts for a proxy service and I'm using a client which creates on the purpose the required conditions to raise the alerts, but nothing displays in the Dashboard. I also enabled the monitoring checkbox but I don't know if the level has to be pipeline, service or action. Did I miss something ?
Many thanks in advance,
Nicolas

1° Monitoring is enabled at service level.
2° The aggregation interval for the condition is the same as the monitoring one.
There is no message in the Dashboard, neither SLA Alerts nore any other one. What is very strange is that the Service Health tab says that the avg. response time is 0 seconds while the proxy service reply takes 30 seconds. The proxy service is based on a JAX-RPC WSDL generated in Workshop. I also tried JAX-RPC with the same result? The client is an Axis one generated in Workshop (not a WebLogic clientgen one) and it calls the proxy service as follows:
//JAX-RPC
TestService service = new TestServiceProxy().getTestService();
// Service will reply in 30 seconds
service.delay30();
//JAX-WS
TestService service = new TestServiceLocator().getTestServiceSoapPort();
// Service will reply in 30 seconds
service.delay30();
Once called, the operation logs a message at its begin and at its end. The message shows that the processing takes 30 seconds. The SLA alert rule says that an alert has to be raised, having the console as the destination, whenever the processing time of this operaztion invocation takes more than 5 seconds. However, no message apears in the dashboard, no SLA alert and the service's avg processing time is displayed as being 0 seconds.
Many thanks in advance for any help.
Nicolas

Create a ALSB 3.0 domain using WLST

Hi,
I have created a ALSB domain using config.sh and then I used the following script to create the template
# create doman template
readDomain('/usr/local/bea/user_projects/domains/z2esbadmin')
writeTemplate('/home/was/work/wlst/z2esbadminTemplate.jar')
exit()
The template jar file is created successfully without any warning/error
When I tried to create the domain using the template with the following comand:
createDomain('z2esbadminTemplate.jar','/home/was/work/user_projects/domains/z2esb', 'weblogic', 'weblogic')
exit()
I got the following error message:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Error: create() failed. Do dumpStack() to see details.
Problem invoking WLST - Traceback (innermost last):
File "/home/mcas/weblogic/wlst/createEsbDomain.py", line 1, in ?
File "/tmp/WLSTOfflineIni25221.py", line 96, in createDomain
com.bea.plateng.domain.script.jython.WLSTException: com.bea.plateng.domain.script.ScriptException: com.bea.plateng.domain.ValidateException: Property "User name" of User with original name "" is invalid. The property value is duplicated.
at com.bea.plateng.domain.script.jython.CommandExceptionHandler.handleException(CommandExceptionHandler.java:51)
at com.bea.plateng.domain.script.jython.WLScriptContext.handleException(WLScriptContext.java:1468)
at com.bea.plateng.domain.script.jython.WLScriptContext.create(WLScriptContext.java:672)
at com.bea.plateng.domain.script.jython.WLScriptContext.createDomain(WLScriptContext.java:507)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160)
at org.python.core.PyMethod.__call__(PyMethod.java:96)
at org.python.core.PyObject.__call__(PyObject.java:248)
at org.python.core.PyObject.invoke(PyObject.java:2016)
at org.python.pycode._pyx5.createDomain$21(/tmp/WLSTOfflineIni25221.py:96)
at org.python.pycode._pyx5.call_function(/tmp/WLSTOfflineIni25221.py)
at org.python.core.PyTableCode.call(PyTableCode.java:208)
at org.python.core.PyTableCode.call(PyTableCode.java:404)
at org.python.core.PyFunction.__call__(PyFunction.java:184)
at org.python.core.PyObject.__call__(PyObject.java:314)
at org.python.pycode._pyx18.f$0(/home/mcas/weblogic/wlst/createEsbDomain.py:1)
at org.python.pycode._pyx18.call_function(/home/mcas/weblogic/wlst/createEsbDomain.py)
at org.python.core.PyTableCode.call(PyTableCode.java:208)
at org.python.core.PyCode.call(PyCode.java:14)
at org.python.core.Py.runCode(Py.java:1135)
at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:167)
at weblogic.management.scripting.WLST.main(WLST.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at weblogic.WLST.main(WLST.java:29)
Caused by: com.bea.plateng.domain.script.ScriptException: com.bea.plateng.domain.ValidateException: Property "User name" of User with original name "" is invalid. The property value is duplicated.
at com.bea.plateng.domain.script.ScriptExecutor.create(ScriptExecutor.java:897)
at com.bea.plateng.domain.script.jython.ScriptProxyFactory.deepCreateProxy4SecurityType(ScriptProxyFactory.java:135)
at com.bea.plateng.domain.script.jython.WLScriptContext.create(WLScriptContext.java:646)
... 27 more
Caused by: com.bea.plateng.domain.ValidateException: Property "User name" of User with original name "" is invalid. The property value is duplicated.
at com.bea.plateng.domain.aspect.XBeanConfigAspect.selfValidate(XBeanConfigAspect.java:630)
at com.bea.plateng.domain.aspect.AbstractConfigAspect.validate(AbstractConfigAspect.java:1130)
at com.bea.plateng.domain.aspect.AbstractConfigAspect.selfSetValue(AbstractConfigAspect.java:1615)
at com.bea.plateng.domain.aspect.AbstractConfigAspect.setValueInternal(AbstractConfigAspect.java:1574)
at com.bea.plateng.domain.aspect.AbstractConfigAspect.setValue(AbstractConfigAspect.java:748)
at com.bea.plateng.domain.aspect.AbstractConfigAspect.setValue(AbstractConfigAspect.java:757)
at com.bea.plateng.domain.aspect.FilteredConfigAspect.setValue(FilteredConfigAspect.java:431)
at com.bea.plateng.domain.operation.HTableEditOperation.createSimpleConfigAspects(HTableEditOperation.java:265)
at com.bea.plateng.domain.operation.HTableEditOperation.createSimpleConfigAspects(HTableEditOperation.java:221)
at com.bea.plateng.domain.script.ScriptExecutor.create(ScriptExecutor.java:873)
... 29 more
Caused by: java.beans.PropertyVetoException: The property value is duplicated.
at com.bea.plateng.domain.event.aspect.UniqueValueValidateListener.valueChanged(UniqueValueValidateListener.java:127)
at com.bea.plateng.domain.event.aspect.ConfigAspectValueListener.vetoableChange(ConfigAspectValueListener.java:138)
at com.bea.plateng.common.comdev.MVetoableChangeSupport.fireVetoableChange(MVetoableChangeSupport.java:189)
at com.bea.plateng.common.comdev.MVetoableChangeSupport.fireVetoableChange(MVetoableChangeSupport.java:156)
at com.bea.plateng.common.comdev.MVetoableChangeSupport.fireVetoableChange(MVetoableChangeSupport.java:139)
at com.bea.plateng.domain.aspect.XBeanConfigAspect.selfValidate(XBeanConfigAspect.java:620)
... 38 more
com.bea.plateng.domain.script.jython.WLSTException: com.bea.plateng.domain.script.jython.WLSTException: com.bea.plateng.domain.script.ScriptException: com.bea.plateng.domain.ValidateException: Property "User name" of User with original name "" is invalid. The property value is duplicated.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I did exactly the same thing for a normal weblogic domain (not alsb) and it works fine. Do I have to do something different for creating ALSB 3.0 domain?
Thanks,
Nathan

Well, we've had exactly the same issues.
From our experience even the most trivial tasks involving ALSB/OSB, WLST and Templates fail. Not just a single error, but every time we've tried something different to work around an issue we came across the script blew up with yet another error. After a couple of painful days we came to the conclusion that at least with WL10/ALSB3 templates and scripting are just too premature and too buggy to be of any use.
And at least from the ALSB Release Notes and Metalink it doesn't look like these issues have been addressed with subsequent releases.
We've resorted to creating the domain from scratch instead of using templates of our own domains created with the config wizard.
Cheers,
Jan

OSB 11g: Can I create an Alert Destination to call another webservice?

Hi All,
We would like to send Alert message via SMS to speified person.
As we have already a web service to send SMS, can we just create an Alert Destination to call this web service to do that?
Thanks for your help!
Edited by: FrankieHuang on May 2, 2013 12:44 AM

you can use a JMS queue as your alert destination and have a process listening on the JMS queue to invoke the webservice.#
You dont have a direct option to call a service from your alert mechanism..
http://docs.oracle.com/cd/E14571_01/doc.1111/e15867/alert_destinations.htm

How to create an RDBMS event generator using wlst on weblogic 10.3

how to create an RDBMS event generator using wlst on weblogic 10.3, i got a code fragment needing class "com.bea.wli.management.configuration.RDBMSEventGenChannelConfiguration"
but i can' t find this class in classpath on weblogic 10.3, pls help me, thanks. code sample is better.

Hi,
RDBMS Event Generator Channel Rule Definition
When you are creating channel rule definitions in the WebLogic Integration Administration Console, it is recommended that you do not use the Back button if you want to resubmit the details on a page.
You should always use the navigation links provided and create a new channel rule definition.
http://download.oracle.com/docs/cd/E13214_01/wli/docs85/deploy/cluster.html
http://download.oracle.com/docs/cd/E13214_01/wli/docs81/relnotes/relnotesLimit.html
http://otndnld.oracle.co.jp/document/products/owli/docs10gr3/pdf/deploy.pdf
This problem has been seen in the past when defining the channel rule for an RDBMS Event Generator if schema name was specified with the incorrect case (i.e. lowercase when it should have been uppercase or vice versa). To that end, it is suggested to change the case of the schema when creating the channel rule
Regards,
Kal

OSB - Creating SLA Alerts using WLST

Similar Messages

Maybe you are looking for