From ControlTier

Contents 1 Overview 2 Problems 2.1 load-resources command fails: no object exists 2.2 load-resources command fails: project not found 3 Solutions 3.1 Using a different Node name

Overview

If you have problems running one of the Examples, try one of these solutions.

Otherwise, please feel free to Contact Us via IRC, or email to the Mailing List.

Problems

load-resources command fails: no object exists

When running load-resources you get this message:

ctl -p demo -m ProjectBuilder -c load-resources -- -filename projectbuilder.xml
...

Command failed: The following error occurred while executing this line:
...
/Users/greg/ctier2/ctl/projects/demo/modules/ProjectBuilder/lib/load-resources/projectxml/antlib.xml:62: \
  Error performing server request: no object exists by that name and type: type: Node, name: somenode

This is caused when the name of the node specified in projectbuilder.xml doesn't match the default Node named for your project.

• See: #Using a different Node name to fix this issue.

load-resources command fails: project not found

ctl -p demo -m ProjectBuilder -c load-resources -- -filename projectbuilder.xml
project not found: 'demo'

You need to create a new project named 'demo' in the ControlTier Server.

See: Using the Examples#Create a New Project for instructions.

Solutions

Using a different Node name

To change the Node name that is used from the default of "localhost", you should edit this file:

1. projectbuilder.xml

Change the <referrers> section:

<referrers>
<resource type="Node" name="localhost"/>
</referrers>

Replace "localhost" with your Node name.

Double-check the file templates/defaults.xml.

This file should specify the default node name using the one configured for your ControlTier installation. The value will be "${framework.node.name}".

You should not find it necessary to change this, but if so you can change it here:

<?xml version="1.0"?>
<defaults>
  <default>
 <node>
   <name>${framework.node.name}</name>
   <type>${framework.node.type}</type>
 </node>

Change "${framework.node.name}" to the name of your Node.