Creating the XADataSource for Oracle or DB2

Creating the XADataSource involves specifying connection information for your database and setting some custom options. The instructions in this section apply to both Oracle and DB2 databases, except where noted.

  1. If you are running the SIMULIA Execution Engine on Windows, verify that you have updated the Windows Firewall on the computer running the application server and the SIMULIA Execution Engine software.

    For more information, see Configuring the Windows Firewall.

  2. In the Name column on the right side of the console, click one of the following:

    • Oracle JDBC Driver (XA)

    • DB2 Universal JDBC Driver Provider (XA)

  3. In the Additional Properties area on the right side of the console, click Data sources.

    The Data sources screen appears.

  4. Click New.

  5. In the Data source name text box, type the following entry:

    Fiper XA Data Source

  6. In the JNDI name text box, type the following entry:

    fiper/jdbc/XADataSource

  7. Click Next.

  8. For an Oracle database, do the following:

    1. Enter the following information for the URL setting (in the Value text box):

      jdbc:oracle:thin:@hostname:port:databasename

      where:

      hostname is the computer name where Oracle is running,

      port is the appropriate port number on which the Oracle database is listening, and

      databasename is the name of the SIMULIA Execution Engine database.

      For example, if the hostname is dbcomputer, the port number is 1521, and the database name is SEE, the entry would appear as follows:

      jdbc:oracle:thin:@dbcomputer:1521:SEE

    2. From the Data store helper class name list, select the data store helper that matches the version of Oracle you are using.

  9. For a DB2 database, do the following:

    1. From the Driver type list, verify that 4 is selected.
    2. In the Database name text box, type the appropriate database name (SEE).
    3. In the Server name text box, type the name of the server that is running DB2.
    4. If necessary, in the Port number text box, alter the port number on which DB2 is listening. If you do not know this port number, contact your local DB2 administrator.

  10. Verify that Use this data source in container managed persistence (CMP) is selected.

  11. Click Next.

  12. From the Authentication alias for XA recovery list, select the J2C authentication alias you created for your database.

  13. From the Component-managed authentication alias list, select the J2C authentication alias you created for your database.

  14. From the Mapping-configuration alias list, select DefaultPrincipalMapping.

  15. From the Container-managed authentication alias list, select the J2C authentication alias you created for your database.

  16. Click Next.

  17. Review the summary.

  18. Click Finish.

  19. On the right side of the console, click Fiper XA Data Source.

  20. In the Additional Properties area on the right side of the console, click Connection pool properties.

  21. Type the following information in the corresponding text boxes and click OK:

    Connection timeout: 300

    Maximum connections: 100

    Minimum connections: 50

  22. In the Additional Properties area on the right side of the console, click Custom properties.

  23. Click New.

  24. Type the following information in the corresponding text boxes:

    Name: useRRASetEquals

    Value: true

    Description: See IBM APAR PK75897

  25. Click OK.

  26. On the left side of the console, click Data sources.

    The Data sources screen appears.

  27. Near the top of the right side of the console, click Save to save the configuration.

  28. In the Select column, click the check box that corresponds to the new data source.

  29. Click Test connection.

    A message appears, telling you that the test connection was successful.



    Note: If your test connection fails, verify that all the information is entered correctly. Confirm that you have disabled the Windows Firewall on the computer running WebSphere. If the Windows Firewall is active, you will not be able to connect to the system running the Oracle database if the database is running on a separate system. For more information, see Configuring the Windows Firewall.

  30. Verify that the connection was successful.