THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Expert Recommendation: There are many databases that OFBiz can use, both commercial and open source. We While there are significant production instances of OFBiz running against Oracle, MS SQLServer, and so on, we generally recommend using an open source database such as Postgres , MaxDB by MySQL, or some of more recent version of the MySQL database. The database to use is an important decision and may affect many things down the road. If you do not have a preferred database to use, we recommend discussing options with an experienced consultant before making a final decision.
...
Modify an existing datasource (near the bottom of the file) or create a new one by copying one of the sample datasources already there and giving it a new unique name ß
- If using the default OFBiz transaction manager and connection pool, update the data URI, username and password in the inline-jdbc tag
...
- If you want your OFBiz tables in a special schema first create that schema in your database, then set the schema-name attribute on the datasource tag
...
- Find the "default" delegator near the top of the file and change the datasource-name attribute value in the group-map tag under it to the name of the data source you modified or created.
Expert Recommendation: if you are using an external app server or want to setup more advanced Entity Engine configurations, see the Entity Engine Configuration Guide or other online documentation. The training videos from Undersun Consulting are highly recommend if you get into more advanced usage of OFBiz.
...
${ofbiz install dir}/base/config/ofbiz-containers.xml (The Containers Configuration File)ß
- Sometimes other container configuration files are used, but are generally in that same directory and will be specified in the start properties file used (see start.properties, pos.properties, install.properties, etc)
...
- The integration with Shark in OFBiz is still not complete, so we recommend disabling Shark. So, the Shark container configuration near the beginning of the file should be commented out.
...
- The BSH client (the last container in the file) should generally be disabled or at least protected by a firewall for production deployments. Otherwise this is a significant security risk.
...
- Note that if an external application server is used instead of the embedded Tomcat or Jetty servers then many things normally configured here will be configured in the setup files for the external application server.
${ofbiz install dir}/framework/webapp/config/url.properties (The URL Properties File)ß
- These properties are used to configure the settings to send to the client browser. The port and host settings may be different than the port and host settings of the local machine if it is running through Apache through AJP, through any proxy, or through a load balancer of any sort. The settings in this file should be set to what the client browser will see when communicating with your system.
...
- Note that the settings in this file can be overridden on the WebSite record with the ID specified by the webSiteId field in the web.xml file in each webapp, if applicable. These can be viewed and modified in the WebSites tab of the Content Manager application.
${ofbiz install dir}/base/config/jndiservers.xml (JNDI Servers XML File)
...
The CSR will be saved in the current directory: ----BEGIN NEW CERTIFICATE REQUEST--- and - ----END NEW CERTIFICATE REQUEST----
...
6. Configure the ofbiz-containers.xml file to point to your new keystore and password:
ß If using Tomcat (Catalina), which is the default, find the "catalina-container" - -> "https-connector" - -> "keystore" and "password" properties and set them.
ß If using Jetty find the "jetty-container" --> "https-listener" - -> "keystore" and "password" properties and set them.
ß For other Servlet containers, see the documentation for that container to find out how to set the HTTPS keystore and password settings.
...