Details

    • Type: Bug Bug
    • Status: Closed
    • Resolution: Fixed
    • Affects Version/s: 5.2.0
    • Fix Version/s: 5.2.0
    • Component/s: None
    • Labels:
      None
    • Similar Issues:
      Show 5 results 

      Description

      Following LPS-1109, move settings for jdbc pool into portal.properties for more flexibility and easier maintenance across application servers.

      See

        Activity

        Hide
        Brian Chan added a comment - - Restricted to

        ##

          1. JDBC
            ##

        #

        1. Set the JDBC properties to configure how Liferay connects to the database
        2. server. Liferay is database agnostic and can connect to a number of
        3. different database servers.
          #
        4. The default settings are configured for an in-memory database called
        5. Hypersonic that is not recommended for production use. Please change the
        6. properties to use another database.
          #
        7. Liferay can also be configured to use one database cluster for read calls
        8. and another database cluster for write calls. The convention is to create
        9. a set of properties prefixed with "jdbc.read." to handle read calls and
        10. another set of proeprties prefixed with "jdbc.write." to handle write
        11. calls. See dynamic-data-source-spring.xml for more information.
          #

        #

        1. DB2
          #
          #jdbc.default.driver=com.ibm.db2.jcc.DB2Driver
          #jdbc.default.url=jdbc:db2:lportal
          #jdbc.default.username=db2admin
          #jdbc.default.password=lportal

        #

        1. Derby
          #
          #jdbc.default.driver=org.apache.derby.jdbc.EmbeddedDriver
          #jdbc.default.url=jdbc:derby:lportal
          #jdbc.default.username=
          #jdbc.default.password=

        #

        1. Hypersonic
          #
          jdbc.default.driver=org.hsqldb.jdbcDriver
          jdbc.default.url=jdbc:hsqldb:lportal
          jdbc.default.username=sa
          jdbc.default.password=

        #

        1. MySQL
          #
          #jdbc.default.driver=com.mysql.jdbc.Driver
          #jdbc.default.url=jdbc:mysql://localhost/lportal?useUnicode=true&characterEncoding=UTF-8&useFastDateParsing=false
          #jdbc.default.username=
          #jdbc.default.password=

        #

        1. Oracle
          #
          #jdbc.default.driver=oracle.jdbc.driver.OracleDriver
          #jdbc.default.url=jdbc:oracle:thin:@localhost:1521:xe
          #jdbc.default.username=lportal
          #jdbc.default.password=lportal

        #

        1. P6Spy
          #
          #jdbc.default.driver=com.p6spy.engine.spy.P6SpyDriver
          #jdbc.default.url=jdbc:mysql://localhost/lportal?useUnicode=true&characterEncoding=UTF-8&useFastDateParsing=false
          #jdbc.default.username=
          #jdbc.default.password=

        #

        1. PostgreSQL
          #
          #jdbc.default.driver=org.postgresql.Driver
          #jdbc.default.url=jdbc:postgresql://localhost:5432/lportal
          #jdbc.default.username=sa
          #jdbc.default.password=

        #

        1. SQL Server
          #
          #jdbc.default.driver=net.sourceforge.jtds.jdbc.Driver
          #jdbc.default.url=jdbc:jtds:sqlserver://localhost/lportal
          #jdbc.default.username=sa
          #jdbc.default.password=

        #

        1. Sybase
          #
          #jdbc.default.driver=net.sourceforge.jtds.jdbc.Driver
          #jdbc.default.url=jdbc:jtds:sybase://localhost:5000/lportal
          #jdbc.default.username=sa
          #jdbc.default.password=
        Show
        Brian Chan added a comment - - Restricted to ## JDBC ## # Set the JDBC properties to configure how Liferay connects to the database server. Liferay is database agnostic and can connect to a number of different database servers. # The default settings are configured for an in-memory database called Hypersonic that is not recommended for production use. Please change the properties to use another database. # Liferay can also be configured to use one database cluster for read calls and another database cluster for write calls. The convention is to create a set of properties prefixed with "jdbc.read." to handle read calls and another set of proeprties prefixed with "jdbc.write." to handle write calls. See dynamic-data-source-spring.xml for more information. # # DB2 # #jdbc.default.driver=com.ibm.db2.jcc.DB2Driver #jdbc.default.url=jdbc:db2:lportal #jdbc.default.username=db2admin #jdbc.default.password=lportal # Derby # #jdbc.default.driver=org.apache.derby.jdbc.EmbeddedDriver #jdbc.default.url=jdbc:derby:lportal #jdbc.default.username= #jdbc.default.password= # Hypersonic # jdbc.default.driver=org.hsqldb.jdbcDriver jdbc.default.url=jdbc:hsqldb:lportal jdbc.default.username=sa jdbc.default.password= # MySQL # #jdbc.default.driver=com.mysql.jdbc.Driver #jdbc.default.url=jdbc:mysql://localhost/lportal?useUnicode=true&characterEncoding=UTF-8&useFastDateParsing=false #jdbc.default.username= #jdbc.default.password= # Oracle # #jdbc.default.driver=oracle.jdbc.driver.OracleDriver #jdbc.default.url=jdbc:oracle:thin:@localhost:1521:xe #jdbc.default.username=lportal #jdbc.default.password=lportal # P6Spy # #jdbc.default.driver=com.p6spy.engine.spy.P6SpyDriver #jdbc.default.url=jdbc:mysql://localhost/lportal?useUnicode=true&characterEncoding=UTF-8&useFastDateParsing=false #jdbc.default.username= #jdbc.default.password= # PostgreSQL # #jdbc.default.driver=org.postgresql.Driver #jdbc.default.url=jdbc:postgresql://localhost:5432/lportal #jdbc.default.username=sa #jdbc.default.password= # SQL Server # #jdbc.default.driver=net.sourceforge.jtds.jdbc.Driver #jdbc.default.url=jdbc:jtds:sqlserver://localhost/lportal #jdbc.default.username=sa #jdbc.default.password= # Sybase # #jdbc.default.driver=net.sourceforge.jtds.jdbc.Driver #jdbc.default.url=jdbc:jtds:sybase://localhost:5000/lportal #jdbc.default.username=sa #jdbc.default.password=

          People

          • Assignee:
            SE Support
            Reporter:
            Anonymous
            Recent user:
            Randy Zhu
            Participants of an Issue:
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Days since last comment:
              6 years, 24 weeks ago

              Development

                Structure Helper Panel