Configuring Release Automation (Nolio) Communication in Release Manager

You must configure Release Automation (Nolio) properties on the Serena Release Manager server so that Serena Release Manager can connect to and communicate with Release Automation (Nolio). To do this, you must do the following:

Specifying Client-Specific Information for Release Automation

You must specify the client-specific information for Release Automation (Nolio) to set time out and wait values and states that indicate success or failure.

To specify the Serena Release Automation client-specific information:

  1. Navigate to the Serena Release Manager common Tomcat Web server classes folder. For example:

    ..\Program Files\Serena\common\tomcat\6.0\webapps\alm\WEB-INF\classes

  2. Open the nolio-client.properties file.

  3. Set the properties for the client as follows:

    Parameter Value

    nolio.job.runprocess.timeout

    Indicates how long to wait until a timeout message is received.

    nolio.job.runprocess.wait

    Indicates whether to run the Release Automation (Nolio) process in wait mode. Values are true and false.

    nolio.job.state.success

    List of Release Automation (Nolio) job states that indicate success, delimited by commas.

    nolio.job.states.failure

    List of Release Automation (Nolio) job states that indicate failure, delimited by commas.

Example

This example sets the values needed to retrieve successful and failed job notifications from Release Automation (Nolio).

nolio-client.properties

nolio.job.runprocess.timeout=0

nolio.job.runprocess.wait=false

nolio.job.state.success = FLOW_FINISHED

nolio.job.states.failure = BLOCKED,CREATION_FAILED,FILES_DISTRIBUTION_FAILED,

FILES_PROPAGATION_FAILED,FLOW_FAILED_PAUSED,PRE_FAILED,FLOW_STOPPED

Specifying Release Automation (Nolio) Queries

You may specify SQL queries for the information you want returned from Release Automation (Nolio).

To specify the Release Automation (Nolio) connection information:

  1. Navigate to the Serena Release Manager common Tomcat Web server classes folder. For example:

    ..\Program Files\Serena\common\tomcat\6.0\webapps\alm\WEB-INF\classes

  2. Open the nolio-client-queries.properties file.

  3. Set the properties for the queries as follows:

    Parameter Value

    query.get.applications

    SQL queries to return the set of applications, environments, processes, and servers you want for the automation deployment tasks. For the default queries, see the example.

    query.get.environments

    query.get.processes

    query.get.servers

    query.find.application

    query.get.job.status

    message.application.not.found

    Message to send if applications aren’t found.

    message.environment.not.found

    Message to send if environments aren’t found.

Example

This example shows the default SQL queries for Release Automation (Nolio).

nolio-client-queries.properties

query.get.applications = select app_name from applications where id!=1

query.get.environments = select name from environments where id!=1 and applicationId = ?

query.get.processes = select process_name from process_container pc, process_in_env pe where pc.id = pe.process_id and pe.environment_id = ? order by process_name

query.get.servers = select s.server_name, st.server_type_name from servers s, server_types st, server_type_instance sti where s.id = sti.mapped_server and st.id = sti.server_type and sti.environment_id = ?

query.find.application = select id from applications where app_name = ?

query.find.environment = select id from environments where name = ? and applicationId = ?

query.get.job.status = select step_title,step_state from step_events where id in (select MAX(id) from step_events where job_id=?)

message.application.not.found = Could not find specified application: {0}

message.environment.not.found = Could not find specified environment: {0}