Fail to setup Jazz server launched on Development env
I setup a Jazz dev env following the instruction -->https://jazz.net/wiki/bin/view/Main/ComponentDevelopmentSetup using the latest souce code and binaries on download page.
And I put trail license file into the \client\eclipse\source\server\eclipse\plugins.
I launch the server through "Run ->Open Run Dialog->OSGI Platfrom" with JazzServer-06-RTC10-Maximal.launch.
firstly I got error "log4j:WARN No appenders could be found for logger (com.ibm.team.repository.jndi.internal.Activator).
log4j:WARN Please initialize the log4j system properly."
Then:
1.Go to https://localhost:9443/jazz/setup
2.Click "fast path setup"
3. select "Tomcat user database" and input user info.
I got the error"An error occurred while saving the configuration properties. Please check your server log for more details."
Since log4j has problem, I cannot get any server log output.
And I put trail license file into the \client\eclipse\source\server\eclipse\plugins.
I launch the server through "Run ->Open Run Dialog->OSGI Platfrom" with JazzServer-06-RTC10-Maximal.launch.
firstly I got error "log4j:WARN No appenders could be found for logger (com.ibm.team.repository.jndi.internal.Activator).
log4j:WARN Please initialize the log4j system properly."
Then:
1.Go to https://localhost:9443/jazz/setup
2.Click "fast path setup"
3. select "Tomcat user database" and input user info.
I got the error"An error occurred while saving the configuration properties. Please check your server log for more details."
Since log4j has problem, I cannot get any server log output.
One answer
The Server Setup Wizard (/jazz/setup) is not necessary for a server
running in the development environment. Since you are running a
development launch, which uses the Jetty server (not Tomcat), it's best
to leave the "User Registry Type" setting as "DETECT" by *not*
completing the "Setup User Registry" wizard page. So skip the Setup
Wizard in a dev environment.
In a dev environment you should use ADMIN/ADMIN as the JazzAdmins user,
so you don't need to create an initial JazzAdmins user like you would
for a real server. If you need additional users, you can create members
of the JazzUsers group using the Admin > User Management page.
By default, configuration changes that you make in a dev server will not
be persisted once you restart the launch. So restarting your server
will set you back to the "DETECT" setting, and your server should be fine.
Kristen Balhoff
Jazz Server Team
wangffan wrote:
running in the development environment. Since you are running a
development launch, which uses the Jetty server (not Tomcat), it's best
to leave the "User Registry Type" setting as "DETECT" by *not*
completing the "Setup User Registry" wizard page. So skip the Setup
Wizard in a dev environment.
In a dev environment you should use ADMIN/ADMIN as the JazzAdmins user,
so you don't need to create an initial JazzAdmins user like you would
for a real server. If you need additional users, you can create members
of the JazzUsers group using the Admin > User Management page.
By default, configuration changes that you make in a dev server will not
be persisted once you restart the launch. So restarting your server
will set you back to the "DETECT" setting, and your server should be fine.
Kristen Balhoff
Jazz Server Team
wangffan wrote:
I setup a Jazz dev env following the instruction
-->https://jazz.net/wiki/bin/view/Main/ComponentDevelopmentSetup
using the latest souce code and binaries on download page.
And I put trail license file into the \client\eclipse\source\server\eclipse\plugins.
I launch the server through "Run ->Open Run Dialog->OSGI
Platfrom" with JazzServer-06-RTC10-Maximal.launch.
firstly I got error "log4j:WARN No appenders could be found for
logger (com.ibm.team.repository.jndi.internal.Activator).
log4j:WARN Please initialize the log4j system properly."
Then:
1.Go to https://localhost:9443/jazz/setup
2.Click "fast path setup"
3. select "Tomcat user database" and input user info.
I got the error"An error occurred while saving the configuration
properties. Please check your server log for more details."
Since log4j has problem, I cannot get any server log output.