Task flow: Basic scenario with IBM Cloud Private
The steps in this basic scenario can help you get started running stubs in IBM Cloud Private.
This is the basic task flow that helps you to run stubs in IBM Cloud Private. After you setup to use IBM Cloud Private, you can perform the tasks in sequence to run one or more stubs in IBM Cloud Private.
| Task | More information |
|---|---|
| 1. Prepare IBM Cloud Private. | Preparing to use IBM Cloud Private |
| 2. Publish one or more stubs to IBM Cloud Private resource files by using the user interface, command line, or Ant task. To publish to IBM Cloud Private resource files, only stubs that are based on specific transports are supported. For more information, see Supported transports to publish stubs to IBM Cloud Private resource files. | See IBM Cloud Private resource files (Kubernetes) in Publishing stubs, Publish stubs by using the command line, or Publish stubs by using an Ant task. |
| 3. Verify that the stub is published by checking the output directory from the publish step. | See IBM Cloud Private resource files (Kubernetes) in Verifying publication of stubs. |
| 4. Run stubs by creating a resource. After you publish one or more stubs to IBM Cloud Private resource files, you upload and extract those files to IBM Cloud Private and then create a resource, which is deployed to run the stubs in IBM Cloud Private. | Publishing stubs to IBM Cloud Private resource files: Running stubs in IBM Cloud Private |
| 5. Verify the stub information by querying the IBM Cloud Private deployments. After you create IBM Cloud Private resource files, you can query the deployment to see stub port information. | Query stub port information in IBM Cloud Private deployments |
| 6. Query IBM Cloud Private logs by using the IBM Cloud Private management console. | Query IBM Cloud Private deployment logs |
| 7. Stop a stub by removing the IBM Cloud Private Deployment and the NodePort service. | Stopping stubs that are running in IBM Cloud Private |