Query Regarding Execute Thread Count

Hi,
My understanding of Execute Thread Count is the threads which are assigned to service
requests coming to Weblogic Server.
In our current architecture a request for generating report is directed to EJB method
which makes a call to another Server (Report Server for executing reports), the report
Server in turn calls the EJB residing on Weblogic Server for getting the data.
So, is my assumption correct that with our current architecture we are limited to
concurrency of Execute Thread Count -1. (Every request for report will consume 2
Excute threads, and others will have to wait till the first request gets completed
and 2 threads are freed).
I also read from the postings that Weblogic takes some of the threads, so it actually
will be limited to (Execute thread count - Weblogic Held- 1).
Please corect me if I am wrong.
Thanks and Regards
Rashmi

Hi,
Thanks very much for the suggestion. I tried, and it is using 2 Execute Threads.
Thanks
Rashmi
"Dave Martin" <[email protected]> wrote:
>
Rashmi:
If you are interested in answering the question rigorously, why not just
throw a
fake exception along both the report generation path and the runReport method
of
the ReportServer, then record their stack traces to a file for comparison?
From the sounds of it, your app wants to make the actual report generation
asynchronous
from the post of the reporting request. If they're really asynchronous,
then your
ReportServer must have some kind of blocking queue that will "wake up" when
it has
work to be done. Depending on how you implemented this, your runReport
method may
not be running a WebLogic execute thread at all.
Seems to me that you should be thinking of this as consuming one execute
thread regardless.
Even if the two pieces of work are asynchronous, the first thread finished
its work
at the point that it posts to the second thread (at least, per your description).
So at any one time, at max one execute thread is being consumed per request.
But capture the stack traces and have a look for yourself.
Dave Martin
"Rashmi S" <[email protected]> wrote:
Hi,
Thanks for your reply.The reason why I say 2 threads will be consumed is
as follows
1. First execute thread will be used for the request to Weblogic Server
to run the
report originating from a client.
2. Now, within the ReportServices EJB there is a call to Report Serverto
run the
report. The running of report is done on the Report Server which is ona
separate
m/c. Within the runReport method of the Report Server ,the data is fetched
for the
report by making a context look-up of another session EJB which fetches
the data.
So, the second Execute thread will be consumed for executing the EJB that
fetches
the data.
Am I correct?
Thanks and Regards
Rashmi
"Cameron Purdy" <[email protected]> wrote:
Incoming requests (from outside the server) use one thread for the duration
of their processing. Previous to their processing they are queued until
a
thread is available. So you would use one thead per concurrent request,
not
two. Otherwise, it sounds right.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Rashmi S" <[email protected]> wrote in message
news:[email protected]...
Hi,
My understanding of Execute Thread Count is the threads which are assignedto service
requests coming to Weblogic Server.
In our current architecture a request for generating report is directedto EJB method
which makes a call to another Server (Report Server for executingreports), the report
Server in turn calls the EJB residing on Weblogic Server for getting
the
data.
So, is my assumption correct that with our current architecture we arelimited to
concurrency of Execute Thread Count -1. (Every request for report willconsume 2
Excute threads, and others will have to wait till the first request
gets
completed
and 2 threads are freed).
I also read from the postings that Weblogic takes some of the threads,so
it actually
will be limited to (Execute thread count - Weblogic Held- 1).
Please corect me if I am wrong.
Thanks and Regards
Rashmi

Similar Messages

How do you modify the default Execute thread count in Weblogic Server 9.2?

How do you modify the default Execute thread count in Weblogic Server 9.2?
How can you tune the starting number of weblogic.ExecuteThread on server startup and/or set minimum number?
Is there an option from the console?
Please let me know.
Thanks

Self tuning will automatically manage the threads but however you can still control the min and max by adding the min and max values for each instance either directly adding in config.xml or through JVM settings
1) Modifying the config.xml
Just add the following line(s) to each server definition :
<server>
<name>AdminServer</name>
<self-tuning-thread-pool-size-min>100</self-tuning-thread-pool-size-min>
<self-tuning-thread-pool-size-max>200</self-tuning-thread-pool-size-max>
</server>
2) Adding some JVM parameters
It's safer the following way :
add the following option in your command line : -Dweblogic.threadpool.MinPoolSize=100
Regards
RR

Change the Execute Thread Count im weblogic9.2

Hi
I am trying to change the execute thread count in weblogic 9.2 but i am not able to find the location in weblogic Console to change it can any one help me

Hi,
In previous versions of WebLogic Server, processing was performed in multiple execute queues. Different classes of work were executed in different queues, based on priority and ordering requirements, and to avoid deadlocks. In addition to the default execute queue, weblogic.kernel.default, there were pre-configured queues dedicated to internal administrative traffic, such as weblogic.admin.HTTP and weblogic.admin.RMI. Now the Same thing is done using WorkManagers...
WebLogic Server, Version 8.1 implemented Execute Queues to handle thread management which allowed you to create thread-pools to determine how workload was handled. WebLogic Server still provides Execute Queues for backward compaitibility, primarily to facilitate application migration. However, new application development should utilize Work Managers to peform thread management more efficiently.
You can enable Execute Queues in the following ways:
* Using the command line option*
-Dweblogic.Use81StyleExecuteQueues=true
So in that Case ...*config.xml* entry will be like this:
<server>
<name>AdminServer</name>
<execute-queue>
<name>weblogic.kernel.Default</name>
<queue-length>256</queue-length>
</execute-queue>
<use81-style-execute-queues>true</use81-style-execute-queues>
<listen-port>7001</listen-port>
<web-server>
<web-server-log>
<file-name>../../logs/admin_access.log</file-name>
</web-server-log>
</web-server>
<listen-address>aaa.bbb.com</listen-address>
</server>
for more detailed Information Please refer to:
http://download.oracle.com/docs/cd/E11035_01/wls100/config_wls/self_tuned.html
Edited by: Jay SenSharma on Jan 20, 2010 3:42 PM

Configuring Execute Thread Count

Hi,
I am working on a webapp thats using Weblogic 8.1 (SP2) as the application server.
The admin server for Weblogic currently provides 2 execute threads as default.
However I was wondering if I can configure the admin server for a higher number
of execute threads.
I have the following questions:
1.> Does configuring the number of threads for the admin sever provide any additional
value? has any one come across a big application where more than 2 execute threads
are required for the admin server?
2.> If yes, is it possible to configure the number of execute threads for the
admin server? I did some search on the bea website and didnt find anything that
explicitly says that the property is configurable. Is this true?
3.> If it is configurable, then how do we go about setting it up?
If anyone has worked around this and can provide me with any information or references,
that would be great.
Thanks

          Sriram,
          Take a look at the following URL for setting the thread count in WLS 6.1
          http://edocs.bea.com/wls/docs61/perform/WLSTuning.html#1112343
          Chuck Nelson
          Developer Relations Engineer
          BEA Technical Support

Query regarding new threads being spawned during rollback operation

Hi,
During a DB operation there are stuck threads that arise because of long time taken to execute the DB operation.
The STUCK thread is acquiring lock on the database driver..
My Queries are:::
Will container create new threads to rollback transaction?
There is a parameter recover only once in xa params.. ? What is the default value for this parameter and is it recommended to use?
Edited by: $vicky$ on May 11, 2010 10:23 AM

Could you check your transaction timeout attribute of your JTA environment and compare this to the server's stuck thread time (configuration health tab). If your transaction time-out is higher than the stuck thread time you must make some adjustments here.
If you are using EJB's and container managed transactions you set the transaction time-out of a particular EJB in the weblogic-ejb.jar deployment override, for example
<weblogic-enterprise-bean>
<ejb-name>MyEJB</ejb-name>
<transaction-descriptor>
<trans-timeout-seconds>100</trans-timeout-seconds>
</transaction-descriptor>
</weblogic-enterpise-bean>
In addition you can use a custom workmanager - to configure the stuck thread time for a particular EJB, for example, (this can also be configured by using the console environment --> work managers)
<work-manager>
<name>VoorbeeldWorkManager</name>
<response-time-request-class>
<name>VoorbeeldRequestClass</name>
<goal-ms>1000</goal-ms>
</response-time-request-class>
<max-threads-constraint>
<name>VoorbeeldConstraint</name>
<count>100</count>
</max-threads-constraint>
<capacity>
<name>VoorbeeldCapacity</name>
<count>100</count>
</capacity>
<work-manager-shutdown-trigger>
<max-stuck-thread-time>300</max-stuck-thread-time>
<stuck-thread-count>5</stuck-thread-count>
</work-manager-shutdown-trigger>
</work-manager>
By using a dispatch policy you can couple this to your EJB
<weblogic-enterprise-bean>
<ejb-name>MyEJBk<ejb-name>
<dispatch-policy>VoorbeeldWorkManager</dispatch-policy>
</weblogic-enterprise-bean>

High thread count on store.exe

I understand that the mdb store process utilizes as much memory as is available. My question is regarding the thread count on the process. One of the three mailbox servers tends to have a higher thread count than the other two. It
usually ranges from 150 to 200 (while the other two are usually 130 to 150) but today it is a little over 300. The rpc thread count on all the mailbox servers stays pretty low (60 or under) and the rpc thread count on the CAS servers usually
hang out around 55-65, so that's all good. All three mailbox servers also use VERY close to the same amount of memory all the time, so that doesn't seem to be making a difference. I am just trying to determine why the thread count is noticably
higher. This server and one of other mailbox servers replicate the public folder database, and I can understand why that would account for some additional activity, but you would think the thread count would be higher on the other server with the public
folder database as well, but it stays pretty low. Hardware-wise these servers are all identical. So is there something I can monitor in perf mon for instance? I don't want to use experfwiz because that monitors everything under the sun and
I need it a bit more centralized. I have googled all over the place and the only thing I can find is that with newer versions of exchange this thread count ranges from 200-300 on heavy usage, and exch07 can handle up to 500 threads, so I can't even find
which specific things to monitor that directly correlate with this issue. So while I understand that it's not really too high, I would like to find out why it deviates from the norm if the other two servers are equal for all intents and purposes (same
hardware, balanced DAG. etc). I would like to mitigate any potential issues. Thank you.

Hi pchw,
Thank you for your question.
I am sorry that we could not find the specific things to monitor this issuer directly, because there are many reason which caused it. For example: virus, big size attachment in queue, hardware performance and so on. We could refer to the following steps
to troubleshoot:
Restart the service of “Microsoft Exchange transport”;
Create a new database and move mailbox to new mailbox;
We could do some disk health check if the load test is normal;
Collect related application log and system log to
[email protected] for our troubleshooting.
We could run SDP on Exchange server and send it to
[email protected] for our troubleshooting.
http://blogs.msdn.com/b/askie/archive/2012/05/22/introduction-to-support-diagnostics-platform-sdp.aspx
We could use tools and logs to analysis if there are anything wrong or abnormal on Exchange server 2013. our bottle neck is disk IO latency, store.exe do require some CPU usage, but if our disk IO speed can keep in a normal range, the
CPU usage will be smaller. Exchange is highly rely on disk IO performance because it need lots of IO operation regarding to transaction log and database file. If Disk IO has a high latency, I will definitely impact store.exe, if it`s getting seriously sometimes
it may cause store.exe no response.
We could refer to the following link:
https://technet.microsoft.com/en-us/library/ee832791(v=exchg.141).aspx
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim

Execute queue thread count set back?

I have a script which automatically sets up execute queues (and their thread counts) for either an admin server or two managed servers in a cluster (depending on whether it's a standalone deployment). Upon building a domain, the script connects to a temporary server and sets everything up, at this point it appears all the queues and thread counts are set correctly. However once the build has completed and the generated config.xml is checked, three queues don't have any thread counts associated with them at all; these queues are:
ThreadQueue (Count)
wli.internal.ProcessInstanceInfo (15)
wli.internal.ProcessTracking (15)
wli.process.event.thread.pool (15)
The other queues have all their thread counts set correctly. Does anybody know how these queues are used and if this will have an impact on the above problem?

No worries about this post, the reason has been solved.
Reason
The default thread count for execute queues in development mode is 15 threads, therefore if a queue is specified with this value it won't be set in the config.xml (when an execute queue doesn't have a ThreadCount attribute, the default is used instead). The trouble is that when the server is started we enter production mode where the default thread count is 25 threads instead.

Query regarding G/LAccounts in psoting

Hi Experts,
I have one query regarding PCP0.
After executing PCP0,If We double click on the posting document we can see the number of G/L accounts in that posting Document.If we double click on each G/L Account it shows all the revision information indetail for all payments cumulated into that particular G/L Account.
Some of the G/L's are appearing as single line in the posting document and if we double click for the revision information it is showing all the Wagetypes with personnel numbers and the total of each wagetype.
Some of the G/L's we can see Multiple times for each individual.
Can any one please explain where does we set up the the revision information for the G/L Accounts .
Appreciate If anyone can help to know this information.
Thanks & Regards,
Sandhya.

Hi Gopal,
Counting class are assigned to the Periodic work Schedule 1 to 9 are just arbitart sequence numbers and have no meaning in general they are used for linking Pweriodic Work schedules with differences.
You can use the class for absence and attendance counting to specify different methods of counting according to the period work schedule.
They have no other meaning apart from that.
Thanks and Regards
Swati

Query regarding WorkManager

Hi All,
I would like to know the following:
1.What is the maxthread constraint associated with a default workmanager?
2.If an mq or jms proxy service invokes an SB layer(proxy service with sb prootocol) where all the layers are associated with default workmanager(MQ---SB), what will be the resultant no of max threads in sb layer(Assuming for mq/jms ..the maxthread is 16 by default since those get deployed as a MDB internally, will the sb layer also get restricted to 16 thread count?)
3. If the polling proxy service layer is associated with a custom workmanager say with max thread constraint 8, is the understanding correct that the polling proxy service can pick 8 concurrent messages at a time and once all the threads are freed it will go an pick the next set of 8 messages or as and when the thtreds get free…however at any given time the total no of threads for that proxy service won’t exceed the count of 8?
Thanks & Regards
kshama

Ansuwer to Q1.
max-threads-constraint—Limits the number of concurrent threads executing requests from the constrained work set. The default is unlimited. For example, consider a constraint defined with maximum threads of 10 and shared by 3 entry points. The scheduling logic ensures that not more than 10 threads are executing requests from the three entry points combined.
You can define a max-threads-constraint in terms of a the availability of the resource that requests depend upon, such as a connection pool.
A max-threads-constraint might, but does not necessarily, prevent a request class from taking its fair share of threads or meeting its response time goal. Once the constraint is reached the server does not schedule requests of this type until the number of concurrent executions falls below the limit. The server then schedules work based on the fair share or response time goal.
min-threads-constraint—Guarantees the number of threads the server will allocate to affected requests to avoid deadlocks. The default is zero. A min-threads-constraint value of one is useful, for example, for a replication update request, which is called synchronously from a peer.
A min-threads-constraint might not necessarily increase a fair share. This type of constraint has an effect primarily when the server instance is close to a deadlock condition. In that case, the constraint will cause WebLogic Server to schedule a request even if requests in the service class have gotten more than its fair share recently.

Thread count higher than max worker threads... Large number of suspended worker threads

I have a SQL 2012 SP2 server that is getting High Thread count alerts in SCOM. looking into the issue I found some interesting things that I am now at a loss for. I have been searching around for a few hours now and havent found much other than
making it more confusing. I found this MSDN blog:
Are my actual worker threads exceeding the sp_configure 'max worker threads' value?
Running through that I found some interesting things.
-Max worker threads is set to default for x64 of 512 threads
running a thread count query found 547 current worker threads:
SELECT
SUM(current_workers_count) as [Current worker thread] FROM sys.dm_os_schedulers
Taking it a step further found that there was 523 worker threads in a suspended state with a last_wait_type of MISCELLANEOUS:
select is_preemptive,state,last_wait_type,count(*) as NumWorkers from sys.dm_os_workers
Group by state,last_wait_type,is_preemptive
order by count(*) desc
is_preemptive state last_wait_type NumWorkers
0 SUSPENDED MISCELLANEOUS 523
This is not yet a production server, no one is connecting to the database and the front end software application is not being used on this server yet. Essentially this is just an idle database server so I thought it might be a fluke, so I restarted
the sql services and the thread counts cleared. I left it alone and overnight the high thread count alert popped back up. I looked at it again this morning and the exact same thing happend. Same number of suspended workers etc and total worker
threads of 523 and 547 respectively.
Other than the one article I have found above I have not been able to find anything to help explain this or what the heck suspended miscellaneous worker threads are. Any help would be appreciated...Thanks!

Hello,
Please run the following query. The text column should tell us what is running.
SELECT
task.task_address,
task.parent_task_address,
task.task_state,
REQ.request_id,
REQ.database_id,
REQ.session_id,
REQ.start_time,
REQ.command,
REQ.connection_id,
REQ.task_address,
QUERY.text
FROM
SYS.dm_exec_requests
req
INNER
JOIN sys.dm_os_tasks
task on
req.task_address
= task.task_address
or req.task_address
= task.parent_task_address
Cross
apply sys.dm_exec_sql_text
(req.sql_handle)
as query
WHERE
req.last_wait_type
= 'MISCELLANEOUS'
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

A query regarding synchronised functions, using shared object

Hi all.
I have this little query, regarding the functions that are synchronised, based on accessing the lock to the object, which is being used for synchronizing.
Ok, I will clear myself with the following example :
class First
int a;
static int b;
public void func_one()
synchronized((Integer) a)
{ // function logic
} // End of func_one
public void func_two()
synchronized((Integer) b)
{ / function logic
} // End of func_two
public static void func_three()
synchronized((Integer) a)
{ // function logic
} // End of func_three, WHICH IS ACTUALLY NOT ALLOWED,
// just written here for completeness.
public static void func_four()
synchronized((Integer) b)
{ / function logic
} // End of func_four
First obj1 = new First();
First obj2 = new First();
Note that the four functions are different on the following criteria :
a) Whether the function is static or non-static.
b) Whether the object on which synchronization is based is a static, or a non-static member of the class.
Now, first my-thoughts; kindly correct me if I am wrong :
a) In case 1, we have a non-static function, synchronized on a non-static object. Thus, effectively, there is no-synchronisation, since in case obj1 and obj2 happen to call the func_one at the same time, obj1 will obtain lock for obj1.a; and obj2 will obtain lock to obj2.a; and both can go inside the supposed-to-be-synchronized-function-but-actually-is-not merrily.
Kindly correct me I am wrong anywhere in the above.
b) In case 2, we have a non-static function, synchronized on a static object. Here, again if obj1, and obj2 happen to call the function at the same time, obj1 will try to obtain lock for obj1.a; while obj2 will try to obtain lock for obj2.a. However, since obj1.a and obj2.a are the same, thus we will indeed obtain sychronisation.
Kindly correct me I am wrong anywhere in the above.
c) In case 3, we have a static function , synchronized on a non-static object. However, Java does not allow functions of this type, so we may safely move forward.
d) In case 4, we have a static function, synchronized on a static object.
Here, again if obj1, and obj2 happen to call the function at the same time, obj1 will try to obtain lock for obj1.a; while obj2 will try to obtain lock for obj2.a. However, since obj1.a and obj2.a are the same, thus we will indeed obtain sychronisation. But we are only partly done for this case.
First, Kindly correct me I am wrong anywhere in the above.
Now, I have a query : what happens if the call is made in a classically static manner, i.e. using the statement "First.func_four;".
Another query : so far we have been assuming that the only objects contending for the synchronized function are obj1, and obj2, in a single thread. Now, consider this, suppose we have the same reference obj1, in two threads, and the call "obj1.func_four;" happens to occur at the same time from each of these threads. Thus, we have obj1 rying to obtain lock for obj1.a; and again obj1 trying to obtain lock for obj1.a, which are the same locks. So, if obj1.a of the first thread obtains the lock, then it will enter the function no-doubt, but the call from the second thread will also succeed. Thus, effectively, our synchronisation is broken.
Or am I being dumb ?
Looking forward to replies..
Ashutosh

a) In case 1, we have a non-static function, synchronized on a non-static object. Thus, effectively, there is no-synchronisationThere is no synchronization between distinct First objects, but that's what you specified. Apart from the coding bug noted below, there would be synchronization between different threads using the same instance of First.
b) In case 2, we have a non-static function, synchronized on a static object. Here, again if obj1, and obj2 happen to call the function at the same time, obj1 will try to obtain lock for obj1.a; while obj2 will try to obtain lock for obj2.a.obj1/2 don't call methods or try to obtain locks. The two different threads do that. And you mean First.b, not obj1.b and obj2.b, but see also below.
d) In case 4, we have a static function, synchronized on a static object. Here, again if obj1, and obj2 happen to call the function at the same time, obj1 will try to obtain lock for obj1.a; while obj2 will try to obtain lock for obj2.a.Again, obj1/2 don't call methods or try to obtain locks. The two different threads do that. And again, you mean First.b. obj1.b and obj2.b are the same as First.b. Does that make it clearer?
Now, I have a query : what happens if the call is made in a classically static manner, i.e. using the statement "First.func_four;".That's what happens in any case whether you write obj1.func_four(), obj2.func)four(), or First.func_four(). All these are identical when func_four(0 is static.
Now, consider this, suppose we have the same reference obj1, in two threads, and the call "obj1.func_four;" happens to occur at the same time from each of these threads. Thus, we have obj1 rying to obtain lock for obj1.aNo we don't, we have a thread trying to obtain the lock on First.b.
and again obj1 trying to obtain lock for obj1.aYou mean obj2 and First.b, but obj2 doesn't obtain the lock, the thread does.
which are the same locks. So, if obj1.a of the first thread obtains the lock, then it will enter the function no-doubt, but the call from the second thread will also succeed.Of course it won't. Your reasoning here makes zero sense..Once First.b is locked it is locked. End of story.
Thus, effectively, our synchronisation is broken.No it isn't. The second thread will wait on the same First.b object that the first thread has locked.
However in any case you have a much bigger problem here. You're autoboxing your local 'int' variable to a possibly brand-new Integer object every call, so there may be no synchronization at all.
You need:
Object a = new Object();
static Object b = new Object();

Query regarding Cluster nodes in CC

Hi Experts,
We have a query regarding the cluster nodes available in the CC monitoring.
Can two nodes of a same channel can poll at the same time?
Kindly suggest what should be done to make a specific cluster node of a CC polls at a particular time.
Thanks
Suganya.

Hi,
There is an answered thread on this
Processing in Multiple Cluster Nodes
Regards,
Manjusha

Thread count tuning

Hi!
We are running a weblogic 5.1 server for jsp/servlet/ejb behind an apache web
server, via the wls/apache bridge. As the number of users increased we expereienced
slow response times. We checked thread dumps from peak hours and saw that all
servlet threads were busy writing to network sockets. Still, if we check the internet
line usage, we are not using up all our bandwith.
We've managed to solve this by adding more threads to our wls server (36 servlet
threads, 46 totally). This has however slowed down our database somewhat since
we have to increase the connection pool size with the number of server threads.
So my question would be: is there some other, more elegant, way to solve this?
Having 46 execute threads seems pretty much (15 is recommended from BEA). Ideally
I would like the wls threads to write their results as quickly as they can to
the apache server, disconnect from the socket and leave actual work of writing
all the data back to the end user's browser to apache. My network knowledge is
pretty limited so I'm not sure if this is possible.
/Mattias

Why do you need to have the maximum thread count equal to the maximum number of simulatneous users? You'll never end up with a system that has 60,000 threads.
If you are doing traditional-style HTTP, then typically you can support many thousands of users with just a few threads. For example, our SPECjAppServ er submissions use about 40 threads to handle 4000 clients. It all depends on how many requests each client actually makes per second, and how long each request takes. If the clients are idle for long periods of time, you could handle 10s of thousands with just a few threads.
The keep-alive tuning is also critical in that scenario, as the server will eventually start disconnecting clients, who will re-create the TCP connections. That works seemlessly from a functional point of view, but isn't necessarily the optimal thing for performance.
On the other hand, if you're trying to use a Web 2.0-style HTTP request where you simulate server pushes by having the servlet request block, then yes, in 8.1 you will need one thread per client, but you'll be bound by OS and other system constraints on the number of threads the process can have. You'd be much better off in that case using the Asynchronous Request processing features being added to AS 9.1 (see Sun's project glassfish for details).
For information on configuring the thread count for 8.1, see:
http://docs.sun.com/source/819-0215/httpservice.html
In particular -- the section on Configuring HTTP Service Request Processing Threads.

Query regarding App V Deployment - (Deploying DriverMSI in App - V)

Hi All,
This is my query regarding deployment of a driver MSI using App V. I have tried sequencing "NMap software" which has Kernel driver as service. I have separated the Kernel driver and wrapped in an MSI and tried deploying the Kernel Driver MSI using
the DeploymentConfig.xml file but its not happening.
I have tried writing script in DeploymentConfig.xml in AddPackage Tag as shown in the below commands where I have added driver MSI in sequenced package, and tried deploying the DeploymentConfig.xml in powershell during Add-Package event but the driver
MSI is not getting installed in Client machine.
<AddPackage>
        <Path>msiexec.exe</Path>
        <Arguments>/i Nmap_KernelDriver.msi /qb /l*v c:\windows\system32\LogFiles\Install_Nmap.log</Arguments>
        <Wait RollbackOnError="true" Timeout="30"/>
      </AddPackage>
      <RemovePackage>
        <Path>msiexec.exe</Path>
        <Arguments>/x {4BAB3E93-716E-4E18-90F0-1DA3876CBEB6} /qn</Arguments>
        <Wait RollbackOnError="false" Timeout="60"/>
      </RemovePackage>
    </MachineScripts>
The other way I have tried is writing a vbscript for installing the driver MSI, added the vbs in sequenced package and called the same in DeploymentConfig.xml but no luck.Please find the command below.
<!--
    <MachineScripts>
      <PublishPackage>
        <Path>wscript.exe</Path>
        <Arguments>[{AppVPackageRoot}]\..\Scripts\NMap_Driver_Install.vbs -guid 7c21d1e9-0fc4-4e56-b7bf-49e54d6e523f -name Insecure_Nmap_6.4_APPV</Arguments>
        <Wait RollbackOnError="true" Timeout="30"/>
      </PublishPackage>
      <UnpublishPackage>
        <Path>\\server\share\barfoo.exe</Path>
        <Arguments>-WithArgs</Arguments>
        <Wait RollbackOnError="false" Timeout="30"/>
      </UnpublishPackage>
Please suggest any method to make this successful or kindly let me know if there is any mistake in the script.
Thanks in advance,
Vivek V

Hi Nicke,
These are the following methods and steps that I have performed for installing Driver MSi.
Method 1:
1. Included the driver MSI in Package Files Tab in sequencer and called the same MSI in DeploymentConfig.xml using the below script.
<AddPackage>
        <Path>msiexec.exe</Path>
        <Arguments>/i Nmap_KernelDriver.msi /qb /l*v c:\windows\system32\LogFiles\Install_Nmap.log</Arguments>
        <Wait RollbackOnError="true" Timeout="30"/>
      </AddPackage>
      <RemovePackage>
        <Path>msiexec.exe</Path>
        <Arguments>/x {4BAB3E93-716E-4E18-90F0-1DA3876CBEB6} /qn</Arguments>
        <Wait RollbackOnError="false" Timeout="60"/>
      </RemovePackage>
    </MachineScripts>
2. After the above steps, deployed the AppV package along with DeploymentConfig.xml in App V Client using the commands mentioned below.
Set-ExecutionPolicy -Unrestricted
Import-module Appvclient
Set-AppVClientConfiguration -EnablePackageScripts 1
Add-AppvClientPackage -Path "Path of the AppV file" -DynamicDeploymentConfig "Path of DeploymentConfig.xml"
after trying the above steps the driver MSI is not getting installed.
Method 2:
1. Included the driver MSI and a VBS file(VBS contains script for calling the driverMSI)in Package Files tab in sequencer. Commandlines has been provided calling the vbs file in DeploymetConfig.xml as mentioned below.
<!--
    <MachineScripts>
      <PublishPackage>
        <Path>wscript.exe</Path>
        <Arguments>[{AppVPackageRoot}]\..\Scripts\NMap_Driver_Install.vbs -guid 7c21d1e9-0fc4-4e56-b7bf-49e54d6e523f -name Insecure_Nmap_6.4_APPV</Arguments>
        <Wait RollbackOnError="true" Timeout="30"/>
      </PublishPackage>
      <UnpublishPackage>
        <Path>\\server\share\barfoo.exe</Path>
        <Arguments>-WithArgs</Arguments>
        <Wait RollbackOnError="false" Timeout="30"/>
      </UnpublishPackage>
2. after executing the above steps, tried deploying the AppV file along with DeploymentConfig.xml using the commands mentioned below,
Set-ExecutionPolicy -Unrestricted
Import-module Appvclient
Set-AppVClientConfiguration -EnablePackageScripts 1
Add-AppvClientPackage -Path "Path of the AppV file" -DynamicDeploymentConfig "Path of DeploymentConfig.xml"
evenafter trying the above methods the driver MSI is not getting installed. Hope you can understand my explanations above.
Regards,
Vivek V

Select the Key Figures to be presented in a query before execute the it

Hi,
I want to select(through checkbox) the Key Figures to be presented in a query before executing the query. I'm creating BEX queries and web templates (I'm working on BEX 7.0).
I haven't found clear post about this so if you have implemented something like this please help me and share your solution.
Kind regards,
Ana

Hi,
If you set a property of your KF as "Hide and can be shown", you will get a filter option for these KFs after executing the report in the navigational block of web report.
When you click on that filter, you will get the list of KFs, then you can select the desired KFs using check box.
Regards,
Yogesh.

Query Regarding Execute Thread Count

Similar Messages

Maybe you are looking for