Versions Compared

Old Version 16

changes.mady.by.user Former user

Saved on

compared with

New Version 17

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents
maxLevel3
styleborder:1
locationtop
separatorpipe

Creating the database

...

and user role

Follow the steps given below explains how to create a PostgreSQL database.

...

database and

...

a user role.

  1. Install PostgreSQL on your computer as follows:
  2. Start the PostgreSQL service using the following command:
  3. Create a database and the login role from a GUI using the PGAdminIII tool.
  4. To connect PGAdminIII to a PostgreSQL database server, locate the server from the object browser, right-click the client, and click Connect. This will show you the databases, tablespaces, and login roles as follows:
  5. To create a database, click Databases in the tree (inside the object browser), and click New Database.
  6. In the New Database dialog box, give a name to the database (for example: gregdb) and click OK.

  7. To create a login role, click Login Roles in the tree (inside the object browser), and click New Login Role. Enter the role name and a password.

    Info

    These values will be used in the product configurations as described in the following sections. In the sample configuration, gregadmin will be used as both the role name and the password.

  8. Optionally enter other policies, such as the expiration time for the login and the connection limit.

  9. Click OK to finish creating the login role. 

...

  1. Edit the default datasource configuration for storing user management and registry data as shown below. The database configurations in registry.xml and user-mgt.xml files refer to this datasource. 

    Code Block
    languagexml
    <datasource>
      <name>WSO2_CARBON_DB</name>
      <description>The datasource used for registry and user manager</description>
      <jndiConfig>
            <name>jdbc/WSO2CarbonDB</name>
      </jndiConfig>
      <definition type="RDBMS">
            <configuration>
                <url>jdbc:postgresql://localhost:5432/gregdb</url>
                <username>regadmin</username>
                <password>regadmin</password>
                <driverClassName>org.postgresql.Driver</driverClassName>
                <maxActive>80</maxActive>
                <maxWait>60000</maxWait>
                <minIdle>5</minIdle>
                <testOnBorrow>true</testOnBorrow>
                <validationQuery>SELECT 1</validationQuery>
                <validationInterval>30000</validationInterval>
           </configuration>
       </definition>
</datasource>

    Following are the database configuration options:

    url - The URL of the database.
    username - The name of the database user.
    password - The password of the database user.
    driverClassName - The class name of the database driver.
    maxActive - The maximum number of active connections that can be allocated from this pool at the same time, or enter a negative value for no limit.
    maxWait - The maximum number of milliseconds that the pool will wait (when there are no available connections) for a connection to be returned before throwing an exception. You can enter zero or a negative value to wait indefinitely.
    minIdle - The minimum number of active connections that can remain idle in the pool without extra ones being created, or enter zero to create none.
    testOnBorrow -  The indication of whether objects will be validated before being borrowed from the pool. If the object fails to validate, it will be dropped from the pool, and another attempt will be made to borrow another. 
    validationQuery - The SQL query that will be used to validate connections from this pool before returning them to the caller.
    validationInterval -  The indication to avoid excess validation, and only run validation at the most, at this frequency (time in milliseconds). If a connection is due for validation, but has been validated previously within this interval, it will not be validated again.

    Info

    For more information on other parameters that can be defined in the master-datasources.xml file, see Tomcat JDBC Connection Pool.

  2. Edit the default datasource configuration for storing RSS meta data as shown below. The RSS meta data specific configurations in the rss-config.xml file refers to this datasource. 

    Code Block
    languagehtml/xml
    <datasource>
	<name>MetadataRepo</name>
	<jndiConfig>
		<name>MetadataRepoDS</name>
	</jndiConfig>
	<definition type="RDBMS">
		<configuration>
			<dataSourceClassName>org.postgresql.xa.PGXADataSource</dataSourceClassName>
			<dataSourceProps>                         	 	 	 	
				<property name="serverName">localhost</property>
				<property name="portNumber">5432</property>
				<property name="databaseName">rss_db</property>                     	 	 	 	
				<property name="user">RootUser</property>
				<property name="password">RootPassword</property>
			</dataSourceProps>
		</configuration>
	</definition>
</datasource>

Setting up RSS meta data configurations

If you have changed the default database for storing RSS meta data as explained above, the following RSS meta data specific configurations should be updated. See Changing the Default RSS configuration for more details.

...