The cloud service exposes meta data that can provide additional information about the various properties that might be returned.This example shows how to access this data and display the values available.

A list of the properties will be displayed, along with some additional information about each property. Note that this is the list of properties used by the supplied resource key, rather than all properties that can be returned by the cloud service.

In addition, the evidence keys that are accepted by the service are listed. These are the keys that, when added to the evidence collection in flow data, could have some impact on the result that is returned.

Bear in mind that this is a list of ALL evidence keys accepted by all products offered by the cloud. If you are only using a single product (for example - device detection) then not all of these keys will be relevant.

This example is available in full on GitHub.

To run this example, you will need to create a resource key. The resource key is used as shorthand to store the particular set of properties you are interested in as well as any associated license keys that entitle you to increased request limits and/or paid-for properties.

You can create a resource key using the 51Degrees Configurator.

Required Composer Dependencies:

51degrees/fiftyone.devicedetection

<?php

/* *********************************************************************

* This Original Work is copyright of 51 Degrees Mobile Experts Limited.

* Forbury Square, Reading, Berkshire, United Kingdom RG1 3EU.

*

* This Original Work is licensed under the European Union Public Licence

* (EUPL) v.1.2 and is subject to its terms as set out below.

*

* If a copy of the EUPL was not distributed with this file, You can obtain

* one at https://opensource.org/licenses/EUPL-1.2.

*

* The 'Compatible Licences' set out in the Appendix to the EUPL (as may be

* amended by the European Commission) shall be deemed incompatible for

* the purposes of the Work and the provisions of the compatibility

* clause in Article 5 of the EUPL shall not apply.

*

* If using the Work as, or as part of, a network application, by

* including the attribution notice(s) required under Article 5 of the EUPL

* in the end user terms of the application under an appropriate heading,

* such notice(s) shall fulfill the requirements of that article.

* ********************************************************************* */

require_once(__DIR__ . "/exampleUtils.php");

require_once(__DIR__ . "/../../vendor/autoload.php");

use fiftyone\pipeline\devicedetection\DeviceDetectionPipelineBuilder;

use fiftyone\pipeline\core\PipelineBuilder;

use fiftyone\pipeline\core\Logger;

class MetaDataConsole

{

public function run($resourceKey, $logger, callable $output)

{

$pipeline = (new DeviceDetectionPipelineBuilder(array("resourceKey" => $resourceKey)))

->addLogger($logger)

->build();

$this->outputProperties($pipeline->getElement("device"), $output);

// We use the CloudRequestEngine to get evidence key details, rather than the

// DeviceDetectionCloudEngine.

// This is because the DeviceDetectionCloudEngine doesn't actually make use

// of any evidence values. It simply processes the JSON that is returned

// by the call to the cloud service that is made by the CloudRequestEngine.

// The CloudRequestEngine is actually taking the evidence values and passing

// them to the cloud, so that's the engine we want the keys from.

$this->outputEvidenceKeyDetails($pipeline->getElement("cloud"), $output);

}

private function outputEvidenceKeyDetails($engine, callable $output)

{

$output("");

if (is_a($engine->getEvidenceKeyFilter(), "fiftyone\\pipeline\\core\\BasicListEvidenceKeyFilter"))

{

// If the evidence key filter extends BasicListEvidenceKeyFilter then we can

// display a list of accepted keys.

$filter = $engine->getEvidenceKeyFilter();

$output("Accepted evidence keys:");

foreach ($filter->getList() as $key)

{

$output("\t$key");

}

else

{

output("The evidence key filter has type " .

$engine->getEvidenceKeyFilter().". As this does not extend " .

"BasicListEvidenceKeyFilter, a list of accepted values cannot be " .

"displayed. As an alternative, you can pass evidence keys to " .

"filter->filterEvidenceKey(string) to see if a particular key will be included " .

"or not.");

output("For example, header.user-agent is " .

($engine->getEvidenceKeyFilter().filterEvidenceKey("header.user-agent") ? "" : "not ") .

"accepted.");

}

private function outputProperties($engine, callable $output)

{

foreach ($engine->getProperties() as $property)

{

// Output some details about the property.

$output("Property - ".$property["name"] . " " .

"[Category: ".$property["category"]."] (".$property["type"].")");

}

};

// Only declare and call the main function if this is being run directly.

// This prevents main from being run where examples are run as part of

// PHPUnit tests.

if (basename(__FILE__) == basename($_SERVER["SCRIPT_FILENAME"]))

{

function main($argv)

{

// Use the command line args to get the resource key if present.

// Otherwise, get it from the environment variable.

$resourceKey = isset($argv) && count($argv) > 0 ? $argv[0] : ExampleUtils::getResourceKey();

$logger = new Logger("info");

if (empty($resourceKey) == false)

{

(new MetaDataConsole())->run($resourceKey, $logger, ["ExampleUtils", "output"]);

}

else

{

$logger->log("error",

"No resource key specified in environment variable " .

"'".ExampleUtils::RESOURCE_KEY_ENV_VAR."'. The 51Degrees " .

"cloud service is accessed using a 'ResourceKey'. " .

"For more detail see " .

"http://51degrees.com/documentation/4.3/_info__resource_keys.html. " .

"A resource key with the properties required by this " .

"example can be created for free at " .

"https://configure.51degrees.com/1QWJwHxl. " .

"Once complete, populate the environment variable " .

"mentioned at the start of this message with the key.");

}

main(isset($argv) ? array_slice($argv, 1) : null);

}

51Degrees Device Detection PHP 4.4

cloud/metadataConsole.php