<br><b>Code</b>: rsb:print<br><b>Error</b>: Formatter [ rootadoname | tolower() ] failed in the evaluation of <p> The [company_name] JDBC Driver for [service] enables you to follow standard procedures to integrate [datasource] into Java Web applications. This article shows how to deploy the [company_name] JDBC Driver for [service] in WebLogic server. </p> <h2>Install the JDBC Driver in WebLogic Server</h2> <p> Add the driver JAR and license file to the classpath your application will be using. The .lic file must be located in the same folder as the JAR. These files are located in the lib subfolder of the installation directory. </p> <p>If you want to add the driver to all domains, add the JAR to the WEBLOGIC_CLASSPATH environment variable. add the following line to the commEnv.cmd/sh script in WL_HOME\common\bin\. </p> <code> set WEBLOGIC_CLASSPATH=your-installation-directory\lib\\[company_name|tolower].jdbc.[rootadoname|tolower].jar;%WEBLOGIC_CLASSPATH% </code> <p> If you want to add the driver to a specific domain, you will need to add the JAR to the PRE_CLASSPATH environment variable. Add the following line to the setDomainEnv.cmd/sh script in the bin subfolder of the folder for that domain: </p> <code> set PRE_CLASSPATH=your-installation-directory\lib\\[company_name|tolower].jdbc.[rootadoname|tolower].jar;%PRE_CLASSPATH% </code> <h2>Create a JDBC Data Source for [service]</h2> <p> After installing the driver, create the connection. </p> <ol> <li> In the Domain Structure tree, click Services -> Data Sources -> New -> Generic Data Source. </li> <li> On the JDBC Data Source Properties page, enter the following information: <ul> <li><b>Name</b>: Enter a user-friendly name; for example, [rootadoname|tolower]jdbc. <li><b>JDBC Name</b>: Enter the path the JDBC data source will be bound to; for example, jdbc/[rootadoname]. <li><b>Database Type</b>: Select Other.</p> </ul> <img src="[x|UrlRootAbs]/kb/articles/jdbc-weblogic-1.png" title="A user-friendly name and the path to bind to. (Salesforce is shown.)"/> </li> <li> <p>Click Next to use the default options. On the last page, enter the following information and click Test Configuration:</p> <ul> <li><b>Driver Class Name</b>: Enter the driver class, [company_name|tolower].jdbc.[rootadoname|tolower].[rootadoname]Driver, in this property. <li><p><b>URL</b>: Enter the JDBC URL. A typical JDBC URL is below:</p><code>jdbc:[rootadoname|tolower]:[extraconnectionprops]</code> [extraconnectionnotes|def('')] </li> <li><b>Database User Name</b>: Enter the username, if not specified in the JDBC URL. <li><b>Password</b>: Enter the password, if not specified in the JDBC URL. </ul> <img src="[x|UrlRootAbs]/kb/articles/jdbc-weblogic-3.png" title="Driver connection properties. (Salesforce is shown.)"/> </li> </ol> <p>After selecting the server where you want to deploy the JDBC data source, you can now connect to [datasource].</p> <img src="[x|UrlRootAbs]/kb/articles/jdbc-weblogic-4.png" title="The data source deployed on the target server and enabled for connection pooling. (Salesforce is shown.)"/> <h2>More WebLogic Integration</h2> <p> The steps above show how configure the driver in a simple connection pooling scenario. For more use cases and information, see the JDBC sections in the <a href="http://docs.oracle.com/middleware/1213/wls/INTRO/jdbc.htm#FIFFIFEB">WebLogic Data Sources</a> chapter of the Oracle Fusion Middleware documentation.</p>. The error was: The attribute does not exist. This formatter cannot be called with nonexistent attributes.<br><b>URL</b>: /jp/kb/tech/sqlite-jdbc-weblogic.rst