From e84cfc6e97d93f0c8ef9f16d8df25aa33b6c19dd Mon Sep 17 00:00:00 2001 From: Kevin Wooten Date: Sun, 3 Feb 2019 17:44:39 -0700 Subject: [PATCH] Destroyed WildFly Alternative Deployment Method (markdown) --- WildFly-Alternative-Deployment-Method.md | 43 ------------------------ 1 file changed, 43 deletions(-) delete mode 100644 WildFly-Alternative-Deployment-Method.md diff --git a/WildFly-Alternative-Deployment-Method.md b/WildFly-Alternative-Deployment-Method.md deleted file mode 100644 index d142ee8..0000000 --- a/WildFly-Alternative-Deployment-Method.md +++ /dev/null @@ -1,43 +0,0 @@ -To use the pgjdbc-ng driver as the source of connection pools in wildfly the following steps needs to be taken: - -1. JDBC Driver Installation - -2. Configure A Datasource - -3. Test Datasource - -## JDBC Driver Installation. - -According to the documentation found at the [WildFly Subsystem Configuration](https://docs.jboss.org/author/display/WFLY8/Subsystem+configuration) site the recommended way to install a JDBC driver into WildFly it to deploy it as a regular JAR file. Use one of the following methods to deploy the jar file to WildFly. - -### Drop jar into deployment folder: -In your WildFly installation directory there will be a deployments folder/directory. Depending on if you run this as part of a domain or standalone the exact location might vary. Open the deployments folder and move/copy the pgjdbc-ng-X.X-complete.jar to the deployments folder. If WildFly is running you will see a marker file called pgjdbc-ng-X.X-complete.jar.deloyed being created. This means that the driver is now deployed onto WildFly. - - -### Use the WildFly admin console to deploy: -Log into the admin console. Click on the RunTime tab and then click on Manage Deployments. CLick on the add button and a file dialog will appear which you can use to browse to the pgjdbc-ng-X.X-complete.jar file and upload. Make sure you Enable the driver after upload. - -## Configure Datasource By Using Console: -Log into the admin console and click on the Profile Tab. Expand the Connector node in the treeview and select Datasources from the child node. - -The console will now list all available datasources in the console. Click the add button and follow these three steps: - -### Step 1/3: Datasource Attributes: -Give your datasource and name such as pgTest. This name can be anything try keep it short and descriptive. The second piece of information is the JNDI Name. WildFly requires this to start with ```java:jboss``` so give it a name such as ```java:jboss/datasources/PGSQLDS```. Note that after the initial required bit(```java:jboss```) you can pretty much name it anything but stick to something that clearly marks it as a datasource. After you have filled in the text boxes click Next. - -### Step 2/3: JDBC Driver: -The next dialog will ask you to select a deployed JDBC driver. If the pgjdbc-ng-X.X-complete.jar deployed correctly in the previous steps you will see it on the list of detected drivers. Select pgjdbc-ng-X.X-complete.jar from the list and click Next. - -### Step 3/3: Connection Settings: -The next dialog box requires at least three pieces of information they are the connection url, user name and password. The connection url should follow this form: ```dbc:pgsql://:/``` as a minimum. Make sure you add the user name and password and click done. - -The datasource will now be listed in the admin console but it will be disabled. Select the datasource in the list by click on it and then enable it by clicking the enable button. - -## Test Datasource: - -Click on the runtime tab in the admin console and then select the Datasources child node of the Subsystem node in the treeview. Select your datasource by click it in the grid and click the test connection button. - -Done. - -## When things go wrong: -Best advice is to view the logs in the logs folder under the WildFly installation folder. All exceptions will be logged here and this is a must for debugging. \ No newline at end of file