...
- Choose Product Installation
- Makes sure PostgreSQL is selected (it should be by default) click External Database.
- Direct JDBC
- Fill out the form,
- Database URL: Change the default line, jdbc:postgresql://localhost:5432/confluence to jdbc:postgresql://localhost:5432/confluencedb
- User: confluencedbuser
- Pass: the pasword you used earlier to create the user
- The intial user will be called "Server Admin" with user name serveradmin
Stopping the Service
There appears to be a problem with shutting down the Confluence server. According to Atlassian, this only happens on certain configuration and they are not able to determine yet why. I have personally experienced with every type of Virtualized Ubuntu system I have setup over the past few years.
Start by trying to perform a normal shutdown,
| Code Block |
|---|
|
su - svradm
/opt/confluence/bin/shutdown.sh |
Next ensure that Confluence actually shut down,
| Code Block |
|---|
|
ps -ef | grep java | grep confluence |
The resulting output shows all your java processes. Look for you Confluence java process which looks something similar to below,
| Code Block |
|---|
|
svradm 2364 1 0 01:00 ? 00:02:37 /opt |
If it does not exist then the shutdown occurred properly. However, if it still exists try running ps again in a few minutes. If it still exists after that you need to kill the process,
| Code Block |
|---|
|
kill 2364 # Note change 2364, to the process ID that you see on your screen. |
Administrator Tasks
| Warning |
|---|
This section still needs to be written to take the user through setting up the base url, creating their first space, disabling automatic backup, how to do real backups and any other important activities. |
...
Once port 9009 is enabled, mod_jk can be enabled by following the Apache Tomcat Connector instructions.
Stopping the Service
There appears to be a problem with shutting down the Confluence server. According to Atlassian, this only happens on certain configuration and they are not able to determine yet why. I have personally experienced with every type of Virtualized Ubuntu system I have setup over the past few years.
Start by trying to perform a normal shutdown,
| Code Block |
|---|
|
su - svradm
/opt/confluence/bin/shutdown.sh |
Next ensure that Confluence actually shut down,
| Code Block |
|---|
|
ps -ef | grep java | grep confluence |
The resulting output shows all your java processes. Look for you Confluence java process which looks something similar to below,
| Code Block |
|---|
|
svradm 2364 1 0 01:00 ? 00:02:37 /opt |
If it does not exist then the shutdown occurred properly. However, if it still exists try running ps again in a few minutes. If it still exists after that you need to kill the process,
| Code Block |
|---|
|
kill 2364 # Note change 2364, to the process ID that you see on your screen. |
Future Upgrade Notes
As part of planning for future upgrades listed here are the key files to keep in mind,
...