Integration into Other Workplace/Portal Scenarios

In many cases, you want to run Application Designer pages inside your own environments that are outside of Application Designer.

The requirements of other workplace/portal environments are:

  • Pages must be accessible by URLs.

  • There must be a possibility to pass information to pages. For example, user management is provided by a portal management. The result (the name of the user who is currently logged in) should be passed to applications for further processing.

To call Application Designer pages with a URL: normally each single Application Designer page can be called individually with a corresponding URL. "Normally" means that this is true from the Application Designer perspective - maybe it is not completely true from your application’s perspective: one page requires a certain page to be run first, etc.

To call an Application Designer page, simply use the following URL:

http://<host>:<port>/cis/StartCISPage?PAGEURL=<pageURL>

Replace the <pageURL> with the URL of the wanted Application Designer page and it will be opened.

For information on additional parameters that you can pass via the StartCISPage servlet, see Appendix E - StartCISPage Servlet .


Passing Parameters to your Application Designer Page

You can append any number of parameters to the URL mentioned in the previous section. Each parameter consists of the sequence "&<paramName>=<paramValue>". If you want to pass the customerId to a "customer detail" page, the URL would look like:

http://<host>:<port>/cis/StartCISPage?PAGEURL=/appxyz/customerdetail.html&customerId=4711

Each parameter is bound to a corresponding property of the page adapter. For example, the "customer detail" page is hooked on the adapter CustomerDetailAdapter. Therefore, it must provide a corresponding customerId property to which the parameter is passed at runtime:

public class CustomerDetailAdapter extends Adapter	
{	
    ...
    public void setCustomerId(String value)	
    {
        ...
    }	
    ...
}