...
Cloudaware is a SaaS-based cloud management application. The application runs entirely in Force.com container architecture, also known as App Cloud. This allows Cloudaware to delegate many scalability and security challenges to SFDC.
...
Management, Integration And Development Tools And Services
The Force.com platform and Cloudaware offer management, integration, and development tools and services, including SSO, APIs, and application coding languages that can be used to automate administration and system functionality. The following is a list of the primary tools and services that are available for customers:
...
Single sign-on, Federated authentication using Security Assertion Markup Language (SAML): Allows customers to send authentication and authorization data between affiliated but unrelated Web services. Enables customers to sign on to Cloudaware from a client application. When federated authentication is enabled, Salesforce does not validate a user's password. Instead, Salesforce verifies an assertion in the HTTP POST request, and allows single sign-on if the assertion is true. Federated authentication using SAML is available by default.
Single sign-on, Delegated authentication: Enables customers to integrate Cloudaware with a customer-selected authentication method including Lightweight Directory Access Protocol (LDAP) server, or performs single sign-on by authenticating using a token instead of a password. Delegated authentication is managed by the customer at the Profile level, allowing some users to use delegated authentication, while other users continue to use their Salesforce-managed password. When delegated authentication is enabled, Salesforce does not validate a user's password. Instead, Salesforce makes a Web services call to the customer organization to establish authentication credentials for the user. This feature must be requested by the customer and enabled by Cloudaware.
Single sign-on, External Authentication Providers: Enables customer users to log into their Cloudaware Org using their login credentials from an external service provider. In order to implement Authentication Providers for single sign-on customers must first configure the service provider's website, create a registration handler using Apex, and define the authentication provider for their organization. Any service provider that supports the OpenID Connect protocol is supported. Customers implementing IP Range restrictions for user logins and/or session locking, are not able to use the Authentication Providers option for single sign-on.
External Data API: Used to upload external data files to Cloudaware. The External Data API can upload .csv, .gz, or .zip files and edit existing datasets by uploading a new .csv file. Using the External Data API provides options to overwrite all records, append records, update records, and delete records.
SOAP API, previously known as the Web Services API: Used to create, retrieve, update, or delete records in the Force.com platform from any external system that supports SOAP-based Web services, including Java, .NET, or PHP client applications. With more than 20 different calls, the API also allows users to maintain passwords, perform searches, retrieve metadata information about objects and more.
Metadata API: Used to retrieve, deploy, create, update or delete customization information, including custom object definitions and page layouts (XML representations), for an organization. The most common usage is to migrate changes from a sandbox or testing organization to a production organization. Metadata API is intended for managing customizations and for building tools that can manage the metadata model, not the data itself.
Bulk API: Provides programmatic access to allow users to quickly load their organization's data into Cloudaware. The Bulk API allows the user to insert, update, upsert or delete a large number of records asynchronously.
Chatter REST API: Used to integrate mobile apps, intranet sites, and third-party Web applications with Chatter. The Chatter REST API provides resources for feeds, comments, likes, users, groups, private messages, and recommendations. The Chatter REST API is on by default in all organizations and editions that have Chatter.
Chatter in Apex: Exposes many Chatter API resources as objects in Apex and can be used to build Chatter integrations and custom UI on Force.com without making HTTP callouts to the Chatter API. Tooling API provides SOAP and REST interfaces that allow customers to build custom development tools for Force.com platform applications.
Streaming API: Allows customers to expose a near real-time stream of data from Force.com platform. Administrators can create topics, to which applications can subscribe, receiving asynchronous notifications of changes to data on Force.com platform.
REST API: Search Scope and Order. The scope and order call in the REST API returns an ordered list of objects in the default global search scope of a logged-in user. The global search keeps track of which objects the user interacts with and how often and arranges the search results accordingly. The objects used most frequently appear at the top of the list.
Apex REST API: Enables developers to create their own REST-based web services using Apex. It has all of the advantages of the REST architecture, provides the ability to define custom logic, and includes automatic argument/object mapping.
Apex SOAP API: Apex SOAP Web services allow an external application to invoke Apex methods through SOAP Web services. Apex callouts enable Apex to invoke external Web or HTTP services.
Apex: A programming language supported on the Force.com platform that allows users to perform functions including: creating Web and email services; performing complex validation over multiple objects; creating complex business processes that are not supported by workflow; creating custom transactional logic (logic that occurs over the entire transaction, not just with a single record or object); and attaching custom logic to another operation, including saving a record, so that it occurs whenever the operation is executed.
Visualforce: A tag-based markup language that gives developers a more powerful way of building applications and customizing the user interface. With Visualforce, customers can build wizards and other multi-step processes, create custom flow control through an application, and define navigation patterns and data-specific rules for optimal, efficient application interaction.
Salesforce Object Query Language (SOQL): Used to construct simple but powerful query strings. The SOQL can be used in query calls, in Apex statements, in Visualforce controllers and getter methods, and in the Schema Explorer of the Eclipse Toolkit. Similar to the SELECT command in Structured Query Language (SQL), SOQL allows users to specify the source object (e.g. Account), a list of fields to retrieve, and conditions for selecting rows in the source object. Creates new objects and updates existing objects; uses a custom field to determine the presence of existing objects. Upsert is a merging of the words insert and update. This call is available for objects if the object has an external ID field or a field with the idLookup field property. On custom objects, this call uses an indexed custom field called an external ID to determine whether to create a new object or update an existing object. On standard objects, this call can use the name of any field with the idLookup field property instead of the external ID.
Salesforce Object Search Language (SOSL): Used to construct searches for text, email, and phone fields for multiple objects simultaneously. The SOQL can be used in query calls, in Apex statements, in Visualforce controllers and getter methods, and in the Schema Explorer of the Eclipse Toolkit. SOSL allows customers to specify the following for source objects: text expression; scope of fields to search; list of objects and fields to retrieve; and conditions for selecting rows in the source objects.