Install the default schedule calendars 

Install the default scheduling calendars on the servers that host the Home page application.


About this task

After installing the Home page global search functionality, you need to ensure that the default scheduling calendars are installed on the servers that are hosting the Home page. This is only required if IBM Connections is deployed on a cluster or in a stand-alone deployment with multiple profiles.

The default scheduler SIMPLE and CRON calendars are available in the SchedulerCalendars.ear system application. They are automatically installed on stand-alone deployments. However, in a network deployment environment, install the default calenders manually. System applications cannot be installed and uninstalled like traditional J2EE applications.

This task uses Jython commands to install the calendars.

Note: When the scheduler is defined at cluster scope, the lease for the scheduler can be claimed by a server that does not have the Home page deployed to it, so remove the scheduler on that server. For more information, see the IBM Connections scheduler incorrectly appears in cluster scope technote.

Complete the following steps to map the SchedulerCalendars.ear application to a stand-alone server or a cluster in a network deployment:


Procedure

  1. Open a command window and start the wsadmin command line tool. For more information, refer to the Starting the wsadmin client topic.

  2. Install the system application.

    • To install on a stand-alone server, use the following Jython command:

        wsadmin>AdminApp.install('${app_server_root} /systemApps/SchedulerCalendars.ear',' [-systemApp -appname SchedulerCalendars -cell <mycell> -node <mynode> -server <myserver>]')

    • where:
      Value Parameter
      <mycell> is the name of the cell
      <mynode> is the name of the node
      <myserver> is the name of the server


    • To install on a cluster, use the following Jython command:

        wsadmin>AdminApp.install('${app_server_root} /systemApps/SchedulerCalendars.ear',' [-systemApp –appname SchedulerCalendars -cell <mycell> -node <mynode>-cluster <mycluster>]')

    • where:
      Value Parameter
      <mycell> is the name of the cell
      <mynode> is the name of the node
      <mycluster> is the name of the cluster


      Note: Run the command only on the primary node of the cluster. You do not need to run the command on the secondary nodes. If you are not sure which is the primary node, see the Determining the primary node topic.

  3. Use the following Jython command to save the configuration changes.

      wsadmin>AdminConfig.save()

    • where:
      Header Header
      AdminConfig is an object representing the WAS configuration
      save is an AdminConfig command


        If you are using interactive mode with the wsadmin tool, you are prompted to save your changes before they are discarded.

        If you are using the -c option with the wsadmin tool, changes are automatically saved. On a Unix operating system, if you invoke a command that includes a dollar sign character ($) using the wsadmin -c option, the command line attempts to substitute a variable. To avoid this problem, escape the dollar sign character with a backslash character (\). For example: wsadmin -c "\$AdminConfig save".

        If a scripting process ends and no save has been performed, any configuration changes made since the last save are discarded. If there are multiple clients (scripts or browser clients) updating the configuration at the same time, it is possible that the changes requested by a script might not be saved. If this happens, you receive an exception and make the updates again. If the save fails, the updates are not saved to the configuration. If it succeeds, all updates are saved. To avoid save failures, you can invoke the save command after every configuration update.

        You can use the reset command of the AdminConfig object to undo changes that you made to your configuration since your last save.

Example

Example of the Jython command:

wsadmin>AdminApp.install('c:/demo/application1.ear', '[-server demoserver]')



What to do next

The page size is optimized by IBM Connections during installation. However, if the indexing process is too slow, you can try to improve it by resetting the page size.


Related tasks


Starting the wsadmin client


   

 

});