DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Docker Model Runner: Running AI Models Locally Made Simple
  • An Introduction to BentoML: A Unified AI Application Framework
  • Keep Your Application Secrets Secret
  • How Do the Docker Client and Docker Servers Work?

Trending

  • Building a Zero-Cost Approval Workflow With AWS Lambda Durable Functions
  • OpenAPI From Code With Spring and Java: A Recipe for Your CI
  • 11 Agentic Testing Tools to Know in 2026
  • From Data Movement to Local Intelligence: The Shift from Centralized to Federated AI
  1. DZone
  2. Software Design and Architecture
  3. Cloud Architecture
  4. Dataweave Playground Sans Docker

Dataweave Playground Sans Docker

New tooling for transforming metadata leverages and improves your Dataweave skills.

By 
Mitch Dresdner user avatar
Mitch Dresdner
·
Oct. 20, 20 · Tutorial
Likes (2)
Comment
Save
Tweet
Share
10.0K Views

Join the DZone community and get the full member experience.

Join For Free

The DataWeave Playground is an integrated development environment that enables you to experiment with complex Mappings and Transformations outside of AnypointStudio. When we first looked at the Playground, a creation of Mariano De Achaval and the Mulesoft Dataweave team, it was an experimental version running inside of a Docker container. While still a work in progress, through the magic of GraalVM, the Playground runs sans Docker, as a binary on Mac, Linux and Windows.

In my earlier article Transformative Moments we started in the middle of the story, showing you how to get immediate value from the DataWeave Command Line interface (DW CLI). We went on to learn how to create Command Line Services which created information pipelines from data source to sink. Now we'll rewind to the beginning of the story to talk about the most important piece of all, the DataWeave Playground.

We'll begin by creating the DW CLI folder and the environment settings which are needed. To make these changes permanent you can add them to your path in the Windows environment dialog settings or to the .bashrc file in your Linux HOME directory. 

Initial Configuration

Shell
xxxxxxxxxx
1
11
 
1
rem Configure DW CLI home in Windows
2
md %USERPROFILE%\.dw
3
set DW_HOME=%USERPROFILE%\.dw
4
set DW_LIB_PATH=%DW_HOME%\libs
5
set PATH=%DW_HOME%\bin;%PATH%
6
---
7
# Configure DW CLI home in Linux
8
mkdir $HOME/.dw
9
export DW_HOME=$HOME/.dw
10
export DW_LIB_PATH=$DW_HOME/libs
11
export PATH=$DW_HOME/bin:$PATH


Download the DW CLI Runtime

In the environment settings above we configured the location for the DW CLI runtime onto your path. Download the runtime from the DW CLI Github repository. The Zip files are located in the Manually paragraph.

After you unzip the download, install the bin and libs folders into the .dw folder you created in the Initial Configurations section above.

Running the DW Playground

After you've completed the download and install, we can take a look at the most prominent part of the DW CLI, the Playground. You can refer to the articles above for more information on the wizardry you can unleash with the DW CLI. Our focus here will be on the Playground.

Shell
x
10
 
1
dw --eval --spell Playground
2

          
3
Fetching `null's` Grimoire.
4
Cloning into 'C:\Users\DresdnerMitchell\.dw\grimoires\data-weave-grimoire'...
5
remote: Enumerating objects: 62, done.
6
remote: Counting objects: 100% (62/62), done.
7
remote: Compressing objects: 100% (51/51), done.
8
remote: Total 62 (delta 16), reused 35 (delta 1), pack-reused 0
9
Unpacking objects: 100% (62/62), 9.79 KiB | 92.00 KiB/s, done.
10
Http Server started at localhost:8082


The first time you invoke the Playground it fetches the code from the Git repository, installs it into your .dw folder and runs the Playground. When the Playground starts you can open it using your browser, it listens on Port 8082.

DW Playground interface


The IDE should be familiar and intuitive,  with your Input sources of information on the left, scripting in the middle and the output on the right.

Clicking on the default input type allows you to change to another type such as XML or CSV. 

You can open the DW API reference from the button bar at the bottom and the Log Viewer as well. 

In the top right you can change the language level to conform with the runtime version you'll be working with.

You can find plenty of examples to try out in the Playground in the DataWeave Cookbook.  This should give you enough to get going and improve your skills with DataWeave. If you enjoy the Playground be sure to give it a Star!

Command-line interface Docker (software)

Opinions expressed by DZone contributors are their own.

Related

  • Docker Model Runner: Running AI Models Locally Made Simple
  • An Introduction to BentoML: A Unified AI Application Framework
  • Keep Your Application Secrets Secret
  • How Do the Docker Client and Docker Servers Work?

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook