Hi,

Yes, you can define your own URL with respects to prweb/PRServlet.

The "prweb" part is the default context root when you deploy PRPC. You can change this at deployment time. There is no requirement to have the context root as "/prweb".

The "PRServlet" is the servlet definition. Creating a custom servlet is possible by defining your own servlet definition or changing a servlet mapping in the web.xml before you deploy. Make sure that you understand web.xml sevlet definitions. There is a single PRPC web tier engine class used for servlets to handle browser connections but contains many options to support different types of authentication. You should copy and modify an existing one that meets your needs.

By far the easiest approach is to simply change the servlet mapping. For Example changeing PRServlet to MyCustom is simple:

As Is:

<servlet-mapping>
  <servlet-name>WebStandard</servlet-name>
  <url-pattern>/PRServlet</url-pattern>
 </servlet-mapping>
 <servlet-mapping>
  <servlet-name>WebStandard</servlet-name>
  <url-pattern>/PRServlet/*</url-pattern>
 </servlet-mapping>

New:

<servlet-mapping>
  <servlet-name>WebStandard</servlet-name>
  <url-pattern>/MyCustom</url-pattern>
 </servlet-mapping>
 <servlet-mapping>
  <servlet-name>WebStandard</servlet-name>
  <url-pattern>/MyCustom/*</url-pattern>
 </servlet-mapping>

There are no changes or copies of the servlet definition of "WebStandard". This is simply changing URL pattern so it's accesses with "/<context_root>/MyCustom"

--Chris