Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-19731

Suspected extraneous integration step for JIRA on WebSphere 6.1

    XMLWordPrintable

Details

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      In http://confluence.atlassian.com/display/JIRA/Installing+JIRA+on+IBM+Websphere+6.x:

      When defining the datasource map it to the jdbc/JiraServerDS JNDI key. Please ensure that the JNDI key is set to jdbc/JiraServerDS and not jdbc/JiraDS.

      I suspected to be an extraneous step.

      Can the requirement for this be found and listed next to the statement or the requirement be removed. The value of this task will remove uncertainty from the WAS61 JIRA integration documentation.

      Attachments

        Issue Links

          is related to

          Suggestion - JRASERVER-19728 Update JNDI DS documentation for WebSphere from 5.1 to 6.1

          • Closed

          Suggestion - JRASERVER-19732 Websphere 6.1 classloader preferences documentation for com.atlassian.jira.plugin.JiraOsgiContainerManager

          • Closed
          relates to

          Suggestion - JRASERVER-19729 WebSphere 6.1 JNDI DS Provider - PostgreSQL JDBC provider implementation classname needs to be stipulated

          • Closed

          Activity

            People

              rosie@atlassian.com Rosie Jameson [Atlassian] (Inactive)
              pdzwart PdZ (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: