Manual to going live - production site

View and download documents on various topics e.g. Configuring Ebase Xi under different environmental setups

Moderators: Jon, Steve, Ian, Dave

cagabit
Ebase User
Posts: 11
Joined: Fri Nov 20, 2015 6:10 pm

Manual to going live - production site

#1

Postby cagabit » Tue Nov 24, 2015 2:53 pm

Hi to all,

I am new to ebase, have some experience on IT subjects but not especially on web development / web servers.
I am experimenting on v5.

I dont understand the process of opening a site live, as a production environment. Tried to search the forum, there are some info but not as good as like a road-map, some steps assumed to be known !
Also read the manual but some points stay in the shadows.

For example I tried a lot, to use the deployment future but could not define a valid server ! So had to test it with export/import.
Also couldnt manage to use firendly URLs from the user site !

For the experienced ones; is it possible for you to wrote a manual for this subject ?

chapters can be :

- deployment
- valid test / production server setup ( after the ebase setup )
- Other software or tools helping us ( IIS redirect etc )
- how to use firendly URLs ( if possible )
- Security measures for a real enviroment
0 x

Jon
Moderator
Moderator
Posts: 1342
Joined: Wed Sep 12, 2007 12:49 pm

#2

Postby Jon » Tue Nov 24, 2015 4:41 pm

Sorry you found this confusing. I think your suggestion of a guide to setting up a production system would be very useful. In the meantime, if you have any explicit questions, please ask.
0 x

cagabit
Ebase User
Posts: 11
Joined: Fri Nov 20, 2015 6:10 pm

#3

Postby cagabit » Tue Nov 24, 2015 9:50 pm

Hi,

For example could not manage to create a deploy server link:

1)
- right clicking the project name and choosing "deploy"
- clicking the green plus to create a new server link
- name is for the link, ok
- for the url entering http://192.168.1.20:3030/ebase
- entering the user / pass of the remote server ( dont understand why the pass field is repeated ! )

When clicked the "test connection" button, it is failed ! "Could not connect to the target server, please check the url"

At the URL , should I put the project name after /ebase ?

2) Another title can be , hosting static html content, also on tomcat ?
Besides the ebase projects, myweb server should also hold a simple static html page, dont want to setup IIS or apache since it is a very simple task.

Tried many configurations (especially for server.xml file ) from internet but none of them was successfull.

Any clue ?
0 x

Jon
Moderator
Moderator
Posts: 1342
Joined: Wed Sep 12, 2007 12:49 pm

#4

Postby Jon » Wed Nov 25, 2015 9:09 am

1. Deploy connection

The message means that the URL is incorrect or the server couldn't be reached - though it looks OK to me, except that the web app name should be in lower case (I think it's the forum software that changed it to "Ebase"). Try entering the same URL in a browser - you should see the help index page on the target server.

2. Hosting static HTML pages

Create a directory within the web application on the server to hold your content e.g. UfsServer/tomcat/webapps/ebase/mycontent. Then add your HTML files and anything else you need to this. If you set up file1.html in this directory, the url will be:

hostname:port/ebase/mycontent/file1.html

You don't need to configure Tomcat in any way to achieve this.

There is a basic HTML editor in the Ebase designer and you can create and maintain HTML files using this, or you can use external tools. If you use the designer editor, you are then working on an HTML file in your workspace, and you can deploy this to the workspace of a target server. But you will then need to manually copy the file from the workspace to the webapps/ebase directory on the target server.
0 x

cagabit
Ebase User
Posts: 11
Joined: Fri Nov 20, 2015 6:10 pm

#5

Postby cagabit » Wed Nov 25, 2015 5:16 pm

Thank you Jon, for your comments.

1) It is ok now, I can deploy the project but dont know why ! I am sure that before writing here I tested once again without success. I was trying to solve tomcat web server thing , maybe that affected.
This is the worst solution as I dont know the reason.

2) Yes for any static content under /ebase/... it is understood. But what about the ROOT ? My web adress should serve some welcome pages when the adress called www.xxxx.com ( the index.html ) , if www.xxxx.com/ebase callled the ebase system should come.

I put this line, under host section in server.xml file:
< Context docBase= "C:\ebaseXi_5.0\UfsServer\tomcat\webapps\ROOT" path= "ROOT" override= "true" / >
Now if I call 192.168.1.20:3030/index.html it works.
But 192.168.1.20:3030 doesnt work !

Checked the web.xml file , the default page types already there but another , default settings is overriding maybe :
<welcome-file-list>
<welcome-file>index.html</ welcome-file>
<welcome-file>index.htm</ welcome-file>
<welcome-file>index.jsp</ welcome-file>
</ welcome-file-list>
0 x

cagabit
Ebase User
Posts: 11
Joined: Fri Nov 20, 2015 6:10 pm

#6

Postby cagabit » Wed Nov 25, 2015 6:14 pm

I think I got it, for the future reference :

Using ebase v5.0.1 on windows 8




For hosting static pages on TOMCAT with the same application pool as ebase:



1) open folder ROOT under webapps, put your pages into it
2) open WEB-INF folder under the newly created ROOT folder, create WEB.XML file in it and put these lines :

Code: Select all

<web-app xmlns="http&#58;//xmlns.jcp.org/xml/ns/javaee"
  xmlns&#58;xsi="http&#58;//www.w3.org/2001/XMLSchema-instance"
  xsi&#58;schemaLocation="http&#58;//xmlns.jcp.org/xml/ns/javaee
                      http&#58;//xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd"
  version="3.1"
  metadata-complete="true">

      <welcome-file-list>
      	<welcome-file>index.html</welcome-file>
      </welcome-file-list>
</web-app>
(you can also put index.htm , index.jsp files.)

3) In the tomcat/conf/server.xml file, under host section put this line

Code: Select all

<Context docBase="C&#58;\ebaseXi_5.0\UfsServer\tomcat\webapps\ROOT" path="/" override="true" />

When you call <server>:3030 the static pages comes !



For calling ebase pages under another name


1) In the tomcat/conf/server.xml file, under host section put this line

Code: Select all

<Context docBase="C&#58;\ebaseXi_5.0\UfsServer\tomcat\webapps\ebase" path="/test" />
When you call <server>:3030/test ebase content should come !
0 x


Who is online

Users browsing this forum: No registered users and 8 guests