Checking out the Activities configuration files 

You can edit the Activities configuration files in two ways: by using the wsadmin client or by editing the configuration XML files directly. In both cases, first check out the configuration files and later check them back in using the wsadmin client.


Procedure

  1. Start the wsadmin client by completing the following steps:

    1. From the dmgr host, go to...:

        app_server_root\profiles\<dm_profile_root>\bin

        where app_server_root is the WAS installation directory and <dm_profile_root> is the dmgr profile directory, typically dmgr01. For example, on Windows:

        C:\Program Files\IBM\WebSphere\AppServer\profiles\Dmgr01\bin

        Attention: You must run the following command to start the wsadmin client from this specific directory because the Jython files for the product are stored here. If you try to start the client from a different directory, then the execfile() command that you subsequently call to initialize the administration environment for an IBM Connections component does not work correctly.

    2. Enter the following command to start the wsadmin client:

      • AIX or Linux:

          ./wsadmin.sh -lang jython -user <admin_user_id> -password <admin_password> -port <SOAP_CONNECTOR_ADDRESS Port>

      • Microsoft Windows:

          wsadmin -lang jython -user <admin_user_id> -password <admin_password> -port <SOAP_CONNECTOR_ADDRESS Port>

        where:

        • <admin_user_id> is the user name of a person in the Administrator role on the IBM WAS.

        • <admin_password> is the password of the WAS administrator.

        • <SOAP_CONNECTOR_ADDRESS Port> is the SOAP port for the WAS. The default value of the SOAP port is 8879. If you are using the default port value, you do not need to specify this parameter. If you are not using the default and you do not know the port number, you can look up its value in the WAS Integrated Solution Console. To look up the SOAP port number, perform the following steps:

          1. Open the WAS Integrated Solution Console for the deployment manager, and then select System Administration -> dmgr.

          2. In the Additional properties section expand Ports, and then look for the SOAP_CONNECTOR_ADDRESS port entry to find the port number.

        For example:

        • AIX or Linux:

            ./wsadmin.sh -lang jython -username primaryAdmin -password p@assword -port 8879

        • Microsoft Windows:

            wsadmin -lang jython -username primaryAdmin -password p@assword -port 8879

  2. Access and check out the Activities configuration files.

    1. Access the Activities configuration file:

        execfile("activitiesAdmin.py")

        If prompted to specify a service to connect to, type 1 to pick the first node in the list. Most commands can run on any node. If the command writes or reads information to or from a file using a local file path, pick the node where the file is stored.

    2. Check out the Activities configuration files using the following command:

        ActivitiesConfigService.checkOutConfig("<working_directory>","<cell_name>")

        where:

        • <working_directory> is the temporary working directory to which the configuration XML and XSD files are copied and are stored while you make changes to them. Use forward slashes to separate directories in the file path, even if you are using the Microsoft Windows operating system.

            Note: AIX and Linux only: The directory must grant write permissions or the command will not run successfully.

        • <cell_name> is the name of the WAS cell hosting the IBM Connections application. This argument is case-sensitive, so type it with care. If you do not know the cell name, you can determine it by typing the following command in the wsadmin command processor:

            print AdminControl.getCell()

        For example:

        • AIX/Linux:

            ActivitiesConfigService.checkOutConfig("/opt/act/temp","foo01Cell01")

        • Microsoft Windows:

            ActivitiesConfigService.checkOutConfig("c:/act/temp","foo01Cell01")

  3. Optional: If you want to find out the current value of a property, you can list the current configuration settings and values using the following command:

      ActivitiesConfigService.showConfig()

  4. Some properties must be edited using the wsadmin client; others can only be edited by editing the configuration XML file directly. To change an Activities configuration setting, do one of the following command:

    • To edit a property using the wsadmin client, use the following command:

        ActivitiesConfigService.updateConfig("<property>","<value>")

    • where <property> is one of the editable Activities configuration properties and <value> is the new value with which you want to set that property. See Activities configuration properties for a complete list of editable properties. For example:

        ActivitiesConfigService.updateConfig("activeContentFilter.enabled", "true")

    • To edit the value of a property in a configuration file directly, from the temporary directory to which you checked it out, open the file in a text editor, and then make your changes.


What to do next


After making changes, check the configuration files back in and do so during the same wsadmin session in which you checked them out for the changes to take effect. See Apply property changes for details.


Parent topic

Change Activities configuration property values
Next topic: Activities configuration properties


November 18, 2011 10:22:36 AM
   

 

Nov 18, 2011 10:22:36 AM Removed angle brackets because cannot get it to format correctly in th... 3 Nov 18, 2011 10:21:30 AM Fixing formatting 2 Nov 18, 2011 10:20:41 AM Added left angle bracket in front of app_server_root. 1

});