Getting started with the Blue Cedar Platform

The Blue Cedar Platform helps to streamline mobile app deployments without costly re-coding. Enterprise DevOps teams use Blue Cedar to orchestrate post-development app enhancement, security, compliance, and release activities for rapid app deployment. 

The steps to get started using the Blue Cedar Platform are similar for new and existing Blue Cedar customers. Depending on your company’s needs, some of these initial steps may be performed with onboarding assistance from Blue Cedar. Skip ahead depending on whether you are a user or the person responsible for Platform administration.

1. Receive login credentials
2. Set up users
3. Configure extensions
4. Import your first app
5. Create and run a workflow

Data is private within a single organization. Nobody else can access the apps or data owned by another organization, even within the same company. For example, a multinational company might have several organizations representing distinct business units or regions. An organization is essentially a tenant, and represents a collection of users who all have access to the same data and features. All users in an organization have access to that organization's data and features.

Receive administrator login credentials

The process starts with the person who is your company’s designated Organization administrator. Blue Cedar sends an email to this person with a username that is already associated with the customer's Organization. This email provides a link for the user to create a password upon first login.

Set up users

Your organization's Blue Cedar Platform administrator can set up other users on the Blue Cedar Platform as described in Managing Users. Users are the individuals who will use Blue Cedar to perform various deployment activities. Your Blue Cedar licensing agreement contains specific information about the users, apps, and Blue Cedar features that are available to your company.

Configure extensions

Extensions are the mechanism used within the Blue Cedar Platform to access functionality that is encapsulated in services. In other words a Blue Cedar service represents an area of functionality. In order to use Blue Cedar functionality for things like importing apps from GitLab, or BlackBerry UEM distribution, you have to configure those extensions with company-specific values as described in Configuring Extensions. For example, you have to create and upload signing credentials in order to use Blue Cedar’s External Signing extension.

Depending on how your company is organized, the Platform administrator may configure Blue Cedar extensions, or individual users responsible for certain portions of the app workflow might configure the extensions associated with a task such as creating keystores for app signing extension, or GitHub repositories for importing apps from GitHub.

Import your first app

In order to create a workflow, start by importing a mobile app binary executable file, as described in Creating an App. This actually creates a container for the mobile app binary, also known as an App Folder.

Create and run a workflow

After you've created your first App Folder, you can see it listed on the App Folder Info screen. At this point, you can create a workflow for the App as described in Working with Workflows.

Using the documentation

This Help Center is available through the Blue Cedar Platform, and also directly from www.bluecedar.com. If you click Help > Help on this screen from any screen in the Platform, the Help page that’s specific to that screen opens. From there, you can traverse anywhere within the Help center as needed.