Difference between url-pattern / and /* ?

There appears to be a subtle difference between:
<url-pattern>/</url-pattern>and
<url-pattern>/*</url-pattern>Both seem to send all requests through the servlet I'm aming for, but the /* on messes up forwards to JSP files. My app works as I expect when I use the "/" version (I don't need suffixes or prefixes since I've written some routing code). I'm wondering if they are supposed to be behave differently or if my Tomcat container has a little bug I'm exploiting wrongly?
If you use the "/" version, would you expect a URL like this to map to it....
http://mysite.com/
... and also ones like this...
http://mysite.com/some/arbitrary/path/here
?

Same question appears here:
http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic&f=7&t=019661
And with lot of discussion.

Similar Messages

Difference between Proxy pattern and Business Delegate pattern

Hi All,
Can any one please tell me what is the difference between Proxy pattern and Business Delegate pattern.
Thanks in advance.
Basak

The books they were first reported in, and the expressed intent, I guess. Arguably, the Business Delegate pattern is a special case Proxy, with more specific details about what resource is being proxied

Difference between Builder Pattern and Factory Pattern

difference between Builder Pattern and Factory Pattern

You are right Both of these patterns are creational design patterns Purpose of these two patterns is very different as Abstract Factory Patterns (which is commonly known as Factory pattern ) is used to create a object in a scenario when you have a product & there is a possibility of many vandors providing implementation for it. So it is good to come up with a abastract factory which provides create method for the product. Each vendor can implement you abstract factory & provide a concrete implementation which will return a product of Vendor implementation.
Builder patter is used in case you have a very complex object creation process involved & you realy want to abstract the client from doing all those complex steps. In such situation you create a builder class which takes care of all complex steps & client just needs to use this builder class to create your complex object.
Hope it clarifies your doubts.

Searching and Matching - Difference between 'Match Pattern' and 'Match Geometric Pattern'?

I was wondering if someone can explain to me the difference between 'Match Pattern' and 'Match Geometric Pattern' VIs? I'm really not sure which best to use for my application. I'm trying to search/match small spherical particles in a grey video in order to track their speed (I'm doing this after subtracting two subsequent frames to get rid of background motion artifacts).
Which should I use?
Thank you!
Solved!
Go to Solution.

Hi TKassis,
1.You may find from this link for the difference between these two,
Pattern Match : http://zone.ni.com/reference/en-XX/help/370281P-01/imaqvision/imaq_match_pattern_3/
Geometric Match : http://zone.ni.com/reference/en-XX/help/370281P-01/imaqvision/imaq_match_geometric_pattern/.
2. I always prefer match pattern because of its execution speed, and incase of geometric pattern match it took lot of time to match your result. You may find in the attached figure for same image with these two algorithm execution time.
Sasi.
Certified LabVIEW Associate Developer
If you can DREAM it, You can DO it - Walt Disney

Difference between Functor Pattern and Processing Pattern

Hi all,
I am missing the difference between these 2 patterns, can someone enlight me ?
I've seen all the screencasts and read the documentation, but I can't find it out.
Thanks.

A session facade hides who you're talking to. It's a way to take a complex conversation that might include N objects and changing it so a single request is made to the facade, which then orchestrates those N objects to fulfill the request.
A proxy also hides who you're talking to, but the main reason is to disguise the location of the callee. It's how RMI and CORBA work - they have your objects talk to a proxy stub, which handles all the complications of marshalling parameters and unmarshalling the response. From the point of view of the caller, it appears that the callee is in their memory address space. The remoteness of the callee is hidden.
%

Difference between url iveiw and BSP iveiw

hi,
     What are the parameters we need for BSP iveiw and URL iveiw. What is the difference between these.

hi,
IViewLauncher
IViewLaucher can be used to launch any IView or Portal Component or a Page in the portal. Portal Component launching is supported only in NW04.
Provider specific Information
IViewLauncher is Provider agnostic. Items may belong to any connector.
Supported Actions
Action name can be anything.
Properties
IViewLauncher expects one of the following two mandatory properties:
iview - iView id or Portal Component name to be launched
page - page id of the page to be launched
All other properties will be passed as name=URL encoded value to the target iView. The dynamic properties can also be passed to an iView via the following property (since NW04 SPS18, NW04s SPS09, NY AP7):
iviewDynamicParameter - optional; name/value pairs of dynamic parameters to be passed to the iView/page. The expected format is name1=value1&name2=value2 etc.
Example
Following is the definition of an action that launches an IView with id ROLES://portal_content/com.sap.pct/every_user/general/iViews/myDemoIView.
<Action name="launchIView" handler="IViewLauncher">
<Properties>
   <Property name="iview" value="ROLES://portal_content/com.sap.pct/every_user/general/iViews/myDemoIView"/>
</Properties>
</Action>
Example on how to configure an action to launch a Portal Component com.sap.netweaver.bc.uwl.ui.DemoIView:
<Action name="launchIView" handler="IViewLauncher">
<Properties>
   <Property name="iview" value="com.sap.netweaver.bc.uwl.ui.DemoIView"/>
</Properties>
</Action>
Example on how to configure an action to launch a Portal Page with id ROLES://portal_content/com.sap.pct/every_user/general/Pages/com.sap.km.MyInfoDiscussions:
<Action name="launchIView" handler="IViewLauncher">
<Properties>
<Property name="page" value="ROLES://portal_content/com.sap.pct/every_user/general/Pages/com.sap.km.MyInfoDiscussions"/>
</Properties>
</Action>
Description
The following parameters are optionally passed on to the iView, WHEN no parameters are explicitly defined.
wi_id - work item id in the provider system
destination - system alias in the Portal system landscape of the provider system
item_id - internal UWL item id
task - provider task item type
uname - backend user id for webflow connector, alert connector and generic ABAP connector, otherwise Portal user id
langu - user language in upper case ISO language code
Additional custom defined parameters are also supported. They can be static and dynamic, i.e., substituted with an actual value during the run time.
Example of a static parameter:
<Action ...>
<Properties>
<Property name="fruit" value="apple"/>
</Properties>
</Action>
This will append &fruit=apple to the constructed url.
Dynamic property values should start with ${ . These values could come from either the Item or some common values like user.
${item.attributeName}
$ - a backend user id corresponding to the logged in Portal user if the provider system is an R3 system
attributeName is case sensitive, and must be either a custom attribute for the item, or one of the following already defined attributes:
appContext attachmentCount completedDate connectorId createdDate creatorId description dueDate escalatedBy executionUrl expiryDate externalId externalObjectId externalType forwardedBy forwardedDate internalId isEscalated itemType memoCount parentItemId priority processDueDate processor status subject subprocessId substitutedFor systemId userId (see description).
An example of using dynamic properies:
<Action ...>
<Properties>
<Property name="workitemId" value="${item.externalId}"/>
<Property name="system" value="${item.systemId}"/>
</Properties>
</Action>
This will result in passing workitemId and system parameters to the target page/iView. This is the same as specifying iviewDynamicParameter property:
<Action ...>
<Properties>
<Property name="iviewDynamicParameter" value="workitemId=${item.externalId}&system=${item.systemId}"/>
</Properties>
</Action>
Note. For webflow connector iViewLauncher can be configured on the backend using SWFVISU transaction. The table below summarizes the mapping between the launcher parameters and the visualization parameters.
Launcher parameter Visualization Type Visualization Parameter
page Portal Page ID
iview iView ID
iviewDynamicParameter iView/Portal Page DYNPARAM
UrlLauncher
UrlLauncher can be used to launch any url.
Provider specific Information
UrlLauncher is Provider agnostic. Items may belong to any connector.
Supported Actions
Action name can be anything.
Properties
UrlLauncher expects the following property:
url mandatory; url to be launched.
All other properties will be passed as name=URL encoded value to the target url.
Example
Following is the definition of an action that launches a url my.web.com and passes to it the parameter workitem_id, which is filled with the work item id during run time:
<Action name="launchUrl" handler="UrlLauncher">
<Properties>
<Property name="url" value="http://my.web.com"/>
<Property name="workitem_id" value="${item.externalId}"/>
</Properties>
</Action>

Difference between Session Facade and Business Delegate design patterns

Can someone tell me the differences between Session Facade and Business Delegate design patterns

1. Session Facade decouples client code from Entity beans introducing session bean as a middle layer while Business Delegate decouples client code from EJB layer ( Session beans).
2. SF reduces network overhead while BD reduces maintenance overhead.
3. In SF any change in Session bean would make client code change.
While in DB client is totally separate from Session bean because BD layer insulate client from Session beans(EJB layer).
3. In only SF scenario, Client coder has to know about EJB programming but BD pattern no EJB specialization needed.
4.SF emphasizes on separation of Verb, Noun scenario while BD emphasizes on separation of client(presentable) and EJB layer.
Anybody pls suggest more differences ?

Differences between (response.sendRedirect and Requestdispatcher.forward)

Hi All,
I have 3 queries
*1> I wanted to know the "Differences" between*
response.sendRedirect and Requestdispatcher.forward
*2> when do we Opt for response.sendRedirect?*
*3> when do we Opt for Requestdispatcher.forward?*
Thanks,
Deepak AL

The fundamental difference is that sendRedirect is a client based direction, while forward is a server based one.
SendRedirect forces the client to make a new request. In effect you are telling the client browser "What you are looking for is over there"
RequestDispatcher forward, is purely an internal server transition. The client knows nothing about the forward happening.
Example
Lets say you request the page www.myserver.com/myPage.jsp
Example A: Redirect
We send a redirect to www.myserver.com/thatPageOverThere.jsp
The browser receives this message, and its address url changes to www.myserver.com/thatPageOverThere.jsp, and it sends a new request over there.
Note that it is a completely new request, so any parameters that were sent with the old request are irrelevant. If you want to send them again you have to put them into the sendRedirect url.
You can also send a redirect to www.myOtherServer.com/thatPageOnACompletelyDifferentServer.jsp
Example B: Forward to thatPageOverThere.jsp
We obtain a request dispatcher to "thatPageOverThere.jsp" and forward to that resource.
The server instead of running myPage.jsp now executes and returns thatPageOverThere.jsp
The client browser knows nothing of this. As far as it knows it asked for myPage.jsp, and it is getting that response back.
So if you forward to something like "my/page/inASubFolder.jsp" you have to be very careful with relative links on the page.
The browser requested myPage.jsp, so it will resolve relative links from that Url.
When to use one or the other?
Redirect would need to be used when the resource is on another server.
Another common usage is the "Post-Redirect-Get" pattern. (you might want to look that up)
Hope this helps you understand a little.
cheers,
evnafets

What is difference between bex analyser and bex browser

what is difference between bex analyser and bex browser . please explain what are use of both and what we do in both.

hi
Bex Browser
The Business Explorer Browser (BEx Browser) makes it possible for you to access all document types of the Business Information Warehouse that are assigned to your role or that you have stored in your favorites. You can select and open documents assigned to you in the BEx Browser or store and manage new documents in the BEx Browser.
Document types that you can work with in the BEx Browser are:
· BW workbooks
· Documents that are stored in the Business Document Service (BDS)
· Links (references to file system, shortcuts)
· Links to internet sites (URLs)
· SAP transaction calls.
· Web applications and Web templates
· Crystal Reports
Bex Analyser
The Business Explorer Analyzer (BEx Analyzer) is the analysis and reporting tool of the Business Explorer that is embedded in Microsoft Excel.
Features
You can call up the BEx Query Designer in the BEx Analyzer, in order to define queries. Subsequently, you can analyze the selected InfoProvider data by navigation to the query created in the Query Designer and create different query views of the data. You can add the different query views for a query or for different queries to a work book and save them there. You can save the workbook in your favorites or in your role on the BW Server. You can also save the workbook locally on your computer.
Beyond that, you can precalculate the workbook and distribute it by e-mail to recipeients or you can export it to the Enterprise Portal and make it accessible to other employees in the company.
You can start queries in a standard view (with a Standard Web Template set up in Customizing) in the Web browser and forward the URL or continue to navigate on the Web. Similarly, you can export the Web query to MS Excel 2000.
Overview of the Functional Area of the BEx Analyzer:
·        BEx toolbar
You access the functions of the BEx Analyzer from the BEx toolbar, which takes you to the BEx Open dialog box where you can open existing queries, or to the BEx Query Designer where you can create new queries or change existing queries.
·        Evaluating Query Data
The BEx Analyzer offers convenient functions for evaluating and presenting InfoProvider data interactively. In the BEx Analyzer, you can add queries to workbooks, navigate within them and refresh the data. You can also process the queries further in Microsoft Excel or display them in the Web browser in a default view.
Navigation of a query allows you, for example, to filter characteristics on a single value, drilldown on all values for a characteristic, regroup characteristics and key figures in the rows and columns of the results area, or hide key figures. Navigation results in different views of the InfoProvider data. In addition, a range of further functions is available which allow you to edit a query interactively (for example, sorting, cumulated output, among others). In addition, you can use the editing functions in Microsoft Excel in order to set up individual format templates, to print results areas, or to create graphics.
·        Queries in Workbooks
Queries are inserted into workbooks so you can display them. When you insert a query, a link is made between the cell areas of the worksheet and the data of the InfoProvider upon which the query is based. A link therefore exists between the Business Explorer and the Business Information Warehouse Server (BW Server).
When inserting a query into the workbook, a VBA routine is automatically generated in the workbook. You can also connect the Business Explorer with your own VBA programs (Visual Basic for Applications).
You can create workbook templates, into which you can insert your queries. Workbook templates can contain pre-determined items for the area of the query, formatting settings, logos, VBA macros, and so on.
·        Precalculating workbooks
You can precalculate and distribute workbooks with the BEx Broadcaster, which is a Web application you get to form the BEx toolbar. The system generates MS Excel workbooks with historical data. You determine the time for precalculation yourself: You can have workbooks precalculated at a predefined time or they can be precalculated whenever data in the underlying InfoProvider changes. You can have the precalculated workbooks sent by e-mail or you can export them into the Enterprise Portal, where you can make them available to employees within your company.
Activities
To start the BEx Analyzer, choose Start ® Programs ® SAP Front-end Business Information Warehouse ® SAP Business Explorer Analyzer.
You can also access the BEx Analyzer via SAP Easy Access ® SAP Business Information Warehouse ® SAP Menu ® Business Explorer ® Analyzer or in the Business Explorer Browser using the Business Explorer Analyzer symbol in the menu bar.
Hope this will solve your issu
nagarjuna

Difference between connection pooling and simple connection

Anybody please tell me what is the Difference between connection pooling and simple connection and also where we define connection pooling and how.
Thanks
Please reply soon
amitindia

Creating and closing connection to the database is a relatively slow process. Equally connections use database resources so you can't just open as many as you want.
A connection pool maintains a number of open connections throughout the lifetime of the application. Instead of opening and closing the connections your application just "borrows" them from the pool when they're needed.
If the pool runs out of connections it will usually create new ones as needed until you reach some predefined upper limit.
A good connection pool will also manage connections which have failed for any reason, and report code which fails to return connections to the pool (ie connection leaks).
The number of connections created at startup is referred to as the "low water mark" and the maximum number that the pool will allow to be opened at any given time is the "high water mark". If no connections are available client code will generally block until one is released.
If by "defined" you mean where can you get a working implementation then your database or application server vendor is likely to provide one. Also the Apache Jakarta Commons includes [url http://jakarta.apache.org/commons/dbcp/]an implementation which you can use with any JDBC driver.
Dave.

Question about main difference between Java bean and Java class in JSP

Hi All,
I am new to Java Bean and wonder what is the main difference to use a Bean or an Object in the jsp. I have search on the forum and find some post also asking the question but still answer my doubt. Indeed, what is the real advantage of using bean in jsp.
Let me give an example to illustrate my question:
<code>
<%@ page errorPage="errorpage.jsp" %>
<%@ page import="ShoppingCart" %>

<jsp:useBean id="cart" scope="session" class="ShoppingCart" />
<html>
<head><title>Shopping Cart</title></head>
<body bgcolor="#FFFFFF">
Your cart's ID is: <%=cart.getId()%>.
</body>
<html>
</code>
In the above code, I can also create a object of ShoppingCart by new operator then get the id at the following way.
<code>
<%
ShoppingCart cart = new ShoppingCart();
out.println(cart.getId());
%>
</code>
Now my question is what is the difference between the two method? As in my mind, a normal class can also have it setter and getter methods for its properties. But someone may say that, there is a scope="session", which can be declared in an normal object. It may be a point but it can be easily solved but putting the object in session by "session.setAttribute("cart", cart)".
I have been searching on this issue on the internet for a long time and most of them just say someting like "persistance of state", "bean follow some conventions of naming", "bean must implement ser" and so on. All of above can be solved by other means, for example, a normal class can also follow the convention. I am really get confused with it, and really want to know what is the main point(s) of using the java bean.
Any help will be highly apprecaited. Thanks!!!
Best Regards,
Alex

Hi All,
I am new to Java Bean and wonder what is the main
difference to use a Bean or an Object in the jsp. The first thing to realize is that JavaBeans are just Plain Old Java Objects (POJOs) that follow a specific set of semantics (get/set methods, etc...). So what is the difference between a Bean and an Object? Nothing.
<jsp:useBean id="cart" scope="session" class="ShoppingCart" />
In the above code, I can also create a object of
ShoppingCart by new operator then get the id at the
following way.
ShoppingCart cart = new ShoppingCart();
out.println(cart.getId());
...Sure you could. And if the Cart was in a package (it has to be) you also need to put an import statement in. Oh, and to make sure the object is accessable in the same scope, you have to put it into the PageContext scope. And to totally equal, you first check to see if that object already exists in scope. So to get the equivalant of this:
<jsp:useBean id="cart" class="my.pack.ShoppingCart"/>Then your scriptlet looks like this:
<%@ page import="my.pack.ShoppingCart %>
<%
ShoppingCart cart = pageContext.getAttribute("cart");
if (cart == null) {
    cart = new ShoppingCart();
    pageContext.setAttribute("cart", cart);
%>So it is a lot more work.
As in my mind, a normal class can also
have it setter and getter methods for its properties.True ... See below.
But someone may say that, there is a scope="session",
which can be declared in an normal object.As long as the object is serializeable, yes.
It may be
a point but it can be easily solved but putting the
object in session by "session.setAttribute("cart",
cart)".Possible, but if the object isn't serializable it can be unsafe. As the point I mentioned above, the useBean tag allows you to check if the bean exists already, and use that, or make a new one if it does not yet exist in one line. A lot easier than the code you need to use otherwise.
I have been searching on this issue on the internet
for a long time and most of them just say someting
like "persistance of state", "bean follow some
conventions of naming", "bean must implement ser" and
so on. Right, that would go along the lines of the definition of what a JavaBean is.
All of above can be solved by other means, for
example, a normal class can also follow the
convention. And if it does - then it is a JavaBean! A JavaBean is any Object whose class definition would include all of the following:
1) A public, no-argument constructor
2) Implements Serializeable
3) Properties are revealed through public mutator methods (void return type, start with 'set' have a single Object parameter list) and public accessor methods (Object return type, void parameter list, begin with 'get').
4) Contain any necessary event handling methods. Depending on the purpose of the bean, you may include event handlers for when the properties change.
I am really get confused with it, and
really want to know what is the main point(s) of
using the java bean.JavaBeans are normal objects that follow these conventions. Because they do, then you can access them through simplified means. For example, One way of having an object in session that contains data I want to print our might be:
<%@ page import="my.pack.ShoppingCart %>
<%
ShoppingCart cart = session.getAttribute("cart");
if (cart == null) {
    cart = new ShoppingCart();
    session.setAttribute("cart", cart);
%>Then later where I want to print a total:
<% out.print(cart.getTotal() %>Or, if the cart is a JavaBean I could do this:
<jsp:useBean id="cart" class="my.pack.ShoppingCart" scope="session"/>
Then later on:
<jsp:getProperty name="cart" property="total"/>
Or perhaps I want to set some properties on the object that I get off of the URL's parameter group. I could do this:
<%
ShoppingCart cart = session.getAttribute("cart");
if (cart == null) {
    cart = new ShoppingCart();
    cart.setCreditCard(request.getParameter("creditCard"));
    cart.setFirstName(request.getParameter("firstName"));
    cart.setLastName(request.getParameter("lastName"));
    cart.setBillingAddress1(request.getParameter("billingAddress1"));
    cart.setBillingAddress2(request.getParameter("billingAddress2"));
    cart.setZipCode(request.getParameter("zipCode"));
    cart.setRegion(request.getParameter("region"));
    cart.setCountry(request.getParameter("country"));
    pageContext.setAttribute("cart", cart);
    session.setAttribute("cart", cart);
}Or you could use:
<jsp:useBean id="cart" class="my.pack.ShoppingCart" scope="session">
<jsp:setProperty name="cart" property="*"/>
</jsp:useBean>The second seems easier to me.
It also allows you to use your objects in more varied cases - for example, JSTL (the standard tag libraries) and EL (expression language) only work with JavaBeans (objects that follow the JavaBeans conventions) because they expect objects to have the no-arg constuctor, and properties accessed/changed via getXXX and setXXX methods.
>
Any help will be highly apprecaited. Thanks!!!
Best Regards,
Alex

Difference between IDOC Bundling and IDOC Packaging

Hi,
Can anybody please explain the difference between IDOC bundling and IDOC packaging?
Thanks,
Loveena.

Hi,
IDoc Bundling is the changing the occurance of IDoc.
In a scenario If there is a necessitity for changing the Occurance of some segment of the IDOC u have to perform this steps
1.Import the IDoc to XI.
2.Export the IDoc(i.e XSD format) and save it to the local machine.
3.Make changes to the IDoc structure by modifying the XSD file in the local machine.
4.Save it as an XSD file Itself.
5.Import the XSD file in the IR under the External Defination.
6.Use this XSD in your Message Interface/Mapping which is same as IDoc structure but with some changes that u have made.
Go Thru this Blog <a href="/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change Bundling - Trick without BPM</a> BY Michal Krawczyk where the Occurance of the IDoc is changed to 1...Unbounded from 1...999999999 by using the XSD.
IDoc Packing is collecting of IDoc
<a href="/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm of Multiple type IDOCs in BPM</a> BY Pooja
Regards
Santhosh
Remember to set the thread to solved when you have received a solution
[url=Use a Good Subject Line, One Question Per Posting - Award Points; Use a Good Subject Line, One Question Per Posting - Award Points[/url]

Differences between PT8.51 and PT8.52 versions

Hi,
Can I get some documentation or reference URL for differences between PT8.51 and PT8.52 versions?
Thank You!
Regards
Soundappan

In addition, specially for the YouTube generation, Gray Sparling has created a great webinar on the features of PeopleTools 8.52
http://www.youtube.com/playlist?list=PL9B370AEEF80F8C10&feature=plcp
I have also written a couple of blogs on some feaures of PeopleTools 8.52
http://bloggingaboutoracleapplications.org/bi-publisher-enhancements-peopletools-852/
http://bloggingaboutoracleapplications.org/create-interactive-dashboard-interwindow-communication-iwc/
http://bloggingaboutoracleapplications.org/create-apealing-dashboards-peopletools-852/
http://bloggingaboutoracleapplications.org/peoplesoft-oracle-secure-enterprise-search-ses/
http://bloggingaboutoracleapplications.org/peopletools-852-generally/
That should keep you busy for some wile :)

Difference between webservices model and adaptive webservices model

hi
Can any one explain me regarding Difference between webservices model and adaptive webservices model.
Thanks

Hi,
In old WS Model, ithere was no concept of logical destinations.
There if you are using a WSDL located on a server and if the location of the WSDL
changes, your application won't run. The deployed application using the WS Model will have trouble finding
the WSDL. As a result you'll have to again import the
model. Moreover old WS Model does not have re-import functionality.
But incase of AWS Model, you can desine logical destinations and even if the location of the WSDL changes, all you have to do is change the new url in the Visual Admin and not import the model again.
You can visit the following link for more details:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b04308ed-62d5-2910-b3a6-c26771b1c78e
Regards,
Nidhi

Difference Between SDM Deployment and JSPM

Hello All,
Can anybody tell me the difference between SDM Deployment and JSPM.
please guide me in brief or guide any URL
Thanks & Regards
Shishir

Shishir,
Do refer the following links
Java Support Package Manager (JSPM) - http://help.sap.com/saphelp_nw04s/helpdata/EN/87/4797422930c56ae10000000a155106/frameset.htm
Software Deployment Manager (SDM) - http://help.sap.com/saphelp_nw04/helpdata/en/22/a7663bb3808c1fe10000000a114084/frameset.htm
The first page of the links itself describes the purpose of the tools. Also, do use the search features of the forum and search on help.sap.com. Most of the queries are already asked or present in the help documentation.
Thanks,
GLM

Difference between url-pattern / and /* ?

Similar Messages

Maybe you are looking for