Initialization & Configuration for Liferay Setup on remote server

/ != /root

/tmp is a location for temporary folder which has all permissions 777. It is a good place to import files from external system.

/opt is where to keep custom or manual applications.(Liferay, DA)

/home is where a user is


Run to upload file to server (-r : recursively copy)
 scp -r liferay-ce-portal-tomcat-7.0-ga5-20171018150113838.zip root@74.208.244.157:/tmp/

(ran it on Ubuntu)




In Putty(terminal), go to /tmp

apt-get update (refresh the repo)
apt-get install unzip
unzip xxx.zip
mv liferay-ce-portal-7.0-ga5/ ../opt/



 systemctl status mysql : to check mysql status


systemctl start mysql
 systemctl stop mysql


Go into mysql server and 

create database lportal character set utf8;
exit

-------------------------------------------------------------

For java (make sure it is not open jdk since it does not meet requirements for liferay)

1. Add the PPA
add-apt-repository ppa:webupd8team/java (anywhere cuz it is globally installed)



2. apt-get update

* Whenever adding the PPA, make sure to update repo by running "apt-get update" (anywhere I am it works globally)


3. apt install oracle-java8-installer  (javac -version)

4.apt install oracle-java8-set-default (after this command, you can check java -version)




------------------------------------------------------------------

# Configure JDBC in properties file



1. get vim first 
apt-get install vim

2. go to tomcat/bin

chmod +x * : make all the files in this dir executable since they are interacting each other to run a server

sh startup.sh && tail -f ../logs/catalina.out : run two cmd at the same time



sh startup.sh == ./ startup.sh (startup.sh is to run the server)
tail -f ../logs/catalina.out : to see all tomcat logs 

(ctl + c : exit from tail)



sh shutdown.sh && tail -f ../logs/catalina.out



http://74.208.244.157:8080/

(later on, change dns server in godaddy to point to 8080















Comments

Post a Comment

Popular posts from this blog

How to include CSS, JS and Image in Liferay Portlet JSP

Image
In Init.jsp,  add the following plug-ins to enable CSS and JS to be loaded inside a portlet. <%-- CSS, JS --%> <link href="/o/contact-us-portlet/css/portlet-main.css" rel="stylesheet" /> <script src="/o/contact-us-portlet/js/portlet-main.js"></script> The path starting with /o/(portlet-name)/  is automatically appended to main url (ex. localhost:8080/o/..) /o/(portlet-name)/  represents resources/META-INF/resources One thing to keep in mind is that the above initialization should be done after <liferay-theme:defineObjects /> <portlet:defineObjects /> I DO NOT KNOW WHY ... In view.jsp. can get path through request src="<%=request.getContextPath()%>/images/form-icon.png" Prerequisite: In bnd.bnd Web-ContextPath: /contact-us-portlet  should be set . ------------------------------------------------------------------------- Today's trouble sh...
Read more

AWS Web App 3-tier Architecture

Image
1. A user will query Route 53 for an alias record. 2. Using the alias record, the user will go straight to Elastic Load Balancer which is in the public subnet as it has to be accessible from the World Wide Web(WWW). 3. Behind the ELB, There is the Auto Scaling Group. In order for the ASG to be highly available, it is split between two Availability Zones. The ASG spins up EC2 instances (4 instances and two in each AZ in the diagram). 4. The ELB spreads out the load onto each instance. Instances can be added as scale-out or removed as scale-in which allows the ASG to be responding to high traffic or low traffic. 5. The instances usually talk directly to RDS (Relational Database Service) database to do some operations. For resilience to failure, RDS master has RDS slave (standby replica) using cross-AZ replication. If the master RDS db fails, the application automatically fall over to RDS slave. 6. ElastiCache cluster (mainly Redis) allow the application to read stuff o...
Read more