Web Client Customization
The Creo Elements/Direct Model Manager Web Client uses Java Server Page (JSP) and the Cascading Style Sheets (CSS) to build the web pages. You can customize the web client in the following ways:
1. XML Configuration: The content of the main pages of the web client can be configured in the WebConfig.xml file located in the Creo Elements/Direct Manager Server installation location. For example, you can configure which columns (attributes) are shown in the search results table for every class. For the Details page you can configure components (such as thumbnails or download actions), the tabs for each class as well as the columns for each tab. You can also configure some additional settings, such as display of thumbnails, in the WebConfig.xml file.
 |
In the WebConfig.xml file, the following load rules are shipped with <DownloadLoadRule>:
• As Stored - Downloads the configuration of the model as it was saved into the Creo Elements/Direct Model Manager Server database.
• Highest Revisions - Downloads the highest revision of every object within the model.
• Highest Released Revisions - Downloads the highest revision that has been released of every object within the model.
|
2. Themes (Style Sheets): The look and format of the web pages can easily be modified by applying a different theme. A theme consists of a Cascading Style Sheet (CSS) and two JSP fragments, footer.jsp and header.jsp. You can use this customization approach to modify the colors, fonts, borders, and so on, or to display custom headers and footers or on your web pages.
|
|
PTC recommends that you should create a new theme instead of modifying the existing ones. For details on creating and applying a new theme, see Customizing the web page layout.
|
3. JSP Pages: For advanced modifications such as different layouts or adding content, you can modify an existing JSP page or add new JSP pages in webapps\mmweb.
|
|
PTC recommends that you should work with an additional web application as follows:
a. Create a new web application in <Creo Elements/Direct Manager Server installation location>\webapps\mmweb_dev.
b. Register the new web application under the Jetty Server configuration section in <Creo Elements/Direct Manager Server installation location>ServiceControllerConfig.xml file. For example:
<Service enabled="true" java_class="com.osm.services.webservice.JettyServer" name="JettyServer">
... <War context="/mmweb" location='webapps/mmweb/'/> <War context="/ mmweb_dev" location='webapps/mmweb_dev//> <War context="/" location="webapps/OSMWebServices.war"/> ... c. Type http://<server>:8580/mmweb_dev/ in a browser to test the web application. For example, http://localhost:8580/mmweb_dev/.
|
4. Login Authentication: The web client login authentication is configured in the web.xml file located in the <Creo Elements/Direct Manager Server installation directory>\webapps\mmweb\WEB-INF directory. You can specify one of the following types of authentication.
◦ Basic authentication - User name and password must be provided to log on.
◦ Forms-based authentication - An editable form must be filled and submitted to log on.
By default, the basic authentication is enabled. For example,
<!-- basic authentication -->
<login-config>
<auth-method>BASIC</auth-method>
<realm-name>osmRealm</realm-name>
</login-config>
<!-- forms authentication -->
<!--
<login-config>
<auth-method>FORM</auth-method>
<realm-name>osmRealm</realm-name>
<form-login-config>
<form-login-page>/login.jsp</form-login-page>
<form-error-page>/error.jsp</form-error-page>
</form-login-config>
/login-config>
<login-config>
<auth-method>BASIC</auth-method>
<realm-name>osmRealm</realm-name>
</login-config>
<!-- forms authentication -->
<!--
<login-config>
<auth-method>FORM</auth-method>
<realm-name>osmRealm</realm-name>
<form-login-config>
<form-login-page>/login.jsp</form-login-page>
<form-error-page>/error.jsp</form-error-page>
</form-login-config>
/login-config>
|
|
Only one authentication type can be enabled at a time.
|
5. Additional Functions: The web client uses the Creo Elements/Direct Manager Web Services to communicate with the database. The available web services provide powerful and efficient query functions as well as some update functions. In addition, the web services can easily be extended by custom Java methods. For details, see the Web Service Customization. These extensions can readily be used by the web client to extend the available functions. For an example, see Add a Reserve button to the web page.