Access Server Configuration Files

The Cantara Access Server uses three configuration files: configuration.xml, environments.xml and security.xml. In most cases, you would modify the files using the Cantara Administration Console instead of editing them directly. The only exception is defining the administrator username and password for managing the configuration of the server, which can only be changed by directly editing the configuration.xml file.

configuration.xml

The configuration.xml file is located in the WEB-INF folder in the deployed application. This file defines the folder location for the environment.xml configuration file, the folder in which the component service definitions are stored, and the log level and log file that is used by the server.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Controller>
    <EnvironmentFolder>/var/Cantara</EnvironmentFolder>
    <ComponentFolder>/var/Cantara</ComponentFolder>
    <Log level="ERROR">/var/Cantara/system.log</Log>
	<Administrator username="admin" password="MySecurity"/>
</Controller>

environments.xml

The environments.xml file is located in the folder specified in the configuration.xml file. This file defines the JD Edwards enterprise servers and JD Edwards environments that the Cantara Access Server can communicate with. You create and manage these environments using the Cantara Administration Console. You can define multiple environments; each must have a unique name attribute.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<CantaraEnvironment>
    <EnvironmentDefinition 
		application="Cantara"
        timeout="180" 
		environment="PD910"
		port="6016"
        hostname="jde.rinami.com"
		name="E1PROD"/>
	<EnvironmentDefinition
		application="Cantara"
		timeout="180"
		environment="PY910"
		port="6016"
		hostname="jdetest.rinami.com"
		name="E1TEST"/>
</CantaraEnvironment>

security.xml

The security.xml file is located in the same folder as the environments.xml file. This file stores the security token configuration and currently issues security tokens for the server. You create and manage the security configuration using the Cantara Administration Console.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<CantaraSecurity expiryDays="14" passPhrase="Sample">
    <User 
		username="jbloggs"
        password="okQIKNForbAsheSVk/LPXg==" 
		environment="PD910"
		token="4600998d37d4e6d14d5de632f810f5cb115920245581ed859eb9a55b8d851093"
        dateCreated="2014-08-28+10:00"
		application="Cantara Console"/>
	<SecuritySubscriber 
		name="Weblogic12"
		endpoint="http://web04.rinami.aus:9171/cantara" 
		username="admin"
		password="sample"
		environment="*ALL"/>
</CantaraSecurity>