In Payara Cloud, applications within the same namespace can communicate with each other using internal URLs. The format for these internal URLs is http://deployedAppName/contextRoot/someEndpoint. The deployedAppName refers to the name of the target application, contextRoot is the base path of that application, and someEndpoint specifies the particular endpoint or resource you want to access. For example, if you have two applications, app1 and app2, deployed in the same namespace, and app1 exposes a REST endpoint at /api/data, then app2 can access this endpoint using the URL http://app1/app1/api/data. It’s recommended to use MicroProfile Config properties to externalize endpoint URLs, allowing for flexibility in different environments. This way, you can easily switch between development and production server URLs without modifying your application code.

The Payara Cloud Command-Line Interface (CLI) offers a powerful way to manage your Payara Cloud resources directly from the terminal and automated environments like CI/CD pipelines.

The pcl command provides various functions, including:

The CLI is particularly useful for automating deployment and management tasks, integrating Payara Cloud into your CI/CD pipelines, and performing operations in non-interactive environments.

The Payara Cloud Maven Plugin integrates Payara Cloud deployments into Maven build process. It provides goals for various operations, such as:

Using the Payara Cloud Maven Plugin in your projects, you can automate deployments, streamline your development process, and ensure consistency between your local dev environment and the cloud.