A customer subscribed to a Service Plan with the StopTheHacker APS application.
The task to install the StopTheHacker APS application fails in POA with the error message 'Target missing' like in the following example:
Task ID 9408387
Queue name aps_application_instance2991
Task name APS application 'StopTheHacker_Website_Security_All_Inclusive', id 391, instance 2991 -> service 'context', instance 4901: executing configuration script
Task description APS application 'StopTheHacker_Website_Security_All_Inclusive', id 391, instance 2991 -> service 'context', instance 4901: executing configuration script
Belongs to groups provision_application_instance_resource_487119_79889991
Subscription ID 1019468
Queue status Rescheduled
Start not earlier than Dec-26-2012 09:39
Method name taskExecuteApplicationInstanceScript on OBJREF:SaaSManagerTasks:0:getAPSExternalTasks:0
Last execution output
Execution of configuration script for instance with id 4901 of service with id context of instance with id 2991 of application with id 391 failed - returned value: -1 output: '<?xml version="1.0"?>
<error id="111" setting-id="domain">
' errors: ''
The StopTheHacker application requires a domain to bind application instance to, while POA did not specify any domain during the application installation. In the failed task properties it may be seen that the parameter env_var_SETTINGS_domain has empty value.
The reason of the problem is misconfigured APS application resource type or Service Template a customer subscription is based on.
In order to make POA to pass a domain during the StopTheHacker APS application installation corresponding resource type based on the resource class Application must be configured in the proper way.
1. Either of the activation parameters Provision application on account's domain or Provision application on vendor's domain must be enabled.
If the first parameter is enabled a customer will be able to add domain to their account in PA Customer Panel (or purchase a domain in the Online Store) and then provision the application on own domain. In the second case a customer will be able to provision application using automatically generated subdomain in a Provider's domain configured in the resource properties (the Base domain parameter).
2. The parameter Automatically provision application should be set to No. This will prevent problem when POA is trying to install application in a customer subscription when customer does not have any domain in their account yet.
The activation parameters configured in a resource type may be re-defined in a Service Template which has the resource included, so check not only resource type, check Service Template parameters as well.
In case of Service Template the activation parameters have another names:
- The Provision application on account's domain activation parameter in resource type corresponds to the Bind application to domain in Service Template parameters
- The Provision application on vendor's domain activation parameter in resource type corresponds to the Bind application to auto-generated domain in Service Template parameters