...
cmd> cd $RELEASE/phixflow-x.y.z-yyyymmdd/install/schema/$platform/install
where $platform is one of oracle, my_sql or sql_server, then follow the instructions in install_instructions.txt.
...
Platform | Create the database user |
Oracle: | This command will prompt for the name of the user to be created. cmd> sqlplus SYS/SYSPassword@SID as SYSDBA @create@schema/oracle/install/create_user |
Sql Server: | This command required the name of the user to be created, the password, etc. to be provided as parameters cmd> sqlcmd -S localhost\myservice -i schema/sql_server/install/create_database_and_user.sql -v dbName="cview" dbLogin="cview" dbUser="cview" dbPassword="mypass" |
MySQL: | cmd> mysql –-user=myrootuser –-password |
Populate the Database
Once you hcave created the database and/or database user, you can use the Installer to create the database tables and initial data.
Running the Installer
To run the installer:
| Code Block |
|---|
cd $RELEASE/phixflow-x.y.z-yyyymmdd/install
java -jar bin/installer.jar [options] |
To see the available options:
| Code Block |
|---|
java -jar bin/installer.jar -help |
Create the tables
...
and Initial data
Use the Installer to create the database tables and the initial data in a single step. This step is the same regardless of platform, varying for all database platforms, differing only in the URL Url used to reference identify the specific database to be used.
...
Oracle:
| Code Block |
|---|
java -jar |
...
bin/installer.jar |
...
-url="jdbc:oracle:thin:@localhost:1521:cview" -user=myuser -pass=mypass |
...
See the appendices for how to specify URLs for the database platforms supported by PhixFlow.
Create the initial data
Creating the initial data uses the database-specific command-line utilities again:.
Database | Create initial data |
Oracle: | cmd> sqlplus myuser/mypass @populate_schema.sql |
Sql Server: | cmd> sqlcmd -S hostname\myservice -i populate_schema.sql -v dbName="cview" |
MySQL: | cmd> mysql --user=root –-password mysql> exit; |
-install |
SQL Server:
| Code Block |
|---|
java -jar bin/installer.jar -url="jdbc:sqlserver://myhost\myserver;database=cview" -user=myuser -pass=mypass -install |
MySQL:
| Code Block |
|---|
java -jar bin/installer.jar -url="jdbc:mysql://localhost/cview" -user=myuser -pass=mypass -install |
See the appendices for how to specify URLs for the database platforms supported by PhixFlow.
Set the Customer Name in the Database
The customer name in the database must exactly match the customer name used by PhixFlow Support to generate licence files.
...
Database
...
Create initial data
...
Oracle:
...
cmd> sqlplus myuser/mypass
sqlplus> update system_configuration set customer_name=’mycustomer’;
sqlplus> commit;
sqlplus> exit;
...
Sql Server:
...
cmd> sqlcmd -S hostname\myservice –d cview
1> update system_configuration set customer_name=’mycustomer’;
2> go
1> exit
...
MySQL:
cmd> mysql --user=root –-password –database=cview
mysql> update system_configuration set customer_name=’mycustomer’;
mysql> commit;
...
| Code Block |
|---|
java -jar bin/installer.jar -url="jdbc:oracle:thin:@localhost:1521:cview" -user=myuser -pass=mypass -customer="Your Customer Name" |
Install the Webapp in the Tomcat application server
...
See the appendices for more information on setting up a resilient configuration.
Configure phixflow-email.xml
The PhixFlow webapp must be configured to allow PhixFlow to poll an internal/external email server for incoming emails.
In $TOMCAT/webapps/phixflow/WEB-INF/classes, copy phixflow-email.xml.example to phixflow-email.xml and edit the properties for <bean id="emailConfiguration"...., e.g.:
<p:enabled="true">
<p:port="110">
<p:host="pop.your-mail-server.com">
<p:protocol="pop3">
<p:username="your username">
<p:password="your password">
Note that setting the enabled property to true will mean PhixFlow will poll the configured email server for incoming emails. Leave this value set to false if you do not require PhixFlow to process incoming emails.
Configure phixflow-domain.xml
...