Home > Blogs > VMware {code}

Getting Started with the vSphere Automation SDK for Java

There has been another exciting open-sourced release in the vSphere Automation SDK lineup. This time, it is the vSphere Automation SDK for Java!

That means it’s time for another blog post in our series on ‘Getting Started with the vSphere Automation SDKs’. The posts available in the series so far are as follows:

We’ll be taking a look at how to easily get started with this SDK on a Mac. Before diving in, there are a couple prerequisites we’ll need to download and install.


The first thing we’ll want to do before getting started with this SDK is to clone the repository to the local system. We can do that with the following command:

Example: cloning repo local

Next, we’ll want to make sure we have the appropriate Java Development Kit (JDK) installed and available. The vSphere Automation SDK for Java has been developed to work with JDK 1.8. We can verify which version of Java is available by the following command:

Example: java version output

In this situation, my system doesn’t have Java installed at all. I’ll need to head out to the JDK8 download page to download and install the appropriate version. Once complete, repeat the last command to ensure JDK 1.8 is installed. Verifying and/or updating the JAVA_HOME and PATH variables is the last step to the install process. We’ll start by finding the current value for the JAVA_HOME variable, then updating it, if necessary, to the Home directory of the newly installed JDK. We’ll then repeat that process for the PATH variable as well. This can be done with the following commands:

Example of updating system variables

We will also need to ensure Maven, a build automation tool, is installed. We will use Maven to build out the SDK and the samples from source so we can start using it. My system doesn’t have Maven installed yet, so we’ll go to the download page and install it according to the instructions on Maven’s site. Alternatively, we can do it with the following commands:

Example of installing Maven

The last prerequisite, before starting to user the SDK, is instructing Maven to build out all the samples with Maven. We’ll first use the initialize command, within the cloned repository directory, to pre-stage any dependencies that are not available publicly. We’ll then follow that with install command. This can be done with the following commands:

Example of downloading SDK prereqs and building out SDK from source

We are now all setup to start using the vSphere Automation SDK for Java!

Running Samples

There are quite a few samples which are included with the SDK. Each sample can be run by using its fully qualified class name.

The first example we’ll take a look at is the ListVMs sample. In terminal, from the root of the SDK directory, we’ll call java, enabling assertions with the ‘ea’ parameter, using the ‘cp’ parameter to call the class path of ‘target/vsphere-samples-6.5.0.jar’, then the fully qualified class name. An example of this command is as follows:

Example parameters available for use with the ListVMs sample in the vSphere Automation SDK for Java

Based on the output, we see quite a few parameters that still need to be referenced in order to authenticate and run the sample. The required parameters are server, username, and password. However, there are also some considerations needed around the handling of the vCenter’s certificate. I’m using a lab environment that still has the vCenter’s self-signed certificate in use, so I’ll be using the ‘skip-server-verification’ parameter. Lastly, there are the optional paramaters, most of which are straight forward, but the config-file parameter is a convenient one. For now, we’ll keep it simple and call each parameter as part of the command. I’ll discuss using a configuration file later in this post.

Performing the ListVMs sample in my environment, with all of the required parameters, looks like the following:

Example output when listing VMs

There’s another sample which takes a VM through the lifecycle of power states. This sample can be discovered in the ‘../vmware/samples/vcenter/vm/power’ directory. The public class we’ll be using is ‘PowerLifeCyle’. If we run that without any parameters, we can see that we’ll need to add the ‘vmname’ parameter and call a specific VM by name. Running this sample can be done with the following command:

Example of taking a VM through the lifecycle of power states

The last example we’ll look at is the modifying the memory configured for a VM. This sample can be found in the ‘../vmware/samples/vcenter/vm/hardware/memory’ directory. The public class we’ll be using is ‘MemoryConfiguration’. If we run that without any parameters, we can see that we will again need to add the ‘vmname’ parameter and call a specific VM by name.

This sample will set the RAM to 8GB then enables hot-add. We can go execute this sample with the following command:

Example of memory configuration options

One last thing before wrapping this up, let’s walk through using the configuration file. The configuration file can be any text-based file which contains lines that begin with the parameter names. In the following example, we create a new file and modify the file to include the following lines:

We can now reference this config file in any of the examples to authenticate against a vCenter server. Reusing the ‘ListVMs’ sample, the command to run that again but instead using a configuration file will look like the following:

Example of using the configuration file


This post shows you how to easily get started with the vSphere Automation SDK for Java. It takes you through the setup of your local development environment, as well as running some of the individual samples. You can then take whichever is most relevant to you and apply to your environment or, pull parts of this code out and use it to automate or integrate as needed.

With our SDKs now being open sourced, we are intent on making sure these samples are of a high quality. If you notice areas of improvement, or come up with some new samples, please feel free to raise issues or pull requests on our GitHub repository.

vSphere Automation SDKs Updated for VMware Cloud on AWS

The vSphere Automation SDKs have recently received an exciting update! These open-sourced SDKs can now also interact with the VMware Cloud on AWS service. The first two SDK languages updated to include this feature set is Python and Java. The remaining SDK languages will follow soon.

The VMware Cloud on AWS service offers a couple different RESTful APIs to interact with. The updated SDKs will focus on the VMware Cloud on AWS (VMC) API, as well as provide the authentication method through the Cloud Services Platform (CSP) API. To find out more about the APIs available as part of the VMware Cloud on AWS service, see this blog post: An Overview of VMware Cloud on AWS APIs

On this initial release, both the Python and Java SDKs include a handful of sample frameworks. These include the following functions:

  • Listing all Organizations associated with a user
  • Creation and removal of an SDDC
  • Managing the host count for a deployed SDDC

Let’s take a look at a couple of these in action.

vSphere Automation SDK for Python

One of the vSphere Automation SDK for Python samples has the functionality to perform two methods. The first will list all of the organizations the user’s refresh token is associated with. These orgs will be displayed by ID and display name. The second will list more detailed information for the first organization, such as ID, display name, name, create and updated dates, and SLA. This sample can be executed with the following command:

Python SDK Sample to list Org information

This SDK also has a new way to interact with the API and that is through the interactive interpreter! This can be done by creating the service object using the ‘create_vmc_client’ function while passing our refresh token. At this point, we can start accessing the available collections. The collections can by discovered in two main ways. First, by referring to the documentation that’s located in the ‘vmc.zip’ file that’s located in the ‘doc’ folder. Second, by using tab-complete. Some example code to obtain similar output to our prior example while in the interactive shell:

Interactive Shell Python Example Usage

vSphere Automation SDK for Java

The vSphere Automation SDK for Java offers a similar sample to the first Python example from above. However, this particular sample operates a little differently. The output from this sample will be the complete details of each org the user is associated with. This sample can be executed with the following command:

Java SDK Sample to list Org information


The open-sourced vSphere Automation SDKs have recently received an update. This update allows these SDKs to work with the RESTful API service of VMware Cloud on AWS. There are also a number of samples available within each SDK to list information about organizations, add and/or remove SDDCs, and manage the host count within an SDDC. These samples are easy to have operational within a few minutes of updating your local repo and are quite simple to integrate into your existing code!

Stay tuned for a more detailed look at getting started with each of these SDKs with the VMware Cloud on AWS service in the future.

For more information about the VMware Cloud on AWS service, see the following blog post: VMware Cloud on AWS Technical Overview
For more information about the VMware Cloud on AWS APIs, see the following blog post: An Overview of VMware Cloud on AWS APIs

VMware {code} Experience On Thursday Dec 14th | Containerized Storage, High Performance Networking with EC2, and MultiCluster Ingress Demo

On Thursday we’re hosting the Kubernetes Meetup group at VMware HQ for our final VMware {code} Experience of 2017! We’ll be hearing from speakers Murat Karslioglu, a VP at CloudByte, Chris Marino, CEO at New Networking Co, and Nikhil Jindal, a Software Engineer at Google on the topics of containerized storage, high performance networking with EC2, and setting up a multicluster ingress. Sound intriguing? Wait until we tell you that we ordered extra BBQ chicken pizza!

The event will kickoff with an opportunity to grab some beer & pizza, and a chance to get to know your neighbor. Please see the complete schedule below. If you’re planning to attend in person make sure to register on Meetup. Can’t make it in person? Not a problem! You can join us and thousands of your others virtually for the livestream on the VMTN Facebook page. See you Thursday!


Thursday, December 14th, 2017
6:00 – 9:00 pm
Prom C Cafeteria, VMware HQ
Watch the livestream on the VMTN Facebook page
Register to Attend on Meetup


6:00 – 6:15 – Networking
6:15 – 6:25 – Introductions
6:25 – 7:20 – 1st talk: Containerized Storage for Containers
10 minute break
7:30 – 8:00- 2nd talk: High Performance Networking in EC2
8:00-8:10 – Demo: Multi-Cluster Ingress Demo

VMware {code} is a free developer program that provides access to a growing community of developers and experts. If you are an existing Developer Center user or partner program member, you can join the new VMware {code} program using your MyVMware account. If you do not have one, register below to access SDKs and participate in developer forums.

Join VMware {code}

Maximize Developer Velocity with Containers: 11/29 VMware {code} Experience Follow-up

VMware {code} Meetup attendees enjoy some beer and pizza while listening to the sessions (Photo credit: Chuck Potter)

Thanks to everyone who attended the VMware {code} sponsored OpenStack Meetup last Wednesday! We had over 50 people join us in person to eat pizza, drink beer, and network at VMware HQ, and almost 1,500 virtual attendees watching the livestream on the VMTN Community Facebook page. Watch the full event below.

Thanks for the great footage OpenTechTV!

Sabari Murugesan (@neosab87), OpenStack Staff Engineer at VMware, led a great session on running Kubernetes on OpenStack. In this session Sabari covered ease of deployment of Kubernetes on OpenStack, the flexible control plane, and the advantages of the cloud provider interface.

Sabari Murugesan – Staff Engineer at VMware (Photo credit: Chuck Potter)

Know what you need before you need it.

Dustin Kirkland (@DustinKirkland), VP of Product Development at Ubuntu, spoke about how to maximize developer velocity with containers, and identified countless cases of where Ubuntu has enabled companies in the container space.

Dustin Kirkland – VP of Product Development at Ubuntu (Photo credit: Chuck Potter)

Trade winds have been used by captains of sailing ships to cross the world’s oceans for centuries.

Please find the slides for Sabari and Dustin’s presentations below:

The sessions were followed by some Q&A with Dustin, as well as 30 minutes of networking with the speakers. Our next VMware {code} Experience is coming up on December 14th, covering Containerized Storage, HighPerf Networking w/ EC2, and MultiCluster Ingress Demo. We hope to see you there!

Join the VMware {code} program for free to chat with other developers on our Slack channel, and to be notified about future VMware {code} Experiences, including Meetups, hackathons, trainings, and more!

An Overview of VMware Cloud on AWS APIs

As part of vSphere 6.5 we revolutionized the programmatic interaction of the product by enabling new REST based APIs and Open Sourced SDKs to provide a developer and automation experience which delighted users. Continuing this work and moving into the cloud we are looking to provide an equal if not better experience with VMware Cloud on AWS.

The new vSphere 6.5 REST APIs which are used to manage both new features of the 6.5 release and some existing features were modernized to provide a superior experience, continuing with this experience, the VMware Cloud on AWS APIs are RESTful, making use of CRUD (Create, Retrieve, Update, Delete) based actions and utilizing JSON formatted inputs and outputs for the data structure. The documentation for these APIs will also be available in numerous ways both online and inline.

There are three main APIs, among several others, which users should be aware of that allow you to programmatically access the VMware Cloud on AWS features and surrounding areas to work with the environment and automate or develop to succeed in your use cases:
VMware Cloud Service API Tree

We will be taking a bit deeper look at the first three in the following sections.

Cloud Services Platform API

The Cloud Services Platform (CSP) APIs are available for all cloud services which are offered by VMware. They contain the core features that customers will use when working with multiple cloud services from VMware.

In the context of VMware Cloud on AWS, the main use of the CSP APIs will be to serve as the authentication point. Once authenticated, the authorization token will be valid against this API as well as the VMware Cloud on AWS API. The CSP API also serves as the main point for Organization (Org) and VMware Cloud on AWS console user management. Some of the methods include displaying all the users within an Org, adding users to an Org, and removing users from an Org.

VMware Cloud on AWS API

The VMware Cloud on AWS (VMC) API will be the endpoint for most actions available within the VMware Cloud on AWS console. This API, which is currently in Technical Preview, allows for SDDC management actions like creating or removing SDDCs with a single API call, adding or removing the elastic hardware provided by the VMC service and adding the ESXi hosts to our SDDC, and handling network operations for the SDDC. We can also gather task based information on items which take place in the VMC environment.

Access to the VMC API is also be available in multiple ways. First off, since this API is RESTful, it can be consumed with your preferred programming language or client which can talk REST. The open-sourced vSphere Automation SDKs can be used as well and are available in programming languages like Python, Java, Ruby, and more. This API can then be explored through a built in API Explorer. The features of VMC can also be accessed through the command line with PowerCLI 6.5.4 and a technical preview of the new version of Datacenter CLI (DCLI). DCLI, which is available as a separate download, can be installed on Windows, MacOS, and Linux. More posts are planned to explain these areas in depth in the future so stay tuned!

Deployed SDDC APIs – vSphere API

The last of the APIs are the vSphere APIs. These are the same APIs you already know and love! You will be able to consume these APIs in the exact same way you already do with our on-premises offerings of vSphere. With VMware Cloud on AWS being a managed environment you will of course have limited permissions and certain key differences on areas which you should deploy to but we will dig into these in a future blog post.


We just reviewed the three API endpoints you will want to become familiar with when accessing VMware Cloud on AWS. The CSP API, which serves as the main authentication point and management point for Orgs and console users. There is the VMC API that is the SDDC management point. Lastly, there are the deployed SDDC APIs themselves which will be the vSphere APIs which hopefully you are already familiar with.

In the next blog, we will cover how to get started using each of these APIs!

VMware {code} OpenStack MeetUp | November 29th | Maximize Developer Velocity with Containers


Wednesday, November 29th, 2017
6:30 – 8:30 pm
Prom C Cafeteria, VMware HQ (see MeetUp event for a map)
Watch the livestream on the VMTN Facebook page



Please join us at VMware headquarters on Wednesday November 29th for an SF Bay Area OpenStack MeetUp hosted by VMware {code}. The speakers at this MeetUp, Dustin Kirkland and Sabari Murugesan, will examine the modern set of container best practices filling the sails of the smartest and most efficient developers in the world. After their presentations, they will stick around after for a bit of Q & A. Please see the details below on the event schedule and speaker bios. Light dinner and drinks will be provided, we hope to see you there!



6:30 – 7:00 Introductions, Snacks, and Brief Presentation on VMware {code}
7:00 – 7:05 – K8s on OpenStack Lightning Talk, Sabari Murugesan
7:05 – 8:00 Discussion and Q&A, Dustin Kirkland
8:00 – 8:30 Networking




Dustin Kirkland

Dustin is a VP of Product Development at Ubuntu/Canonical. Dustin leads a team of expert product managers, directing and managing the product lifecycle and road maps across the suite of Ubuntu server, cloud, desktop, and IoT device products. Dustin drives functional requirements across internal and external teams, delivering marketing and product requirements. Find Dustin on Twitter: @DustinKirkland




Sabari Murugesan

Sabari is a Staff Engineer at VMware and has been working with OpenStack since the Havana release. In the past, he was a core contributor to the Glance project and has also been associated with the Nova and Oslo projects. At VMware, he primarily works as a developer in the VMware Integrated OpenStack & Kubernetes product team, a.k.a “Team OpenStack @ VMware.” Find Sabari on Twitter: @neosab87



Interested? RSVP on MeetUp. If you can’t attend in person, the event will be live-streamed on the VMTN Facebook page.

VMware {code} is a free developer program that provides access to a growing community of developers and experts. If you are an existing Developer Center user or partner program member, you can join the new VMware {code} program using your MyVMware account. If you do not have one, register below to access SDKs and participate in developer forums.

Join VMware {code}

VMware Cloud Certification Services: A Journey to SaaS Transformation

VMware delivers a pre-configured cloud based certification test bed in the cloud for a fixed duration of time to it’s partners to certify their products. Partners with access to the program can log-in using a URL provided by VMware and access the test bed without any VPN.

Continue reading

Introducing the New Workspace ONE Swift SDK

The VMware Workspace ONE product teams have been hard at work this year with the goal to make developing with VMware and Workspace ONE easier and better than ever. First we launched the brand new Workspace ONE Dev Center and then the completely revamped Workspace ONE Swift Software Development Kit (SDK).

You may already be familiar with the AirWatch Software Development Kit (SDK), a set of tools that let you easily add advanced security and management capabilities to enterprise mobile apps. The new Workspace ONE Swift SDK is the completely revamped version of the AirWatch SDK for the iOS platform. The Swift SDK takes the old SDK, written in Objective-C, and is updated with the Swift 3.1 (Swift 3.2 and 4.0 support is right around the corner) programming language from Apple (https://developer.apple.com/swift/) along with many other modern technologies.

By leveraging the latest and greatest Apple technology, the Swift SDK offers all of the benefits of the AirWatch SDK with a few more bells and whistles when it comes to user experience and performance.

You’ll love the Swift SDK, here is why:

  • Greatly reduced app-to-app flipping: The Swift SDK leverages a new protocol for app data sharing, significantly reducing the amount of app-to-app flipping required
  • Reduced integration time:  With the Swift SDK, you no longer need to include as many dependent frameworks
  • Refactored code: Much of the AirWatch SDK code has been refactored, resulting in less operations on the main thread, a smoother feel when interacting with UI elements and more
  • Support for Workspace ONE devices:  The Swift SDK apps will now also be compatible on devices enrolled through Workspace ONE

Architecture for the Future

In addition to the tangible user experience and performance improvements, there are several major underlying architecture changes made in the new Swift SDK which set the groundwork for future improvements. Future improvements will include things such as bitcode support and adoption of modern package management technologies like Cocoa Pods.

So, want to try it out?

The Workspace ONE Swift SDK is available today. Contact your account representative or AirWatch customer support for more information.

Using the Objective-C SDK? Here are some things you should know.

What behavior has changed between Objective-C and. Swift?

The Swift SDK will introduce a new mechanism using the shared keychain for SDK apps to communicate with other SDK apps on the device. This approach provides benefits from both a security and a user experience perspective.

SDK applications built by the same developer account and are also in the same keychain group or “cluster” will now be able to share an app passcode & SSO session with each other without requiring a flip to the Agent or Container application every time authentication is required. However, applications on the same device built by different keychain groups will not be able to take advantage of this passcode sharing capability. There will still be some scenarios where a flip to the Agent, Container, or Workspace ONE app is required for obtaining the server URL and other setup information but this particular flip should only occur once per cluster of apps.

The diagram below illustrates this new “clustering” behavior. The dotted cluster represents a unique developer account and keychain group. Applications with the same color code represents SDK apps which will share information with each other.

How will Swift SDK and Objective-C SDK applications interact and behave when both are present on a device?

Upon upgrading one app to use the Swift SDK (see State 2 in diagram below), the Objective-C SDK applications will automatically switch to the clustering behavior for passcode and other app data sharing mentioned in the behavior changes section above. Thus, the Objective-C applications will no longer flip to the Agent for passcode authentication nor will it share a passcode with apps which are outside of its own keychain cluster.

Note: Anchor app refers to either Agent, Container, or Workspace ONE.

What is the plan for the Objective-C SDK?

The Objective-C version of the iOS SDK will be in maintenance mode and new features/capabilities will be exclusive to the new Swift SDK.

Get in on the conversation!

Join VMware {code}

Become a part of one of the fastest-growing developer communities devoted to cloud infrastructure and enterprise mobility.


Learn More

Check out the VMware EUC blog post on developing enterprise applications with the Workspace ONE SDK here.

VMware {code} Town Hall: 10/24 Event Follow-Up

The AirWatch team recently released a completely refreshed and re-architected SDK for iOS using the new iOS Swift programming language.


As part of the release, we wanted to make sure we’re soliciting feedback from the folks in our development community to make sure we’re taking into account any and all considerations about the adoption of the new SDK along with any questions people may have.

That’s what our second Slack town hall today was all about.

Present in our #workspaceone channel to answer questions were Lucas Chen and Reeves Kissel. Lucas is the product manager for the SDK. And Reeves is one of the members on their iOS engineering team. Lucas and Reeves are both based out of Atlanta, GA.

Please find a cleaned-up transcript of our conversation below. Any additional questions, just post a comment or join the conversation on the #workspaceone channel. The AirWatch team is very responsive!

In case you haven’t joined the VMware {code} program yet, simply register, and you’ll receive your personal Slack invite immediately.

Thanks once again to everyone who was able to join us. We appreciate all the feedback and engagement!

Summary of questions & answers

Q: What are some of the main benefits of the new Swift SDK?
A: There are many great benefits of the Swift SDK. One is the improvement in user experience, i.e., much less flipping to agent or container. Also, the Swift SDK brings with it Workspace One compatibility, reduced integration time, and from our developer perspective the new Swift SDK is much more stable and maintainable allowing us to provide you with a higher quality product!

Q: How long did the rearchitecting project take, beginning to end (roughly)?
A: Great question! The complete re-design and re-write of the SDK in swift took about 9 months to achieve parity with the Obj-c SDK and then another 3 months for the new improvements.

Q: If I’m already using the Objective-C SDK, what do I need to do or know to migrate to Swift?
A: The good news is that migration is extremely easy and very similar to a regular SDK upgrade that you would be doing between two version of the OBJ-C SDK. The APIs remain the same if you are calling from OBJ-C. They are simpler if you are calling these APIs from swift which should make things much cleaner.

We have also made sure to document a step-by-step guide for everyone to be able to following along with while migrating their project from OBJ-C SDK to Swift SDK.

You can learn more at this link. There is also a PDF inside the DMG file the SDK is shipped in.

Another important step to take is to ensure your SDK app(s) have keychain sharing enabled. As Reeves mentioned earlier, one of the key highlights in the Swift SDK is the reduced flipping between apps…the way we’ve accomplished that is through the use of the keychain for app to app communication. That’s why it’s going to be crucial in the new Swift SDK integration that your apps have keychain sharing enabled…if it’s not shared then the app can still function and all but you just lose out on some functionality such as SSO.

Q: What version of Swift is this written in and is there anything I need to do to incorporate into a Swift 4 project?
A: The 17.6 release of the Swift SDK will have both a 3.1 and 3.2 version of the SDK so your Swift 4 project will be compatible with the 3.2 version. Future releases after 17.6 will be swift 4 only. However, we are at the mercy of Apple if Swift 5 comes along in the future.

The current version of the Swift SDK is 17.5, we expect 17.6 to be released within the next 2-3 weeks.

Q: What version of the console do we need to be on in order to support these features? At least 9.0? Does it matter?
A: Great question! It does matter. The Swift SDK requires the console to be on version 9.1.1 or higher.

Q: Are you all supporting the latest version of Swift?
A: Yes, in the 17.6 DMG we will be providing a Swift 3.1 version of the SDK and a Swift 3.2 version of the SDK which is compatible with Swift 4.0. All releases after 17.6 will only include the Swift 4 version of the SDK.

Q: For keychain sharing: this is only useful if we’re shipping multiple SDK-enabled apps, right?
A: That’s correct.

Q: In the objective C version of the SDK, we have to enable ATS settings for using 404.air-watch.com which is a security flag internally for our security scans through HP Fortify. Is that ATS setting something that remains with the Swift version of the SDK?
A: You don’t need to do that anymore, Enabling ATS was supposed to be a workaround for a larger defect (involving a Tunnel Proxy HTTPS reachability check not working correctly) we had a while back but we’ve since then patched the root issue.

Q: What about Xamarin?
A: We also have a Xamarin component for our SDK. We have plans to migrate our Xamarin component to use Swift SDK in the near future as well.

For more, check this link.

Q: In the past, when we’ve upgraded we experienced some issues with jumping versions. Have you all done any testing in regards to jumping versions and if so what were your findings?
A: The migration path from Obj-C to Swift was part of our migration path. Although it depends on how old your Obj-C SDK version is. If you’re utilizing the 5.9.x versions of the Obj-C SDK you should be good.

As long as you follow our guide and go through the migration steps, you will be fine. I think the keychain migration may be the trickiest part, but that really just depends on how things are setup in your apps today.

We have run through many possible scenarios and have documented the steps needed to set up keychain settings and have even documented the 4 most common issues you may run in to and how to resolve those issues.

If you check out our keychain enablements page on the documentation you should see a general overview as well as two other pages 1 for troubleshooting and 1 for basic enablement.

Q: Does the Swift SDK take advantage of the Apteligent integrations?
A: Currently, the Apteligent SDK is still a separate offering and not technically coupled with the Workspace ONE (AirWatch) SDK. Although we have some really neat integration projects on our roadmap that will allow you to get visibility into analytics regarding SDK apps (both written by you as well AirWatch productivity apps) being used by your end users. And of course, you can always integrate an app that includes both the Apteligent SDK in addition to the Workspace ONE SDK. There shouldn’t be any conflicts.

Q: What about SDK profiles? Any changes there? Anything new that has to be enabled?
A: No changes have been made to the SDK profiles, I think the main considerations are around how passcode sharing and SSO work between SDK apps now with the new keychain sharing approach. Not necessarily a direct change to the SDK profile, but worth knowing in case it applies to you.

There’s a nice blurb about it here in this KB article: Preparing for the New iOS Swift SDK

Although take that KB article with a grain of salt since that article was written during the release of 17.5 so some of the information about Swift versions will be out of date very soon once we release 17.6.

Q: What are your plans regarding the Obj-C SDK?
A: We will continue to support the Obj-C SDK until at least the end of 2018. The support will be limited to only bug fixes and defects and we don’t expect to have iOS 12 support with the Obj-C SDK. All new feature development will only be in the new Swift SDK. We’ll publish an official announcement soon with more exact details and dates.

With that being said, we want everyone to be successful in their adoption of the new Swift SDK so please don’t hesitate to reach out if you have any questions.

Q: What’s usually the best way to reach the AirWatch team?
A: Please find us on Slack.


Take the VMware {code} Developer Survey

Developers are a critical part of the success of any organization in tech, and VMware is no different.

Our developer community plays an especially important role. At VMware {code}, we want to ensure we are taking every step possible to support you and improve your experience.

We just launched our first  developer survey in a long time to learn more about your preferences and areas of interest. Please help us by sharing your feedback.

Larry McDonough, Director Product Management, Ecosystem Tools here at VMware and a longtime speaker at developer relations conferences, had this to add:

VMware’s 1st product, released back in May 1999, was Workstation – designed by developers for developers. Our business has grown quite a lot since those days and along the way, we spun out Pivotal Software, a PaaS company aimed at improving on developer productivity and we focused ourselves back on the IaaS layer.  But, as technologies continue to evolve and new innovations come along like containers, cloud native applications, and DevOps, we find ourselves building APIs and tools again for developers.  That’s why we’re reaching out with this survey.  We’d like to hear from you about what you’re building, what you need, and how we can best help you.

Participation should only take about 10 minutes. Those who complete the survey will be entered into a random drawing to win one (1) pair of Bose Wireless Noise Cancelling Headphones. Sweet!

Thanks in advance for your valuable time and input.