Paging large results?? - Woodstock + Provider Framework

I'm using the Table & TableRowGroup components out of the com.sun.webui.jsf.component package. I created a table backed by an ObjectListDataProvider. Since my query will literally return thousands of very large objects, I must implment the provider in such a way that the internal list it wraps only has a page of that data at a time.
In order to do this, I need to make sure that whenever the user clicks on one of the buttons on some pagination control (page forward, page backward) that the server-side backing UIComponent object gets that updated state.
I'm already sure that the refresh method on my provider is executing after the ApplyRequestValues phase, but it seems that those state values aren't updated. The UI shows that the page number is moving forward and backward, but the backing UIComponent still shows page=1.
I've looked at the source for the TablePaginationActionListener, and it seems to respond to the table events of interest (all pagination events), but I don't see how to attach this listener to the table. The javadoc in the class says that it should be attached to the Table component using addActionListener, but I do not see that method available on the Table.
I even tried adding the listener as a child <f:actionListener> tag. For completeness sake, I tried nesting this tag in the Table, the TableRowGroup, and the TableColumn - but all of them threw exceptions because it's not a valid child tag. So I have no idea how to attach this listener to the table to make sure the server-side model values will stay fresh.
I want to use the provider framework, but I can't afford to load all of the table data into memory. I need to be able to have the provider contain a single page of data at a time, and for the server-side UIComponent to always be up-to-date (so that my refresh method on the provider always knows which page of data to get from my backing Session Facade).
Am I using the wrong provider? Is there something fundamental I'm misunderstanding? I'm using 4.0.1 stable release of Woodstock.
Regards,
-joseph

Well the server right now is a 32-bit VM machine, so the memory limit is 1400m on -XMX setting. We are upgrading from the one production machine to 2 production machines with 2 instances of Jboss and 16gb of memory each machine. So each Jboss would theoretically have 7750mb of memory, leaving 512mb for Windows 2003 64-bit. It will help the problem, but only delay capacity.
Sometimes our data is the exact same, and we are loading it for each user. We may go out and get all the routes for all of our trucks, and refresh that every 5 minutes for each user. Even that piece is taking up probably 2-3mb per user...so if we could streamline that it would help.
What can you recommend for having a central cache of data say on our Jboss server that we update say every 5 minutes, and multiple users could access it? I was looking into EJB 3.0, but they are a little confusing when it comes to persistence, and I have not found a good example of a bean holding a cache of data, and having a way to refresh every X minutes.
How much memory can JVM take up for the heap on a 64-bit machine?

Similar Messages

How to handle large result set of a SQL query

Hi,
I have a question about how to handle large result set of a SQL query.
My query returns more than a million records. However, the Query Template has a "row count" parameter. If I don't specify it, it by default returns only 100 lines of records in the query result. If I specify it, then it's limited to a specific number.
Is there any way to get around of this row count issue? I don't want any restriction on the number of records returned by a query.
Thanks a lot!

No human can manage that much data...in a grid, a chart, or a direct-connected link to the brain.
What you want to implement (much like other customers with similar requirements) is a drill-in and filtering model that helps the user identify and zoom in on data of relevance, not forcing them to scroll through thousands or millions of records.
You can also use a time-based paging model so that you only deal with a time "slice" at one request (e.g. an hour, day, etc...) and provide a scrolling window. This is commonly how large datasets are also dealt with in applications.
I would suggest describing your application in more detail, and we can offer design recommendations and ideas.
- Rick

How to handle large result sets?

Hi All,
I have a large result set to be displayed to user using jsp's. Problem is that result set is too big, so I can't display all the records in a single push. I want to show the results page by page say 25 per page. Now for every page I have to fetch data from database, means there are going to be many database calls which is not advisable. Or i can cache data in a CachedRowSet to reduce database calls, but in this case you have to store all the data in memory which is not a good solution in case you have very large data sets. Can anybody suggest me a solution to this problem?

The best thing for you to do is to implmeneting paging logic in conjunction with a scrollable resultset (JDBC 2.0+).
The logic would go like this assuming 30 rows per page:
- keep track of which page the user is on (e.g. page 3)
- issue the full sql
- scroll thru only the rows in the current page (e.g. rows 90-120)
- copy the page's rows to value objects
- close the resultset, statement, and connection
In the above example, you would scroll to row 90 using rs.absolute(90).
The efficiency comes from the fact that you're using a scrollable resultset. By using this, only the rows that you scroll thru are extracted out from the database. I performed some simple testing and with my data, and the scrollable resultset was about 10x in performance.
Good luck!

Web Services with Large Result Sets

Hi,
We have an application where in a call to a web service could potentially yield a large result set. For the sake of argument, lets say that we cannot limit the result set size, i.e., by criteria narrowing or some other means.
Have any of you handled paging when using Web Services? If so can you please share your experiences considering Web Services are stateless? Any patterns that have worked? I am aware of the Value List pattern but am looking for previous experiences here.
Thanks

Joseph Weinstein wrote:
Aswin Dinakar wrote:
I ran the test again and I removed the ResultSet.Fetch_Forward and it
still gave me the same error OutOfMemory.
The problem to me is similar to what Slava has described. I am parsing
the result set in memory storing the results in a hash map and then
emptying the post processed results into a table.
The hash map turns out to be very big and jvm throws a OutOfMemory
Exception.
I am not sure how I can turn this around -
I can partition my query so that it returns smaller chunks or "blocks"
of data each time(say a page of data or two pages of data). Then I can
store a page of data in the table. The problem with this approach is
that it is not exactly transactional. Recovery would be very difficult
in this approach.
I could do this in a try catch block page by page and then the catch
could go ahead and delete the rows that got committed. The question then
becomes what if that transaction fails ?It sounds like you're committing the 'cardinal performance sin of DBMS processing',
of shovelling lots of raw data out of the DBMS, processing it in some small way,
and sending it (or some of it) back. You should instead do this processing in
a stored procedure or procedures, so the data is manipulated where it is. The
DBMS was written from the ground up to be a fast efficient set-based processor.
Using clever SQL will pay off greatly. Build your saw-mills where the trees are.
JoeYes we did think of stored procedures. Like I mentioned yesterday some of the post
processing depends on unicode and specific character sets. Java seemed ideally suited
to this since it handles these unicode characters very well and has all these libraries
we can use. Moving this to DBMS would mean we would make that proprietary (not that we
wont do it if it became absolutely essential) but its one of the reasons why the post
processing happens in java. Now that you mention it stored procedures seem the best
option.

Quotacheck: searchfs Result too large: Result too large

Aside from a 2006 post regarding this issue, I'm unsure how to resolve my scenario. We're using OSX server's time machine AFP goodies, but we needed to enable quotas for users. Simple? Maybe, but not mac style... so you head into the terminal, read some old posts on outdated forums... use repquota, quotacheck, and quotaon...
And everything seemed to work, until you add a user (through edquota) who's quota isn't in fstab, who can't be found in repquota...
sigh...
I turned off quota checking, tried starting from scratch... what do I get with but an error who's last mention on this forum is from 2006:
sudo quotacheck -a -v
* Checking user and group quotas for /dev/rdisk4 (/Volumes/ColdStorage)
34
quotacheck: searchfs Result too large: Result too large
Any ideas of ways around? The 2006 posts seem to indicate that after attempting variations of quotacheck, I might eventually break through!

Hello,
I've run into the same issue on our setup as well. (Xserve G5 10.4.8, data is an Xserve RAID, level 5 1TB, used for home directories) I'm working with Apple to see if there is a solution to this issue or if it is a bug. In the meanwhile, they recommended running quotacheck with the path to the share rather then -a
sudo quotacheck -v /Volumes/OURDATA
Using the command this way seems to work about half of the time for me, the other half still giving the same error message. I'm hoping this is a cosmetic issue with quotacheck, and not a hint of a problem with our setup.
I'll be sure to post if I find anything else out.
Matt Bryant
ACTC
Husson College and the New England School of Communications

I-bot not emailing when report returns large result set..

Hi,
I am trying to set up an i-bot to run daily and email the results to the user. Assuming the report in question is Report_A.
Report_A returns around 60000 rows of data without any filter condition. When I tried to set up thei-bot for Report_A (No filter conditions on the report) the ibot is publishing results to dashboard but is not delivering via email. When I introduce a filter in Report_A to reduce the data returned then everything works fine and email is being sent out successfully.
So
1) Is there a size limit for i-bots to deliver by email?
2) Is there a way to increase the limits if any so the report can be emailed even when returning large result sets?
Please let me know.

Sorry for late reply
Below is the log file for one of the i-bots. Now I am getting an error message "***kmsgPortalGoRequestHasBeenCancelled: message text not found ***" and the i-bot alert message shows as "Cancelled".
+++ ThreadID: f3c6cb90 : 2010-12-17 23:55:04.551
[nQSError: 77006] Oracle BI Presentation Server Error: A fatal error occurred while processing the request. The server responded with: ***kmsgPortalGoRequestHasBeenCancelled: message text not found ***
Error Codes: YLKKAV7S
Error Codes: AGEGTYVF
+++ ThreadID: f3c6cb90 : 2010-12-17 23:55:04.553
iBotID: /shared/_ibots/common/TM/Claims Report
...Trying iBot Get Response Content loop again.
+++ ThreadID: f3c6cb90 : 2010-12-17 23:55:04.554
... Sleeping for 8 seconds.
+++ ThreadID: f3c6cb90 : 2010-12-17 23:55:12.642
[nQSError: 77006] Oracle BI Presentation Server Error: A fatal error occurred while processing the request. The server responded with: ***kmsgPortalGoRequestHasBeenCancelled: message text not found ***
Error Codes: YLKKAV7S
Error Codes: AGEGTYVF
+++ ThreadID: f3c6cb90 : 2010-12-17 23:55:12.644
iBotID: /shared/_ibots/common/TM/Claims Report
...Trying iBot Get Response Content loop again.
+++ ThreadID: f3c6cb90 : 2010-12-17 23:55:12.644
... Sleeping for 6 seconds.
+++ ThreadID: f3c6cb90 : 2010-12-17 23:55:18.730
[nQSError: 77006] Oracle BI Presentation Server Error: A fatal error occurred while processing the request. The server responded with: ***kmsgPortalGoRequestHasBeenCancelled: message text not found ***
Error Codes: YLKKAV7S
Error Codes: AGEGTYVF
+++ ThreadID: f3c6cb90 : 2010-12-17 23:55:18.734
iBotID: /shared/_ibots/common/TM/Claims Report
Exceeded number of request retries.

Displaying large result sets in Table View u0096 request for patterns

When providing a table of results from a large data set from SAP, care needs to be taken in order to not tax the R/3 database or the R/3 and WAS application servers. Additionally, in terms of performance, results need to be displayed quickly in order to provide sub-second response times to users.
This post is my thoughts on how to do this based on my findings that the Table UI element cannot send an event to retrieve more data when paging down through data in the table (hopefully a future feature of the Table UI Element).
Approach:
For data retrieval, we need to have an RFC with search parameters that retrieves a maximum number of records (say 200) and a flag whether 200 results were returned.
In terms of display, we use a table UI Element, and bind the result set to the table.
For sorting, when they sort by a column, if we have less than the maximum search results, we sort the result set we already have (no need to go to SAP), but otherwise the RFC also needs to have sort information as parameters so that sorting can take place during the database retrieval. We sort it during the SQL select so that we stop as soon as we hit 200 records.
For filtering, again, if less than 200 results, we just filter the results internally, otherwise, we need to go to SAP, and the RFC needs to have this parameterized also.
If the requirement is that the user must look at more than 200 results, we need to have a button on the screen to fetch the next 200 results. This implies that the RFC will also need to have a start point to return results from. Similarly, a previous 200 results button would need to be enabled once they move beyond the initial result set.
Limitations of this are:
1.     We need to use custom RFC function as BAPIs dont generally provide this type of sorting and limiting of data.
2.     Functions need to directly access tables in order to do sorting at the database level (to reduce memory consumption).
3.     Its not a great interface to add buttons to Get next/previous set of 200.
4.     Obviously, based on where you are getting the data from, it may be better to load the data completely into an internal table in SAP, and do sorting and filtering on this, rather than use the database to do it.
Does anyone have a proven pattern for doing this or any improvements to the above design? Im sure SAP-CRM must have to do this, or did they just go with a BSP view when searching for customers?
Note I noticed there is a pattern for search results in some documentation, but it does not exist in the sneak preview edition of developer studio. Has anyone had in exposure to this?
Update - I'm currently investigating whether we can create a new value node and use a supply function to fill the data. It may be that when we bind this to the table UI element, that it will call this incrementally as it requires more data and hence could be a better solution.

Hi Matt,
i'm afraid, the supplyFunction will not help you to get out of this, because it's only called, if the node is invalid or gets invalidated again. The number of elements a node contains defines the number of elements the table uses for the determination of the overall number of table rows. Something quite similar to what you want does already exist in the WD runtime for internal usage. As you've surely noticed, only "visibleRowCount" elements are initially transferred to the client. If you scroll down one or multiple lines, the following rows are internally transferred on demand. But this doesn't help you really, since:
1. You don't get this event at all and
2. Even if you would get the event, since the number of node elements determines the table's overall rows number, the event would never request to load elements with an index greater than number of node elements - 1.
You can mimic the desired behaviour by hiding the table footer and creating your own buttons for pagination and scrolling.
Assume you have 10 displayed rows and 200 overall rows, What you need to be able to implement the desired behaviour is:
1. A context attribute "maxNumberOfExpectedRows" type int, which you would set to 200.
2. A context attribute "visibleRowCount" type int, which you would set to 10 and bind to table's visibleRowCount property.
3. A context attribute "firstVisibleRow" type int, which you would set to 0 and bind to table's firstVisibleRow property.
4. The actions PageUp, PageDown, RowUp, RowDown, FirstRow and LastRow, which are used for scrolling and the corresponding buttons.
The action handlers do the following:
PageUp: firstVisibleRow -= visibleRowCount (must be >=0 of course)
PageDown: firstVisibleRow += visibleRowCount (first + visible must be < maxNumberOfExpectedRows)
RowDown/Up: firstVisibleRow++/-- with the same restrictions as in page "mode"
FirstRow/LastRow is easy, isn't it?
Since you know, which sections of elements has already been "loaded" into the dataSource-node, you can fill the necessary sections on demand, when the corresponding action is triggered.
For example, if you initially display elements 0..9 and goto last row, you load from maxNumberOfExpected (200) - visibleRows (10) entries, so you would request entries 190 to 199 from the backend.
A drawback is, that the BAPIs/RFCs still have to be capable to process such "section selecting".
Best regards,
Stefan
PS: And this is meant as a workaround and does not really replace your pattern request.

ValueListHandler, Large Results and Clustering

Has anybody got experience of using the ValueListHanlder pattern with a session facade and potentially very large query results, e.g. millions of results (even when filtered)?
How did this solution scale with many users each with a stateful session bean containing all of the results? How did state replication over a cluster scale? Are there any better solutions you have implemented?
Any experience/tips would be much appreciated.
Duncan Eley

Ah, ValueListHandler, a pattern whose soleexistence
is due to the limitations of entity beans. Ah,the
old painful days of EJB. (I digress)
Yes, there are several solutions. Do you
need
millions of rows? There are a few ways to getaround
this, depending on your requirements:Unfortunatley, the current implementation of the
system could result in millions of rows, paged of
course, being delivered to the end user. I am yet to
discuss how useful this could be to the end user -
- it is quite possibly useless but that's for our
users to decide.
There are business requirements, and there are also technical realities. First approach them with, "How would you even scroll through a million records?" Then, if they persist, "Well, it doesn't matter anyway because a million records will either break the server or require you to buy ten for every one you would have purchased otherwise."
If you are storing all those rows to perform aseries of calculations, perform the calculations
'close' to the ResultSet itself, meaning read each
row and update your calculations accordingly. You
should then simply have to return the calculation
results. This would typically be done during abatch
process run or a report.
If you are only displaying, say, a hundred at atime, implement pagination. This would be like in
Google where you see 1 ... n for however manypages
of data there are. Rather than returning amillion
rows, SELECT the count first and then SELECThowever
many rows are appropriate for a page. You can use
ROWNUM (for Oracle) or LIMIT (for ANSI compliant
RDBMS) to 'page' the results returned by the
database.This approach would require two queries to begin
with (count and first page) then a query for each
page. What worries me about this approach is that if
the query consists of multiple joins on tables with
millions of rows, the queries can be quite slow. And
having used this technique once before on a complex
query with GROUP BY, ORDER BY and HAVING, using LIMIT
was not much quicker than not using LIMIT (in MySQL
4.0).
You can always serialize the results to the file system or store the query results in a temporary table. The latter is nice because LIMIT works on that (smaller with fewer joins) query. The issue you will run into is how and when to clear out 'stale' query results. Depending on how much disk you have, you could conceivably dedicate a parent record for each user. When the user requested another query, the existing one would be overwritten. A batch process could expire all stored results at the end of the night, week, month, etc.
If all else fails, and this is a very rarerequirement that literally millions of rows
must be sent to either the app server orthe
client, then store the results temporarily in the
file system of the app server. This is a last
resort. I would be shocked to find real, valid
business requirements to actually hold ontomillions
of rows.I agree this would be a last resort: would not work
in a cluster, clean up issues etc. I've seen one
solution where results were stored back in the
database as a BLOB!? See:
http://wldj.sys-con.com/read/45563.htm
BLOB is a possibility, but I think a dedicated temporary table is more elegant. How would you paginate a BLOB without loading it into memory first?
Hope that stimulates a few ideas. Why do you have
millions of rows? (BTW, regarding statereplication,
this would make a horrendous situation that much
worse; it would in all likelihood gum up yournetwork
and cause all your machines to run out of memory
soon).
Thanks for your input. If the requirements
cannot change then I guess at the moment I'll have to
compare the 'one query, page through results in
stateful session bean' approach with the 'multiple
but limited queries approach'.
I think the former has memory scaling issues and the latter may have performance issues.
Has anybody already compared these two approaches?
What do people think of the 'results stored in the
database' approach?
- SaishDuncan EleyInteresting discussion!
- Saish

SOAP handlers and the WebLogic Security Provider Framework

I am new to WebLogic... I am trying to understand the Weblogic security framework in terms of how a SOAP message would be processed. Do SOAP handlers get called before the configured security providers? after being processed by the Authentication provider? after being processed by the Authorization provider? or at some other point?

Thanks. But I have some questions about the seed:
- where is it stored?
- how is it encrypted?
- is the seed regenerated periodically? or under certain circumstances?
Regards,
Janice Pang
"Tom Hegadorn" <[email protected]> wrote:
>
>
Hi Janice,
If you choose to use the PrincipalValidatorImpl class in the
weblogic.security.provider package, the sign() implementation
will be the internal weblogic implementation. This implementation
generates a random seed and computes a digest based on the
random seed. I hope that helps you.
Regards,
Tom Hegadorn
Sr. Developer Relations Engineer
BEA Support
"Janice Pang" <[email protected]> wrote:
From the online documentations, it is said that this weblogic.security.provider.PrincipalValidatorImpl
"signs" the authenticated principals to make sure they are not altered
while they
are transported on the network.
The document also mentioned, as a suggested way to develop a customprincipal
validation provider, to use this class and extend the capabilities of
user and
group classes. What kind of private information from the server isused
for the
signature and where is that information stored?

Fetching large results into excel

I would like to fetch 50,000 records from an oracle database and store it as an ascii file so that it can be viewed through an excel. The request will be initiated from a client�s computer through J2ee web application.
1. What is the best way to fetch the 50,000 records and store in an ASCII/Excel file?
2. Is there a potential performance issue in writing into local PC/Laptop?
Thankyou,
Ramran

Ramran wrote:
I would like to fetch 50,000 records from an oracle database and store it as an ascii file so that it can be viewed through an excel. Who in their right mind would want to view 50K records on the web?
The request will be initiated from a clients computer through J2ee web application. What's the use case? Here's one:
1. User specifies WHERE clause to specify which records they want
2. Application queries database and sends result to browser using Excel MIME type
3. User now has the option of saving the browser as an Excel file to their local machine
1. What is the best way to fetch the 50,000 records and store in an ASCII/Excel file?"Best"? You'll use JDBC for the fetch, of course. I'd use Andy Khan's JExcel and Spring's JExcelView to render in the browser.
2. Is there a potential performance issue in writing into local PC/Laptop?Sure. Depending on how large each record is (X bytes/record), you'll have 50000X bytes consumed on the server and in the browser for each request. How many simultaneous users do you plan on having? Nevermind the network latency required to fetch the data and stream it to the browser.
%

Paged query results in a JSP page

Hi All,
I have a requirement to display only a small number of records (say 50) in a JSP page at a time from a database query that returns more than 10,000 records. For accessing all the other records I have to provide links from the same page. I should be able to go to the first, last, next & previous sets of records at any time. Database is Oracle and the table I am using to query doesn't have a serial number column. Any easy way? Thanks Raj

Hi Raj,
There are two ways to handle it.
One is to fetch the entire set of record from the Database and store the details in a Container which has session level context. But if the fetched size is higher then Session cannot hold that much amount of data.
Alternatively you can go about fetching fixed chunks of data from the
Database(preferably of size 50 to 100). This can be achieved using SQL queries. I have done this and seems to work pefectly in situations where large data available in Database has to be displayed pagewise to the users. (U will find the query in AskTom site of Oracle Corporation).
Please revert back if any further help is needed in this regard.
Ilamparithi

Paged query results within a TIle ?

what is the best way to page query results within a Tile
component ?
eg. I have a Tile component with multiple Repeater Image
links supplied via an HTTPService call to a PHP script.
I want to break up the tiled result pages to save loading
time.
Would I load the entire result set into Flex, and then
control how they are viewed by using the horizontal or
verticalScrollPosition property of the Tile container, or perhaps I
could make multiple HTTPService calls for each page of results ?
Any ideas would be much appreciated.

What about using the tilelist object for multiple returned
images? You can provide the list as the dataSource to the TileList.
The images are dynamically linked and they are delivered from the
server when they are rendered. That way you could bring down the
url for many images and dynamically link to the images. This would
allow you to bring down many rows at one time.

How to save memory when processing large result set

I need to dump multi millions of rows of data into excel files
I query the tables and open excel to write in
The problem is even I chopped the result into hundred files, close excel completely after 65536 rows, the memory usage keeps going up as the result set is looped and at one point hit the heap size
How can I release the memory has been used in the result set?
Thank you

mycoffee wrote:
936517 wrote:
I think resultSet.close() will do what you want (you shouldn't have to set resultSet=null when you're done with it).
You can't force the garbage collector to run and reclaim memory. It uses an intelligent algorithm to do so .
I question why your project is sending millions of records to excel. Who is going to read a 10,000 page excel document(s)?
Instead, I suggest you provide a (intelligent) filter mechanism to allow users to get a subset of data to send to an excel document rather than all data. For example: instead of sending him the entire telephone book, have him search for results based on lastName and/or firstName. That will cut down on the number of records returned. Next, does the user really need all the columns of data in each record? That will cut it down further.
You can search Google for 'java heap size' to increase the memory for your program. However, your 65536 limit is probably due to Excel's limitation and not your Java program.Sorry I could not explain the need,
No. That is not issue here. I already use max heap size I can
but I can handle it now. Open files, write directly to the file instead of holding the data and dumping all at once. I save all the overhead and it works fine even the result set still consumes almost all the memory.is it possible you are using mysql? the mysql jdbc driver has a terrible default setup in that it keeps all results for the result set in memory ! i think some of the latest drivers finally allow you to stream results sensibly, but you have to use the correct options.

Does SAP provide framework for statistical calculations ?

Hi all,
Does SAP provide any framework for statistical calculations ?...The reason for asking this question is, in order to calculate the BSUoS (Balancing Services Use of System ) charges.
There is a need to calculate the amount to levy charges for use of the Electricity transmission system. For that there are some statistical calculations need to be done.
Please let me know, if SAP provides solutions for such requirements.
Any information on this requirement is helpful.
Sample Calculations:
IBCd = u03A3j d CSOBMjd + BSCCVjd + NI jd +TLjd + BSCCAd u2212OMd u2212 RTd
FYIncPayINTd = (PT int u2212 FSOINTd ) * SF int
and so on.
Regards,
Sairamakrishna Kante
Edited by: sairamakrishna kante on Aug 6, 2008 8:26 AM

Hi,
I understood your requirement as, you would like to have a pre-configured set for every business process like sales, returns etc... These pre-configured solution r available in SAP in terms of BC set, more information you can get in the SAP Best practise (http://help.sap.com/bp_bblibrary/600/BBlibrary_start.htm) wer for every business process you can install the building block which SAP has created.
Regards
Mani

HT4623 Dowmload update resets after 700 mb 1GB to large for my provider

Update to large a file for my provider and internet speed still in dark ages
Will someone provide cd?

There is no CD. You can make an appointment at your local apple store and have them help you.

Paging large results?? - Woodstock + Provider Framework

Similar Messages

Maybe you are looking for