...
This document is intended to describe how to create a maven overlay project to build your own instance of the Scheduling Assistant configured for your Oracle Communications Suite Calendar Server instance.
These instructions are largely identical to those in Deploying the Scheduling Assistant - Bedework. The University of Wisconsin-Madison has verified these instructions work with version "7u1-1.11."
Prerequisites
You'll need the following before you begin:
...
The Scheduling Assistant needs super user credentials for your Oracle Communications Suite Calendar Server instance in order to create and manipulate appointments on behalf of the participants. The 'calmaster' user meets these requirements, you may wish to create a separate account for use by the Scheduling Assistant. If you create a separate account, it needs to be a "memberOf" the following LDAP group:
| No Format |
|---|
cn=Service Administrators,ou=Groups,o=isp |
Creating the war overlay project
...
- Download the sample overlay project at https://mywebspace.wisc.edu/npblair/jasig/my-sched-assist-oraclecommssuite-war-1.0.2.zip and unzip on your filesystem.
The released versions of the Scheduling Assistant come pre-configured to talk to a Oracle Communications Suite Calendar Server instance. All you need to provide is a properties file that contains the hostnames, ports, usernames and passwords to integrate with your environment. Directly under your my-sched-assist-oraclecommssuite-war directory, open the file with the path:
No Format src/main/resources/scheduling-assistant.properties- Edit the properties according to the comments. It is critical that you change the values of the ws.username and ws.password properties from the default to avoid being vulnerable to untrusted web service requests.
- Once the properties file matches your environment, save the file.
- You should also edit 'src/main/webapp/META-INF/context.xml' to match the JDBC credentials for the database; by default this file contains the credentials for the HSQL database that can be started from the Scheduling Assistant source.
Execute the following command from the root of your my-sched-assist-war directory:
No Format mvn package- This will download the version of the Scheduling Assistant specified in the pom.xml and add your configuration. The result will be a war file named 'my-scheduling-assistant.war' in the target sub-directory.
...
Creating an overlay of the portlet
You can't deploy the portlet without having an instance of the Scheduling Assistant running, so be sure to follow the 'Creating the war overlay project' steps first.
- Download the sample portlet overlay project at https://mywebspace.wisc.edu/npblair/jasig/my-sched-assist-portlet.zip and unzip on your filesystem.
- Directly under your my-sched-assist-portlet directory, open the file with the path:
No Format src/main/resources/scheduling-assistant.properties - Edit the properties to match your Scheduling Assistant instance. Note that the portlet doesn't interact with your Oracle Communications Suite Calendar Server instance, database, or LDAP; it communicates completely through the Scheduling Assistant web services endpoint.
- Execute the following command from the root of your my-sched-assist-portlet directory:
No Format mvn package - This will download the version of the Scheduling Assistant portlet specified in the pom.xml and add your configuration. The result will be a war file named 'my-scheduling-assistant.war' in the target sub-directory.
This war file can be published to a JSR-168 Portlet Container (like uPortal).The Scheduling Assistant portlet requires no custom configuration for use with an Oracle Communications Suite environment. Follow the instructions in the Bedework documentation: