Creating a service instance for DataStage

When you install DataStage, a service instance is created automatically. You can optionally create more service instances in the operands project. You can choose the method or methods that you want to use to create service instances.

Who needs to complete this task?

The permissions that you need depend the method that you want to use:

Method	Required permissions
cpd-cli manage apply-cr command	You must be an instance administrator on the Red Hat® OpenShift® Container Platform cluster.
cpd-cli service-instance create command	You must have the Create service instances (can_provision) permission in Cloud Pak for Data.
Web client	You must have the Create service instances (can_provision) permission in Cloud Pak for Data.

When do you need to complete this task?

You can complete one of the following tasks if you want to create additional service instances.

About this task

A parallel engine (PX) DataStage instance is the runtime environment that DataStage jobs run on. When DataStage is installed, one default PX instance is automatically created. The size of the default instance is the size that was specified when DataStage was installed, and can be small, medium, or large.

The default instance is provisioned under the administrator account, so only users with administration permissions can view or edit the default instance. The default instance is named ds-px-default. Every DataStage user has access to the default instance. Jobs that have no environment that is associated with them automatically run on the default instance.

Users in roles with the correct permissions can create more instances. Administrators can create new roles with permissions as needed. Each PX instance has its own conductor and compute pods to ensure the DataStage workloads are separate. Different users and user groups can be assigned to each PX instance. A user can be granted access to an instance as an admin or an operator. An operator can use the instance to run DataStage jobs, while an admin can also grant access and delete the instance.

Every instance can access ds-storage, which is used for storing project metadata and resource files. Do not use this mounted PV to persist user data that needs to be accessible only from a particular px-runtime instance. To keep data assets from being accessible to all instances, refer to them with the absolute path whenever they are being used as a source. If the relative path is used, the data asset is generated under ds-storage.