On the Partner Links page, notice that the Partner Service Provider's Invoke Handler for data access is automatically set to System Service.
If you are using a cloud process, in the edit field, replace the text, FILL_IN_DATASOURCE_JNDI, with one of the following:
The JNDI Name defined in your application server that is bound to the data source. There is no need to include the JNDI prefix. For example:
jdbc/myDatabase
Similarly, for WebLogic and Websphere, no prefix is required:
jdbc:/myDatabase
A URN that can be mapped to a JNDI Name or URL in the Process Console URN Mappings page. This option gives you a way to change the database connection information without refactoring and redeploying your process.

 java:comp/env/jdbc/myDatabase

In Process Developer, stop the embedded server, if it is running. For details, see Setting Up the Embedded Process Server.
In the file system, in your Process Developer installation directory, navigate to the embedded server plugin. For example,
[
designer install directory
]\designer\plugins\org.activebpel.enginep_[
versionNNN
]
where versionNNN is the plugin version.
In the
org.activebpel.enginep
plug-in, navigate to
server\conf\Catalina\localhost
and make a backup copy of the
active-bpel.xml
file. Then open the file.
In the
active-bpel.xml
file, add a new
<Resource>
element within the
<Context>
element, as shown in the example:]
<Resource 
    driverClassName="driver_class_name" 
    maxActive="100"
    maxIdle="30" 
    maxWait="10000" 
    name="jdbc/anyName"
    password="password" 
    type="javax.sql.DataSource"
    url="url_of_your_db" 
    username="db_login_name"/>
Be sure to replace all attribute values with values for connecting to your database.
Save the file and restart the embedded server.
Be sure to add the JNDI name to the PDD of your process before deploying your BPR to the embedded server.