GI Test Enviroment Tasks

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 7

Cairo Environment Server Tasks

A. DB Tasks:
1. Login:
Sqlplus / as sysdba
or
Sqlplus sys/oramanager@xcom
2. Grant:
SQL GRANT is a command used to provide access or privileges on the database objects to the users.
The Syntax for the GRANT command is:

GRANT privilege_name
ON object_name
TO {user_name |PUBLIC |role_name}
[WITH GRANT OPTION];

privilege_name is the access right or privilege granted to the user. Some of the access rights
are ALL, EXECUTE, and SELECT.

object_name is the name of an database object like TABLE, VIEW, STORED PROC and
SEQUENCE.

user_name is the name of the user to whom an access right is being granted.

user_name is the name of the user to whom an access right is being granted.

PUBLIC is used to grant access rights to all users.

ROLES are a set of privileges grouped together.

WITH GRANT OPTION - allows a user to grant access rights to other users.

For Example: GRANT SELECT ON employee TO user1;This command grants a SELECT permission on
employee table to user1.You should use the WITH GRANT option carefully because for example if you
GRANT SELECT privilege on employee table to user1 using the WITH GRANT option, then user1 can
GRANT SELECT privilege on employee table to another user, such as user2 etc. Later, if you REVOKE
the SELECT privilege on employee from user1, still user2 will have SELECT privilege on employee table.

3. Revoke:
The REVOKE command removes user access rights or privileges to the database objects.
The Syntax for the REVOKE command is:

1
Mohamed F. Shehata

REVOKE privilege_name
ON object_name
FROM {user_name |PUBLIC |role_name}

For Example: REVOKE SELECT ON employee FROM user1;This command will REVOKE a SELECT
privilege on employee table from user1.When you REVOKE SELECT privilege on a table from a
user, the user will not be able to SELECT data from that table anymore. However, if the user has
received SELECT privileges on that table from more than one users, he/she can SELECT from that
table until everyone who granted the permission revokes it. You cannot REVOKE privileges if they
were not initially granted by you.

4. Creating Roles:
The Syntax to create a role is:

CREATE ROLE role_name


[IDENTIFIED BY password];
For Example: To create a role called "developer" with password as "pwd",the code will be as follows

CREATE ROLE testing


[IDENTIFIED BY pwd];
It's easier to GRANT or REVOKE privileges to the users through a role rather than assigning a
privilege directly to every user. If a role is identified by a password, then, when you GRANT or
REVOKE privileges to the role, you definitely have to identify it with the password.
We can GRANT or REVOKE privilege to a role as below.
For example: To grant CREATE TABLE privilege to a user by creating a testing role:
First, create a testing Role

CREATE ROLE testing


Second, grant a CREATE TABLE privilege to the ROLE testing. You can add more privileges to the
ROLE.

GRANT CREATE TABLE TO testing;


Third, grant the role to a user.

2
Mohamed F. Shehata

GRANT testing TO user1;


To revoke a CREATE TABLE privilege from testing ROLE, you can write:

REVOKE CREATE TABLE FROM testing;


The Syntax to drop a role from the database is as below:

DROP ROLE role_name;


For example: To drop a role called developer, you can write:

DROP ROLE testing;

5. Export schema:
exp qtelni/qtelni file=/app/gdm/qtelni_today.dmp log=/app/gdm/ qtelni_today.log
6. Import schema:
imp system/oramanager fromuser=qtelni touser=test
file=/app/gdm/qtelni_today.dmp log=/app/gdm/qtelni_today.log
B. Weblogic tasks:
1. Stopping The Managed Servers, Granite domain:
a.
b.
c.
d.

Open http://192.168.10.29:7001/console
In the Home page, from Environment > Servers.
In the summary of servers page, press the control tab.
In the list of servers, shutdown them all one by one by selecting the check
box then go to shutdown menu, then force shutdown now. Shutdown servers
is done in the following order (PLEASE DONT FORGET THE ORDERS!)
i.
webaccess
ii.
opi
iii.
customer_app
iv.
granite_core
v.
admin
e. After finishing shut down all servers and the admin server, your session will
kick you out.
2. Starting the Managed Servers:
Important: Each server should be started in the order, one server at a time. Make
sure server is in RUNNING status (in the log file) as below prior to going to the next
server in the list below.

3
Mohamed F. Shehata

a. Login to webLogic on 192.168.10.29


b. Type: cd /app/bea/user_projects/domains/granite
c. Type:
./startadmin.sh
d. Make sure you see the word (Server started in RUNNING mode) before
going to the next step.
e. Type:
./startgranitecore.sh
f. Make sure you see the word (Server started in RUNNING mode) before
going to the next step.
g. Type:
./startcustomerapp.sh
h. Make sure you see the word (Server started in RUNNING mode) before
going to the next step.
i. Type:
./startopi.sh
j.

Make sure you see the word (Server started in RUNNING mode) before
going to the next step.
k. Type:
./startwebaccess.sh
l.

Make sure you see the word (Server started in RUNNING mode)

3. Stopping The Managed Servers, IIEP domain:


a.
b.
c.
d.

Open http://192.168.10.29:7101/console
In the Home page, from Environment > Servers.
In the summary of servers page, press the control tab.
In the list of servers, shutdown them all one by one by selecting the check
box then go to shutdown menu, then force shutdown now. Shutdown servers
is done in the following order (PLEASE DONT FORGET THE ORDERS!)
i.
iiep_core
ii.
gateway
iii.
granite_core
iv.
admin
e. After finishing shut down all servers and the admin server, your session will
kick you out.
4. Starting the Managed Servers:
Important: Each server should be started in the order, one server at a time. Make
sure server is in RUNNING status (in the log file) as below prior to going to the next
server in the list below.

4
Mohamed F. Shehata

m. Login to webLogic on 192.168.10.29


n. Type: cd /app/bea/user_projects/domains/iiep
o. Type:
./startadmin.sh
p. Make sure you see the word (Server started in RUNNING mode) before
going to the next step.
q. Type:
./startgranitecore.sh
r.

Make sure you see the word (Server started in RUNNING mode) before
going to the next step.
s. Type:
./startgateway.sh
t. Make sure you see the word (Server started in RUNNING mode) before
going to the next step.
u. Type:
./startiiepcore.sh
v. Make sure you see the word (Server started in RUNNING mode)

C. Login credentials:
1. Unix Credentials:
IP address

192.168.10.29

User

Password

root

root123

oracle

oracle

weblogic

weblogic

2. DB Credentials:
Oracle
SID
xcom

User

Password

Comments

sys

oramanager

Oracle sys account

system

oramanager

Oracle system account


5

Mohamed F. Shehata

qtelni

qtelni

Testing schema

fulfillment_test

fulfillment_test

Interface Schema

reporting

reporting

Interface reporting schema

etl

orcl

DM schema

granite_loader_g

orcl

DM schema

granite_loader_work_g

orcl

DM schema

**For any other user schema, username=password

6
Mohamed F. Shehata

3. Weblogic Credentials
Weblogic Domain

http://192.168.10.29:7001/
console

http://192.168.10.29:7101/
console

User

Passwor
d

Comments

syste
m

Or@cleWL
10

Used in Granite admin tasks

deploy
er

deployer1
!

Used in deployment tasks by


testing team

syste
m

weblogic1
0

Used in IIEP admin tasks

7
Mohamed F. Shehata

You might also like