Regarding wlss work managers

I am using WLSS 3.1-MP1. I have couple of doubts regarding work managers wlss.timer & wlss.transport.
1. Minimum Threads Constraint : Weblogic documentation says "+The minimum number of threads allocated to resolve deadlocks+". Does it mean that these threads won't be used to process messages & timers ? What happens if this constraint is not specified ?
2. wlss.timer : WebLogic document says "+SIP timers are processed by a work manager named wlss timer+". Does it mean application level timers (ServletTimer) or the container level timers (e.g. transaction timers etc..)
3. wlss.transport : I am assuming the MaxThreadsConstraints specified for this work manager tells maximum number of threads that can process incoming SIP messages (requests and responses) for new and existing sessions...Am I right?
Thanks,
KeDar

Yes wlss.timer work manager handles execution of all the timers (application or container/protocol level)
Similarly wlss.transport is workmanager for handling all the sip messages
Regarding WM's, it is more of core weblogic query. But IMO
Minimum Threads Constraint : Essentially means that at least that many threads will be working for the given WorkManager out of common pool of threads
and
Maximum Threads Constraint on workmanager essentially means at most that many threads will be working for the given WorkManager out of common pool of threads
IMO If no Minimum Threads Constraint is specified then still that WM will get threads as per need till pool has some idle threads and/or we are still below pool capacity where in new thread will be spawned.

Similar Messages

Work Managers for SOA composites

Hi All,
We have couple composites which needs to be deployed on Oracle SOA 11g, weblogic as platform. My question is can we set work managers for different composites like we generally set dispatch policy for proxy services in OSB. Please let me know.
Regards.

Hi
I don't believe you set workmanagers on a composite by composite basis but it may be possible to setup new application scoped work managers in Weblogic although I have never tried this...
Damien

Throtting or Work Managers - OSB @ method level

Would it be possible to throttle a BS or set a work manager for the PS at the WSDL operation level?

Work-manager setup and throttling are two different concepts. Throttling is used to restrict the message flow to a business service however work managers are used to prioritize service work. Remember that in case of throttling there is possibility of message loss however with work manager setup there is no such possibility.
To give an example, suppose you are routing PO ACK's to target system. Given that, latest PO ACK is sufficient to provide the status of PO, it is not mandatory to deliver all the PO ACKs to the target system. So if I have to restrict the flow to target system here, I will use throttling.
If there are two type of messages being processed in your OSB, suppose PO and PO ACK, you will always prefer that PO gets processed on priority and PO ACK processing must not affect the PO processing. Hence here I will use work-manager to prioritize the processing of PO.
Regards,
Anuj

Using work managers to process WorkItems in a message driven bean

Hi, I'm trying to get to grips with using a work manager (in 10.3) to process WorkItems concurrently, with the whole process being triggered by a JMS message. I've got everything working using the default work manager but I'm having problems switching over to using a work manager that I've created myself, using annotations to provide the resource ref.
My current setup, using the default work manager, is (roughly) this:
@MessageDriven(mappedName = "jms/tsrd.DependencyWorker", activationConfig = {
        @ActivationConfigProperty(propertyName = "connectionFactoryJndiName", propertyValue = "jms/connectionFactory"),
        @ActivationConfigProperty(propertyName = "ejbName", propertyValue = "tsrd.DependencyWorker"),
        @ActivationConfigProperty(propertyName = "destinationJndiName", propertyValue = "jms/tsrd.DependencyWorker"),
        @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue") })
@Interceptors(SpringBeanAutowiringInterceptor.class)
public class DependencyWorker implements MessageListener {
    private WorkManager workManager;
    @Required
    @Resource(name = "taskExecutor")
    public void setWorkManager(final WorkManager workManager) {
        this.workManager = workManager;
    public void doOperation(final WorkflowControlMessage msg) throws Exception {
         Work myWork = new ...
         workManager.schedule(myWork, listener);
}With my spring config including this bean:
<bean id="taskExecutor" class="org.springframework.scheduling.commonj.WorkManagerTaskExecutor">
    <property name="workManagerName" value="wm/default"/>
    <property name="resourceRef" value="true"/>
</bean>And this works fine: when the JMS message is received I send a load of WorkItems to the default work manager and they get processed.
Now what I'd like to do is change the spring config to this:
<bean id="taskExecutor" class="org.springframework.scheduling.commonj.WorkManagerTaskExecutor">
    <property name="workManagerName" value="wm/MyWorkManager"/>
    <property name="resourceRef" value="true"/>
</bean>Where I've already created MyWorkManager as a global work manager for the server, and it's visible on the admin server for the deployment.
From the examples I've seen I know I need to add a resource ref for the MDB so that it can lookup the work manager using JNDI. We mainly use annotations, so I'd like to just be able to add this line to the MDB:
@Resource(name = "MyWorkManager", type = commonj.work.WorkManager.class, authenticationType = Resource.AuthenticationType.CONTAINER, shareable = true)But when I try that my server refuses to start:
Unable to deploy EJB: DependencyWorker from tsrd-mdb.jar:
[EJB:011026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment.
weblogic.deployment.EnvironmentException: [EJB:010176]The resource-env-ref 'MyWorkManager' declared in the ejb-jar.xml descriptor or annotation has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor or corresponding annotation.So is there a way to fully configure my work manager just using the @Resource annotation, or do I need to add a weblogic-ejb.jar.xml file and put some specific config in there? Presumably if I do need to add an xml file then I'd need to put something like this in it?
<wls:weblogic-enterprise-bean>
    <wls:ejb-name>DependencyWorker</wls:ejb-name>
    <wls:resource-description>
        <wls:res-ref-name>MyWorkManager</wls:res-ref-name>
        <wls:jndi-name>wm/MyWorkManager</wls:jndi-name>
    </wls:resource-description>
</wls:weblogic-enterprise-bean>Am I also right in thinking that I don't need to add a dispatch policy to the MDB specifying MyWorkManager, because I don't actually want to dispatch the MDB to that manager, I just want the manager to be available to the MDB.
Thanks.

Hi, so I've added a weblogic-ejb.jar.xml file with a reference to the JNDI name of the work manager:
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-ejb-jar xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-ejb-jar" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd http://xmlns.oracle.com/weblogic/weblogic-ejb-jar http://xmlns.oracle.com/weblogic/weblogic-ejb-jar/1.0/weblogic-ejb-jar.xsd">
    <wls:weblogic-enterprise-bean>
        <wls:ejb-name>DependencyWorker</wls:ejb-name>
        <wls:resource-description>
            <wls:res-ref-name>MyWorkManager</wls:res-ref-name>
            <wls:jndi-name>wm/MyWorkManager</wls:jndi-name>
        </wls:resource-description>
    </wls:weblogic-enterprise-bean>
</wls:weblogic-ejb-jar>But I still get exactly the same error when I try to start my server. The example you referred to kind of cryptically suggests that adding a plan.xml suddenly fixed everything, but what am I missing here that actually hooks the work manager up to JNDI? am I getting these problems because I'm using annotations, or are people not supposed to access work managers in this way?
Thanks,
Edited by: 806682 on 05-Nov-2010 08:57

Work managers threads constraint and page cannot be displayed

Hi,
We have a memory intensive processing for certain functionality and we would like to limit the number of parallel requests to process these requests. We are able to acheive configure by using "Work Managers" in WebLogic and putting a limit on the number of threads for that servlet.
For example, if we put maximim thread limit as 3, then if there are 10 parallel requests; 7 requests are in queue. There could be situations where these the requests waiting in queue could take up to 30-40 minutes to be processed.
We are observing that some times we get page cannot be displayed after 15 mins and some times we get this afer 1 hour. Is there a setting in WebLogic that drives page cannot be displayed or is this a browser setting?
Thanks

Hi RAdha,
CRSJavaAdmin.exe is controlled by UCCX node manage servicer, Can you go to the serviceability tool (start - programs - Cisco unified CCX administrator - Cisco Unified CCX serviceability ) and in process ACtivation tab make sure all the services aren enabled specialy "cisco unified CCX administrator" if not enable it and restart the node manager service from the services menu
Hope this helps
Thank you
Anuj

Why do we need work managers if the self-tuning pool is not limited ?

Hi all,
AFAIK, the self-tuning thread pool in WLS 10.3 is not limited in size, meaning it can grow indefinitely.
On the other hand, work managers only make sense when there's a shortage in resources, and we need to decide what are the priorities to get a thread and CPU time.
So if, for example, I have a system that's only 20% busy even on the heaviest load, the work managers will never "kick in" actually, since there's "enough for everyone".
Thanks for sharing your thoughts!

If you have more than a single application deployed and only have the default work manager, all apps compete equally and are also equally unable to be tuned in their thread usage.
If you instead have a unique work manager for each app, you can limit each app's consumption of resources - if needed - or alter each work manager's treatment / tolerance of hogging threads. For instance, an app that maintains sockets versus a webapp.
Having separate workmanagers allows you to tune the apps individually. If needed.

Work Manager both Global Work Managers & Application-scoped Work Managers

Hi all,
I want to use both Global Work Managers & Application-scoped Work Managers in my domain [single], is it possible?
Basically I want to make sure my domain have fix number of thread.
In my environment, I have multiple domains on a single machine, so I want to make sure every domain has fix number of threads to maintain the whole system integrity.
if I won't make sure this, there could be scenario that one particular domain is taking much of the CPU usages than others.
Thanks,
Qumar

Hello Fred,
Thank you very much for reply.
I totally agree with you but in my scenario, I have multiple domains on a single box.
and I am afraid that there could be a situation where one bad application of a particular domain may take most of the CPU usages.
What I can do is: I can define max thread constrain to all the applications of all the domains but it is not acceptable bcz we have hundreds of applications per domain.
So what I want is: to define some kind of thread constrain at the domain level [so that I can have CPU usages allocated to every domain] as well as some kind of thread constrain to few applications [non prioritize].
I tried this by defining Global Work Managers & Application-scoped Work Managers but I found that applications only respect to Application-scoped Work Managers.
or if I have some kind of way that make sure certain percentage of CPU usages is allocated to a particular domain?
hope I have made my self clear.
Thanks,
Qumar

Applicable OSB service points to attach Work Managers

Hi All,
Currently I have an OSB design as below:
I have 3 work managers each having a different fair share class as per their priorities.
I have a single HTTP Proxy service, which takes the hit from all source applications. Based on a DVM and message contents, the proxy determines the priority of the particular request message, and will accordingly route it to one of 3 HTTP proxies (Priority 1 HTTP Proxy, Priority 2 HTTP Proxy, Priority 3 HTTP Proxy). These 3 HTTP Proxy services will then forward the request further to other OSB and target appplication services.
On each of the 3 priority proxy services, I have assigned the appropriate work manager.
However, I am confused on whether to assign a work manager to the exposed HTTP Proxy or not. If I do assign a work manager, whether a fair share request class should be assigned or not. From what I read in oracle documentation, assigning a work manager without fair share class, will assign a fair share of 50 automatically.
What should be done to the exposed HTTP Proxy in order to achieve the prioritization of requests processing.

Hi,
as far as I know there is no standard way of doing this in CRM 7.0.
I imaging it would be possible to call an ERP smartform from CRM by :
- writing an RFC capable function module in ERP that wraps the call of the smartform and returns the generated PDF data.
- writing a function or method in CRM that calls the ERP function module and displays the returned data.
In the lead and opportunity the print preview is done by having a print relevant action in the action profile assigned to the transaction type and I guess for these it should be possible to call a function module by creating an own smart forms method.
But I think this is not possible for an ERP quotation, so you would have to create an own button. In the event handler for this button, one could call the ERP function module and display the result.
Paul

Shared Capacity For Work Managers and state SUSPEND for ManagedServer

Hi!
I have 3 ManagedServers in cluster. I want configure the Overload Conditions for each ManagedServer - set Shared Capacity For Work Managers = 100. So, if the count of concurrent requests will be more than 100 for ManagedServer, this ManagedServer stopes processing new requests (as for sutdown state) and finishes processing the current requests, and all next requests go to a other ManagedServers.
Could you please tell me how to achieve it?
Now, ManagedServer changes state to OVERLOAD temporarily, and becoms to RUNNING.
Failure Action = Suspend this server (dindt help)

You can consider using the capacity constraint
capacity - Causes the server to reject requests only when it has reached its capacity. The default is -1. Note that the capacity includes all requests, queued or executing, from the constrained work set. Work is rejected either when an individual capacity threshold is exceeded or if the global capacity is exceeded. This constraint is independent of the global queue threshold.
Check the below links for more on this:
http://docs.oracle.com/cd/E12839_01/web.1111/e13701/self_tuned.htm#i1060813
http://www.oracle.com/technetwork/articles/entarch/workload-management3-087769.html

Regarding customized layout managers

I need a layout manager which is similar to Null layout+Column layout. ie, there will be a single column of components in the container and the user can move the components from one row to another row.
Someone please tell me how to acheve this. I tried using a BoxLayout but moving of components in the container is not working properly.
Regards,
Varun

Layout Managers have nothing to do with Drag and Drop.
I tried using a BoxLayout but moving of components in the container is not working properly.Well, then you are doing something wrong. Using a new layout manager won't solve the problem.
Your code needs to:
a) remove the component from the container
b) drag the component around the screen (I would use a LayeredPane for this
c) add the component back to the container at the correct position
d) revalidate the container to is get layed out correctly.

Query regarding Job work senario in India

dear all,
i am facing a strange problem
i m having some Customer who sent material on (4)(5) a or 57F4 challan for job work. In that case only labour charges are charged no excise duty will charged, but how i will take the material "in" in to system,from which transaction code and which movement type i used. Also the storage location should be different for that ?
It Dose not hit the RG1 Register.
can any body help me to solve this
please please solve the problem
regards
pankaj
[email protected]

Dear Pankaj
1. Then i will suggest to use DIEN Material type , which will not be valuated, as
it is customer's stock
2. Then you recieve the material from Customer, which is non-valuated.
This you can do in MIGO.
3 Then you make a production order with BOM, where component will
be material given by customer and FG will be Material you are going
to send along with byproducts.
3. Once material is process(or produced) then you can make a seperate jobwork sales order type and deliver it
4. Finally bill it for services rendered.
If you use Services you will not get stock of customer's material in the system.
But if you use non valuated material you can get the stock. So ask if stock
is required???
As no excise entries are required you need no worry about CIN part
I hope it is clear....
Regards
Jitesh

Regarding COMMIT WORK

Hi,
I am using two BAPIs 'BAPI_ACC_ACTIVITY_ALLOC_POST' and 'BAPI_NETWORK_CONF_ADD' in my custom function module. These two BAPIs are used as explained below:
1) Fisrt the BAPI 'BAPI_ACC_ACTIVITY_ALLOC_POST' is called. If sy-subrc NE '0', the error messages are read.
2) Then the BAPI 'BAPI_NETWORK_CONF_ADD' is called. If sy-subrc NE '0', its error messages are read.
3) If there is no error for the two BAPIs called above, then the actual posting is done by calling the BAPI
'BAPI_ACC_ACTIVITY_ALLOC_POST'. If sy-subrc EQ 0, Commit work.
I would like to know if the Commit work in third step will commit the changes of the steps 1 and 2 as the the statement COMMIT WORK completes the current SAP LUW.
Or will it commit the step 3 only.
Thanks & Regards,
Soumya.

Hi soumya,
you can rollback for the step 1& 2 if sy-subrc ne 0.
and then use the comit work if sy-subrc eq 0 for step 3.
Hope this will help you.
regards,
Phani.

Regarding Universal Work Flow

Hi all
we are making use of universal work flow where when the publisher publishes the item is there any possibility to trigger any java code since we want to make use of that information in our WebDynpro java code.
please help us in this regard
from
Prasad.

Hello Varaprasad,
Do you mean using the UWL API. yes this is possible. you will find the javadocs for the api at https://help.sap.com/javadocs/NW04S/SPS09/uw/index.html
hope that helps
Abdul

Regarding tables work area,events in reporting,LSMW

Hai to All,
1. Sequence of events in classical & interactive reporting.
2. Why call transaction does not support LSMW
(Legasy System Migration Workbench)
3. We have to provide tables work area in the declaration when select-options logic is used but it is not mandatory in parameters selection screen logic why?
4. what is the reason for maintaining <b>loop ... endloop</b> logic under PAI in the case of table control
please provide answers for these quections
regards,
suryanarayana k.

Hi
1. Sequence of events in classical & interactive reporting.
Events in ABAP Programming
Classical Reporting:
INITIALIZATION
AT SELECTION-SCREEN OUTPUT
AT SELECTION-SCREEN
START-OFSELECTION.
TOP-OF-PAGE
END-OF-PAGE
END-OF-SELECTION.
Events in Interactive Report
TOP-OF-PAGE DURING LINE-SELECTION
AT USER-COMMAND.
AT LINE-SELECTION
AT PF-FUNCTION KEY
2. Why call transaction does not support LSMW
(Legasy System Migration Workbench)
http://www.sapbrain.com/TOOLS/LSMW/SAP_LSMW_steps_introduction.html
http://esnips.com/doc/8e732760-5548-44cc-a0bb-5982c9424f17/lsmw_sp.ppt
http://esnips.com/doc/f55fef40-fb82-4e89-9000-88316699c323/Data-Transfer-Using-LSMW.zip
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI.ppt
http://esnips.com/doc/7582d072-6663-4388-803b-4b2b94d7f85e/LSMW.pdf
for Long texts Upload
Please take a look at this..
http://help.sap.com/saphelp_erp2005/helpdata/en/e1/c6d30210e6cf4eac7b054a73f8fb1d/frameset.htm
3. We have to provide tables work area in the declaration when select-options logic is used but it is not mandatory in parameters selection screen logic why?
When youd eclarae select-options by default it creates a selection table with 4 fields called SIGN,OPTIOn,LOW and HIGH fields
Paramters its' not like that
4. what is the reason for maintaining loop ... endloop logic under PAI in the case of table control
Table control means handling multiple records , so to process/handle them it is a must to use loop.endloop.
Reward points for useful Answers
Regards
Anji

Help regarding dialog work process

hello experts,
In S.A.P abap or abap+java,why we need atleast 2 dialog work process.Is that 2 dialog work process are used for any extra functions?

Hi,
it is mandatory to have two dialog work processes within an ABAP-Instance.
There is no way around.
It is the same for enqueue process, you have to have exactly one for your ABAP system.
(Remember: an ABAP system can persist of many instances, but only one central instance).
Hope, this is helpful.
Kind regards,
Achim
P.S. Never the less, this is the wrong Forum for your question.

Regarding wlss work managers

Similar Messages

Maybe you are looking for