How to Install Jboss Web Server2

 Installation Guide Jboss Web Server2

RPM Required

krb5-workstation

mod_auth_kerb

elinks (required for the apachectl functionality)

1. Install RPM

# yum install krb5-workstation m od_auth_kerb elinks

Check RPM

# rpm -q krb5-workstation m od_auth_kerb elinks

Installing Java

2.  On the command line, as the root user run the command to install Java 1.6 or 1.7:

A. On Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6, execute the yum install

command to install Java 1.6:

# yum install java-1.6.0-<VENDOR>-devel

Execute the following variation of the listed command to install Java 1.7:

# yum install java-1.7.0-<VENDOR>-devel

3. Run the following commands as the root user (if switching from another user, make sure to run the

command su -) to make sure the correct JDK is in use:

# alternatives --config java

# alternatives --config javac

T hese commands return lists of available JDK versions with the version in use marked with a plus

(+) sign. If the set JDK is not the desired option, switch to the right JDK as instructed on the

command line.

Download JBoss Operations Network (JON) Plugin

Complete this task to download the JBoss Operations Network (JON) plugin for JBoss Enterprise Web

Server from the Red Hat Customer Portal.

Procedure 2.3. Download Installation Files

1. Open http://access.redhat.com in a web browser.

2. Click Downloads in the menu across the top of the page.

3. Click Downloads in the list under JBoss Enterprise Middleware.

4. Enter your login information.

You are taken to the Software Downloads page.

5. Download the JBoss Operations Network Plugin

If you intend to use the JBoss Operations Network plugin for JBoss Enterprise Web Server, select

JBoss ON for EWS from either the Software Downloads drop-down box, or the menu on the left.

a. Click the JBoss Operations Network VERSION Base Distribution download link.

b. Click the Download link to start the Base Distribution download.

c. Repeat the steps to download the EWS Plugin Pack for JBoss ON VERSION

Installing Enterprise Web Server from a ZIP File

Make sure that you have installed all the required packages before you install JBoss Enterprise Web

Server from a Z IP file

Downloading and Extracting the ZIP File

T o install JBoss Enterprise Web Server, download and extract the installation Z IP file. T he Z IP file is

available on the Red Hat Customer Portal.

Downloading the Enterprise Web Server ZIP File

Download the JBoss Enterprise Web Server Z IP files (jboss-ews-application-servers-2.0.1-

<platform >-<architecture>.zip and jboss-ews-httpd-2.0.1-<platform >-

<architecture>.zip) from the Red Hat Customer Portal site:

1. Open http://access.redhat.com in your web browser.

2. In the upper right corner, click the Log in button.

3. Enter your login information and click Log in.

4. Hover over the Downloads option in the menu bar at the top of the page and under JBoss

Enterprise Middleware in the displayed menu, click Downloads.

5. In the Product drop-down box column, click Web Server.

6. On the Software Downloads page, select the product version in the Version drop-down box and in

the Releases tab below, click the JBoss EWS link with the correct version.

7. On the Software Details page, click the Download button next to the File drop-down box for the

jboss-ews-application-servers-2.0.1-<platform >-<architecture>.zip and

jboss-ews-httpd-2.0.1-<platform >-<architecture>.zip files.

8. Confirm the file downloads have successfully completed.

Unzip the downloaded Z IP files:

1. On the command line, change to the directory with the Z IP files.

2. Run the following unzip command, once for each Z IP file:

unzi p <FILE_NAME> -d <TARGET_DIRECTORY>

Substitute FILE_NAME with the name of each downloaded file and TARGET_DIRECTORY with the

path to the target directory. After the Z IP files are extracted, configure the environment before

running JBoss Enterprise Web Server 

Configuring the Environment

Setting JAVA_HOME

1. In the bin directory of your T omcat (either $EWS_HOME/tom cat6/bin or

$EWS_HOME/tom cat7/bin), create the setenv.sh file.

For example, run the command vim tom cat<VERSION>/bin/setenv.sh

2. Add the JAVA_HOME path definition into the file.

For example export JAVA_HOME=/usr/lib/jvm /jre-1.6.0-openjdk.x86_64

Creating tomcat User

Follow this procedure to create the tomcat user and its parent group:

1. At the shell prompt, become the root user.

2. Run the following command to create the tomcat user group:

# groupadd -g 91 -r tom cat

3. Go to /opt/jboss-ews-2.0.

4. From /opt/jboss-ews-2.0, run the following command to create the tomcat user in the tomcat user

group:

# useradd -c "Tom cat" -u 91 -g tom cat -s /bin/sh -r tom cat

5. From /opt/jboss-ews-2.0, run the following command to assign the ownership of the tomcat

directories to the tom cat user and allow the user to run the tomcat service:

# cho wn -R to mcat:to mcat to mcat<VERSION>

Substitute <VERSION> with the respective tomcat version number (6 or 7).

6. From /opt/jboss-ews-2.0, issue the command ls -l and check if the tomcat user is the owner of

the T omcat directory.

7. Make sure that the tom cat user has the execution permission to all parent directories.

Setting the apache User

Follow this procedure to set up the apache user:

1. Run the following commands as the root user to create the apache user group:

# groupadd -g 48 -r apache

2. Run the following command to create the apache user in the apache user group:

# useradd -c "Apache" -u 48 -g apache -s /bin/sh -r apache

3. Change to /opt/jboss-ews-2.0 and run the following command to assign the ownership of the

apache directories to the apache user and allow the user to run httpd:

# chown -R apache:apache httpd

4. From /opt/jboss-ews-2.0, issue the command ls -l and check that the apache user has

execution permission to the respective Apache install path. Output is similar to the following:

drwxrwxr-- 11 apache apache 4096 Feb 14 06:52 httpd

Removing SSL

JBoss Enterprise Web Server supports SSL by default, but it can be removed.

Follow this procedure to remove or re-add SSL:

1. Go to the /opt/jboss-ews-2.0/httpd/conf.d/ directory.

2. Rename the SSL configuration file:

A. T o remove SSL, rename ssl.conf to ssl.conf.disabled.

B. T o re-add SSL, rename ssl.conf.disabled to ssl.conf.

Configuring log4 j

Follow this procedure to add log4 j logging to T omcat:

1. Go to the /opt/jboss-ews-2.0/extras/ directory.

2. Copy the log4 j.jar and log4 j.properties files to the lib directory of the T omcat

directory:

A. If using T omcat 6, run the following commands:

extras]# cp log4j.properties ../tom cat6/lib/

extras]# cp log4j.jar ../tom cat6/lib/

B. If using T omcat 7, run the following commands:

extras]# cp log4j.properties ../tom cat7/lib/

extras]# cp log4j.jar ../tom cat7/lib/

Configuring mod_jk

T o configure the HT T P Server to use mod_jk, define the following:

available workers (JBoss instances) in the workers.properties file

the mod_jk configuration file

Follow this procedure to configure the HT T P Server to use mod_jk as its load balancer:

1. In the /opt/jboss-ews-2.0/httpd/conf/ directory, create workers.properties.

2. In the /opt/jboss-ews-2.0/httpd/conf.d/ directory, create m od_jk.conf.

Configuring mod_cluster

T he mod_cluster configuration can be customized in /opt/jboss-ews-

2.0/httpd/conf.d/m od_cluster.conf.

For further information about customizing mod_cluster, refer to the JBoss HTTP Connector section of

the HTTP Connectors and Load Balancing Guide.

Procedure 2.13. Running the Post-Installation Script

Follow this procedure to run the post-installation script:

1. At the shell prompt, become the root user.

2. Change to the /opt/jboss-ews-2.0/httpd directory.

3. Run the following command:

# ./.postinstall

Starting and Stopping Tomcat

T omcat can be started, stopped, and configured to start automatically at boot time either from the

command line or using a graphical tool.

T he tom cat6 or tom cat7 services can be started and stopped using the service command as root

on a console window (as is typical of a network service):

T o start and stop the tom cat6 service:

# service tom cat6 start

# service tom cat6 stop

T o start and stop the tom cat7 service:

# service tom cat7 start

#service tom cat7 stop

Once the tomcat service has been started, you can verify that it is running by pointing your web browser

to http://localhost:8080.

T he tomcat service runs under a new tomcat system user. Due to file system permissions it may be

necessary to use the su -s /bin/bash tom cat system command to deploy the application under the

webapps directory. Alternatively, a developer can be listed in the tomcat user group by the system

administrator. T he best approach is to use the Web Console (URL above) to deploy the application.

T he behavior at boot can be controlled with the chkconfig command (see the chkconfig man page

for further details).

Configuration can then be altered in the /etc/sysconfig/tom cat6 file for T omcat version 6 and the

/etc/sysconfig/tom cat7 file for T omcat version 7.

Running Tomcat

T he following procedure outlines the steps to run Tomcat.

Running Tomcat on Red Hat Enterprise Linux

1. After extracting the zip file, check to see if a user called tom cat exists on the system by running

the following command:

id tom cat

2. If the user does not exist, use the following command to add it:

groupadd -g 91 -r tom cat

useradd -c "Tom cat" -u 91 -g tom cat -s /bin/sh -r tomcat

3. If the tom cat user will be running T omcat, change the ownership of the tomcat directories.

a. Use the following command for T omcat 6:

chown -R tomcat:tomcat tom cat6

A. Use the following command for T omcat 7:

chown -R tom cat:tom cat tom cat7

4. T est that the tom cat user has execution permission to the tomcat install path.

5. Set the JAVA_HOME variable. Use one of the following approaches to set this variable.

a. Provide the value for JAVA_HOME externally by setting the value prior to starting T omcat.

A. Set the value for JAVA_HOME in the setenv.sh file. In T omcat 6, this file is available at

tom cat6/bin/ and in T omcat 7, this file is available at tom cat7/bin/. T his value is

loaded from catalina.sh and overrides all other set values for JAVA_HOME.

Start Tomcat

T o start T omcat, execute the following script as the user tom cat:

sh startup.sh

Once the T omcat service has been started, you can verify that it is running by pointing your web

browser to http://localhost:8080.

Stop Tomcat

T o stop T omcat, execute the following script as the user tom cat:

sh shutdown.sh

2.5.5. Starting and Stopping the HTTP Server

T he HT T P Server can be started, stopped, and configured to start automatically at boot time either from

the command line or using a graphical tool.

T he following examples of running the HT T P Server will also cover the differences of undertaking this

on Red Hat Enterprise Linux 5 and 6.

You can start and stop the HT T P Server service using the service command as root on a console

terminal (as is typical of a network service):

T o start and stop the HT T P Server service on Red Hat Enterprise Linux 5 and 6:

service httpd start

service httpd stop

Configuration can then be altered in the /etc/sysconfig/httpd file on Red Hat Enterprise Linux 5

and 6.

2.5.6. Running the HTTP Server

After you have extracted the Enterprise Web Server Z IP file, change into the httpd directory and run the

post install script by executing the following:

./.postinstall

Check to see if a user called apache exists on the system by running the following command:

id apache

If the user does not exist then it will need to be added, along with the appropriate usergroup. In order to

achieve this, execute the following:

/usr/sbin/groupadd -g 91 -r apache 2> /dev/null || :

/usr/sbin/useradd -c "Apache" -u 48 \ -s /sbin/nologin -r -d %{contentdir} apache

2> /dev/null || :

Once this is completed, if the apache user will be running the httpd service, then the ownership of the

HT T P directories will need to be changed to reflect this:

chown -R apache:apache httpd

T o test that the above commands have been successful, check that the apache user has execution

permission to the HTTP server install path.

Start the HT T P server by changing to the httpd directory and executing:

su -m -c "./sbin/apachectl start"

Stop the HT T P server by executing:

su -m -c "./sbin/apachectl stop"

Installation guidance for MS SQL Server on Linux

This article provides guidance for installing, updating, and uninstalling SQL Server 2017 and SQL Server 2019 preview on Linux.
Prerequisites
You must have a RHEL 7.3, 7.4, 7.5, or 7.6 machine with at least 2 GB of memory.

Supported platforms

SQL Server 2017 is supported on Red Hat Enterprise Linux (RHEL), SUSE Linux Enterprise Server (SLES), and Ubuntu. It is also supported as a Docker image, which can run on Docker Engine on Linux or Docker for Windows/Mac.

Platform	Supported version(s)	Get
Red Hat Enterprise Linux	7.3, 7.4, 7.5, 7.6	Get RHEL 7.6
SUSE Linux Enterprise Server	v12 SP2	Get SLES v12 SP2
Ubuntu	16.04	Get Ubuntu 16.04
Docker Engine	1.8+	Get Docker

System requirements

SQL Server 2017 has the following system requirements for Linux:

Memory	2 GB
File System	XFS or EXT4 (other file systems, such as BTRFS, are unsupported)
Disk space	6 GB
Processor speed	2 GHz
Processor cores	2 cores
Processor type	x64-compatible only

If you use Network File System (NFS) remote shares in production, note the following support requirements:

• Use NFS version 4.2 or higher. Older versions of NFS do not support required features, such as fallocate and sparse file creation, common to modern file systems.
• Locate only the /var/opt/mssql directories on the NFS mount. Other files, such as the SQL Server system binaries, are not supported.
• Ensure that NFS clients use the 'nolock' option when mounting the remote share.

https://docs.microsoft.com/en-us/sql/linux/quickstart-install-connect-red-hat?view=sql-server-ver15

How To: Configure WINRM for HTTP

     Configure HTTP Connection

      Use an HTTP connection type to connect WINRM-Server to Client 

     Follow these steps:

1. To use HTTP to connect to WinRM on the server side, enter the following command:

   
   winrm create winrm/config/listener?Address=*+Transport=HTTP
   

2. Enter the following command to test the WinRM connection:

   
   winrm identify -r:http://winrm_server:5985 -auth:kerberos -u:user_name -p:password -encoding:utf-8
   

   A section in the displayed response is as follows:

   
   IdentifyResponse
   
     ProtocolVersion = http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd
   
     ProductVendor = Microsoft Corporation
   
     ProductVersion = OS: 6.1.7600 SP: 0.0 Stack: 2.0
   

How To: Configure WINRM for HTTPS

 Configure WINRM for HTTPS

WinRM uses the HTTPS connection type on the Hyper-V server when you use SSL to connect to the server. The default HTTPS port is 5986.

Follow these steps:

1.    Generate a self-signed certificate for the remote host.

a.    In Server Manager, navigate to Roles, Web Server (IIS), Internet Information Services, and select the name of the server for which you want to generate the certificate.

b.    In IIS, open Server Certificates.

c.     In Actions, click Self-Signed Certificate.

d.    Define a certificate name, and then click OK.
The certificate appears in Server Certificates list.

e.    (Optional) Verify that the certificate exists in the correct certificate store.

§  Navigate to Start, Run, and execute the following command:

certmgr.msc

§  Navigate to Trusted Root Certificate Authorities, Certificates.
Verify that the latest certificate appears in the list.

2.    Enter the following command to find the thumbprint of the certificate for the remote host:

Get-childItem cert:\LocalMachine\Root\ | Select-String -pattern <HOSTNAME>

3.    Enter the following command to create an HTTPS WinRM listener for the remote host (xendesktop server) with the thumbprint from the previous step:

winrm create winrm/config/Listener?Address=*+Transport=HTTPS @{Hostname="<CN>"; CertificateThumbprint="<THUMBPRINT>"}

4.    Export the certificate.

Note: CA recommends that you export certificates to removable media, such as a floppy disk or USB flash drive.

a.    Click the Windows Start button.

b.    Enter certmgr.msc in the Search field.

c.     Enter administrator credentials, if prompted.
The Certificate Manager opens.

d.    Right-click the certificate that you want to export, choose All Tasks, then click Export.

e.    Click Next in the Certificate Export Wizard.

f.     Click No, do not export the private key and then click Next.

g.    Select the Base64 encoded X.509 format, then click Next.
The export process creates a file to store the certificate.

h.    Specify a name and location for the certificate file.

i.      Click Finish.

5.    Create a keystore file to connect client side (configuration). This procedure explains the usage of Java keytool to generate the keystore. The keystore can be generated from a machine where JRE is installed and available in %PATH%.

a.    Enter the following command:

Keytool -importcert -file “<CERTIFICATE>” -keystore “<KEYSTORE>.jks”

For CERTIFICATE, enter the file name of the certificate exported in the previous step.
For KEYSTORE, enter a name for the keystore in the format <path\name>.jks.
For example:

keytool -importcert -file "C:\Test1.cer" -keystore "C:\test.jks”

b.    Enter a password when prompted.

c.     Enter Yes when prompted to trust the certificate.
The keystore is available in the path specified.

6.    Copy the keystore file to the client  machine where the you want to make connection.

7.    In the App configuration GUI, edit or create the profile that represents the  server:

a.    Click the Use SSL check box and set the Port as 5986.

b     Enter the appropriate information in the Keystore Location and Keystore Password fields.

c.    Click OK.

How to Configuring Cisco IP Phone Voice Traffic

   Configuring Cisco IP Phone Voice Traffic

You can configure a port connected to the Cisco IP Phone to send CDP packets to the phone to configure the way in which the phone sends voice traffic. The phone can carry voice traffic in IEEE 802.1Q frames for a specified voice VLAN with a Layer 2 CoS value. It can use IEEE 802.1p priority tagging to give voice traffic a higher priority and forward all voice traffic through the native (access) VLAN. The Cisco IP Phone can also send untagged voice traffic or use its own configuration to send voice traffic in the access VLAN. In all configurations, the voice traffic carries a Layer 3 IP precedence value (the default is 5).

Beginning in privileged EXEC mode, follow these steps to configure voice traffic on a port:

Steps	Command	Purpose
Step 1	configure terminal	Enter global configuration mode.
Step 2	interface interface-id	Specify the interface connected to the phone, and enter interface configuration mode.
Step 3	mls qos trust cos	Configure the interface to classify incoming traffic packets by using the packet CoS value. For untagged packets, the port default CoS value is used. Note Before configuring the port trust state, you must first globally enable QoS by using the mls qos global configuration command.
Step 4	switchport  voice {detectcisco-phone [full-duplex] | vlan {vlan-id |dot1p | none |untagged}}	Configure how the Cisco IP Phone carries voice traffic: •detect—Configure the interface to detect and recognize a Cisco IP phone. •cisco-phone—When you initially implement the switchport voice detect command, this is the only allowed option. The default is no switchport voice detect cisco-phone [full-duplex]. •full-duplex—(Opti

Mount CD/DVD ROM on RHEL 7 Linux

       

Instructions

Locate Block device

First we need to find a correct CD/DVD block device. To do this execute a command blkid:

# blkid
/dev/sda1: UUID="937c8752-0206-4c5a-a25f-63a187b1a749" TYPE="xfs"
/dev/sda2: UUID="fWxSbV-Y4mQ-CJbE-HUTb-XsnF-DsGB-1ThV6s" TYPE="LVM2_member"
/dev/sr0: UUID="2015-10-30-11-11-49-00" LABEL="RHEL-7.2 Server.x86_64" TYPE="iso9660" PTTYPE="dos"
/dev/mapper/rhel-root: UUID="63b73273-3de4-423d-9a85-8c99701fb137" TYPE="xfs"
/dev/mapper/rhel-swap: UUID="0f3f07ac-d817-4f2c-9b74-b7223b486605" TYPE="swap"
/dev/mapper/rhel-home: UUID="467a69d7-6fec-4a07-bec9-e1e9d7cb1ad8" TYPE="xfs"

Take a note of the relevant block device eg. /dev/sr0 and optionally also take a note of the shown UUID Take a note of the relevant block device eg. /dev/sr0 and optionally also take a note of the shown UUID 2016-10-19-18-32-06-.

Create a mount point

Next, create a new directory or use existing to be used as a mount point:

# mkdir /media/rhel

Permanent CD/DVD mount using fstab

The above will mount your CD/DVD ROM only temporarily. In order to make this mount permanent after reboot edit /etc/fstab configuration file by adding a following line replacing UUID to match your previous blkid command output:

UUID=2015-10-30-11-11-49-00             /media/rhel   iso9660 ro,user,auto  0 0 

[root@xyz ~]# df -h
Filesystem             Size  Used Avail Use% Mounted on
/dev/mapper/rhel-root   50G  3.3G   47G   7% /
devtmpfs               2.9G     0  2.9G   0% /dev
tmpfs                  2.9G  140K  2.9G   1% /dev/shm
tmpfs                  2.9G  8.9M  2.9G   1% /run
tmpfs                  2.9G     0  2.9G   0% /sys/fs/cgroup
/dev/mapper/rhel-home  144G  3.9G  140G   3% /home
/dev/sda1              497M  157M  340M  32% /boot
tmpfs                  581M   28K  580M   1% /run/user/0
/dev/sr0               3.8G  3.8G     0 100% /media/rhel

SVN server 1.7 configuration with apache 2.4 on Centos 7 with Ldap auth

Step1

 Add AD Domain joining process of Centos Machine

Install following rpms using yum command

yum install sssd realmd oddjob oddjob-mkhomedir adcli samba-common samba-common-tools krb5-workstation openldap-clients

policycoreutils-python mod_ldap -y

Check your DNS AD server ip entry

[root@centos7 ~]# cat /etc/resolv.conf
search example.com
nameserver 192.168.1.2

Join Domain

[root@centos7 ~]# realm join --user=administrator example.com
Password for administrator:

check domain details

root@centos7 ~]# realm list

Reboot the Centos Machine




2. Here we will install Apache server as webserver for the SVN repository

yum -y install subversion subversion-tools mod_dav_svn

mkdir /var/svn

svnadmin create /var/svn/devrepo

chown -R apache:apache /var/svn/devrepo/

chcon -R -t httpd_sys_content_t /var/svn/devrepo/

chcon -R -t httpd_sys_rw_content_t /var/svn/devrepo/

Edit file

vi /etc/httpd/conf.modules.d/10-subversion.conf
LoadModule dav_svn_module     modules/mod_dav_svn.so
LoadModule authz_svn_module   modules/mod_authz_svn.so
LoadModule dontdothat_module  modules/mod_dontdothat.so
LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
LoadModule ldap_module modules/mod_ldap.so

###For LOCAl user authontiation

Alias /svn /var/svn/
 <Location /svn>
 DAV svn
 SVNParentPath /var/svn/
 AuthType Basic
 AuthName "Authentication Realm"
 AuthUserFile /var/svn/svn.user
 AuthzSVNAccessFile /var/svn/devrepo/conf/authz
 Require valid-user
</Location>

###savefile &exit

systemctl start httpd.service

htpasswd -cm /var/svn/svn.user svnadmin

systemctl reload httpd.service

mkdir -p /tmp/repository/project1/{trunk,branches,tags}


svn import -m 'Initial Import' /tmp/repository/project1/ http://SVN-Server/svn/devrepo

####Now access in browser service server working withe svnadmin login ##########

#####################################################
3. If Now configure Active directory Auth with svn
#####################################################

#######add the following entries in 10-subversion .comf##########

vi /etc/httpd/conf.modules.d/10-subversion.conf

Alias /svn /var/svn/
<location /svn>
DAV svn
SVNParentPath /var/svn/
SVNListParentPath on
order allow,deny
allow from all
#Options Indexes
AuthType Basic
#AthzLDAPAuthoritative On
AuthBasicProvider ldap
AuthLDAPBindDN svnadmin@example.com
AuthLDAPBindPassword s!^n1$n*l
Require valid-user svnadmin@example.com
AuthLDAPURL "ldap://192.168.2.200:3268/dc=example,dc=com?sAMAccountName?sub?(objectCategory=person)"
Require ldap-group CN=svnadmin,OU=users,DC=example,DC=com
AuthzSVNAccessFile /var/svn/devrepo/conf/authz

##save& exit###

####edit file add following######

Vi /var/svn/devrepo/conf/svnserve.conf

anon-access = none
authz-db = authz
auth-access = write

### save& exit###

systemctl restart httpd.service         #### Now check you will be able login in svn via domain user#########

############################################
4. iMPLEMENT PERMISSION ON SVN DIRECTORY
############################################

####Edit file authz to restricted directory####

vi /var/svn/devrepo/conf/authz

[groups]
admin = svnadmin,
devaccess = USER1,user2
qaaccess =  user3,user4

[/]
* = r

[devrepo:/trunk]
@admin = rw
@qaaccess = rw
@qaaccess = r

[devrepo:/branches]
@qaaccess = r
@devaccess = rw
* = r

[devrepo:/tags]
* = r
@qaaccess = rw
@devaccess = rw


##save & exit#####

Restart apache serverice

systemctl restart httpd.service

chkconfig httpd on


### Now svn server has been created Enjoy#####