quarta-feira, 6 de novembro de 2013

sudo - Algumas dicas, truques e informações.

Vamos a um resumo do sudoers.


1 - O que é sudoers?
Executando o comando "man sudo" a primeira linha do que é a aplicação é retornado '
sudo, sudoedit — execute a command as another user" resumindo, com o sudoers configurado conseguimos executar qualquer comando como se fossemos outro usuário.

2 - Como é realizado a sua configuração? 
Dentro de nossos servidores linux temos o arquivo /etc/sudoers que contém toda a configuração do sudo para editar o arquivo devemos usar o visudo, que valida as sintaxes que estão sendo alteradas/adicionadas, evitando assim "DEDADAS"

3 - Configurando o sudoers
O arquivo de configuração do sudo é o /etc/sudoers, onde se encontra as permissões e usuários que poderam executar algum comando. 

Geralmente, em algumas distros, este arquivo é protegido conta edição, existindo um comando exclusivo para manipulação, o comando visudo. O qual deve-se utilizar para edição do sudo.

Com o comando sudo pode-se delegar autoridade para execução de comandos ou coleção de comandos exclusivos a um usuário especifico ou a um grupo de usuários.

OBS: O arquivo de configuração /etc/sudoers deve ser editado unicamente pelo comando *'visudo'.*

Com o sudo o administrador pode especificar que um determinado usuário só poderá executar um comando com status administrativo de um host específico.

Host Aliases:

Pode definir alias para grupos de máquinas ou para host específico.

Exemplos: 
Host_Alias     FILESERVERS = fs1, fs2 # com dns local
Host_Alias     MAILSERVERS = 10.0.0.1, 10.1.1.1
Host_Alias     SERVERS = 10.0.0.2, dns, firewall, dhcp, www

User Aliases:

Pode definir alias para grupos de usuários ou para um usuário específico. Inclusive com informações oriundas de LDAP, NIS, AD e arquivos de configuração de Linux

Exemplos: 
User_Alias ADM = %groupname %administradores
User_Alias ADMINS = ricardobn, ricardo.brito
User_Alias WEBMASTERS = pedro, rodrigo, eliana

Command Aliases:

Pode definir alias para grupos de comandos ou para um comando específico. 
Cmnd_Alias     DUMPS = /usr/bin/mt, /usr/sbin/dump, /usr/sbin/rdump,\
                       /usr/sbin/restore, /usr/sbin/rrestore
Cmnd_Alias     KILL = /usr/bin/kill
Cmnd_Alias     PRINTING = /usr/sbin/lpc, /usr/bin/lprm
Cmnd_Alias     SHUTDOWN = /usr/sbin/shutdown
Cmnd_Alias     HALT = /usr/sbin/halt
Cmnd_Alias     REBOOT = /usr/sbin/reboot
Cmnd_Alias     SHELLS = /usr/bin/sh, /usr/bin/csh, /usr/bin/ksh, \
               /usr/local/bin/tcsh, /usr/bin/rsh, \
               /usr/local/bin/zsh
Cmnd_Alias     SU = /usr/bin/su

Subgrupo para administração de rede: 
Cmnd_Alias NETWORKING = /sbin/route, /sbin/ifconfig, /bin/ping, /sbin/dhclient, /usr/bin/net, /sbin/iptables, /usr/bin/rfcomm, /usr/bin/wvdial, /sbin/iwconfig, /sbin/mii-tool

Subgrupo para Instalação e gerenciamento de software: 
Cmnd_Alias SOFTWARE = /bin/rpm, /usr/bin/up2date, /usr/bin/yum

Subgrupo para administração de serviços: 
Cmnd_Alias SERVICES = /sbin/service, /sbin/chkconfig

Subgrupo para administração de atualização da base de dados local: 
Cmnd_Alias LOCATE = /usr/sbin/updatedb

Subgrupo para administração dos dispositivos de bloco: 
Cmnd_Alias STORAGE = /sbin/fdisk, /sbin/sfdisk, /sbin/parted, /sbin/partprobe, /bin/mount, /bin/umount

Subgrupo para administração para Delegação de permissões: 
Cmnd_Alias DELEGATING = /usr/sbin/visudo, /bin/chown, /bin/chmod, /bin/chgrp

Subgrupo para administração de Processos: 
Cmnd_Alias PROCESSES = /bin/nice, /bin/kill, /usr/bin/kill, /usr/bin/killall

Subgrupo para administração de Drivers: 
Cmnd_Alias DRIVERS = /sbin/modprobe



4 - Modo Avançado
Delegação de autoridade:

É aconselhável desabilitar o *"ssh hostname sudo <cmd>"*, porque executando o ssh desta maneira será apresentado a senha em claro. Em vez disto execute *"ssh -t hostname sudo <cmd>"*

Esta é a parte principal, que habilita o que o usuário pode executar e em que máquina. O arquivo /etc/sudoers pode ser compartilhado entre múltiplos sistemas para que se tenha efeito.

Sintaxe:

   user    MACHINE=COMMANDS

Seção de Comandos:

Permite ao usuário root executar qualquer comando de qualquer lugar;

   root    ALL=(ALL)     ALL

Permite aos membros do grupo 'sys' executarem todos os comandos especificados neste alias:

   %sys ALL = NETWORKING, SOFTWARE, SERVICES, STORAGE, DELEGATING, PROCESSES, LOCATE, DRIVERS

Permite aos membros do grupos wheel executarem todos os comandos:

   %wheel    ALL=(ALL)    ALL

Permite aos membros do grupos wheel executarem todos os comandos sem a necessidade de senhas:

   %wheel    ALL=(ALL)    NOPASSWD: ALL

Permite a todos os membros do grupo 'users' executarem os comandos mount e umount sobre o cdrom como superusuário:

   %users  ALL=/sbin/mount /mnt/cdrom, /sbin/umount /mnt/cdrom

Permite a todos os membros do grupo 'users' executar o comando 'shutdown':

   %users  localhost=/sbin/shutdown -h now

Permite a todos os usuários listados no alias 'ADMINS' executem comandos como superusuários sem a necessidade de senhas.

   ADMINS    ALL=(ALL)    NOPASSWD: ALL

Permite as usuários listados no alias 'ADM' executarem os comandos listados em 'STORAGE' nos host de 'FILESERVERS' sem a necessidade de senhas:

   ADM   FILESERVERS=NOPASSWD: STORAGE

Permite ao usuário 'ricardo.brito' executar os comandos kill e iptables na máquina 10.1.1.1, entretanto o comando iptables ele pode executar sem senha:

   ricardo.brito    10.1.1.1 = NOPASSWD:/bin/iptables , PASSWD: /bin/kill

Permite ao usuário 'ricardo.brito' executar o comando 'passwd' para modificar a senha dos usuários nos servidores de email 'MAILSERVERS', exceto a senha do root:

   ricardo.brito           MAILSERVERS = /usr/bin/passwd [A-z]*, !/usr/bin/passwd root

Proíbe ao usuário 'john' executar o comando 'su -', 'su - root' ou 'su root' na máquina 'penta':

   john        penta = /usr/bin/su [!-]*, !/usr/bin/su *root*

Para qualquer máquina no Host_Alias SERVERS o usuário jill pode executar qualquer comando do diretórios /usr/bin/ exceto os comandos descritos nos Cmnd_Aliases 'SU' e 'SHELLS':

   jill           SERVERS = /usr/bin/, !SU, !SHELLS

No host www, qualquer usuário do User_Alias WEBMASTERS, pode qualquer comando como usuário (www) ou apenas o 'su www'.

WEBMASTERS     www = (www) ALL, (root) /usr/bin/su www

Os usuários do grupo de rede secretaries podem gerenciar as impressoras bem como adicionar e remover usuários em todos os hosts.

+secretaries   ALL = PRINTING, /usr/bin/adduser, /usr/bin/rmuser

O usuário 'jen' pode executar qualquer comando, exceto nos servidores do Host_Alias SERVERS:

jen            ALL, !SERVERS = ALL

# O usuários do grupo 'users' podem executar os comandos 'STORAGE' nos hosts 'FILESERVERS':

%users FILESERVERS=STORAGE 

segunda-feira, 22 de outubro de 2012

Oracle Fusion Middleware 11g – Repository Creation Utility (RCU)


fusion rcu
This post covers overview of Repository Creation Utility(RCU) which is first thing you need to do, if you are planning to implement/install Oracle Fusion Middleware 11g R1 (11.1.1.0).
Metadata Repository - contains metadata for Fusion Middleware Components (SOA, Webcenter, Identity Management) . There are various types of Repository – Metadata Services (MDS), Audit Services (IAU), Oracle Internet Directory (OID), Single Sign-On (SSO), SOA Infrastructure (SOAINFRA), Business Activity Monitoring (BAM) , User Messaging (ORASDPM) , Oracle WebCenter (WEBCENTER) , WebCenter Portlets (PORTLETS) , Oracle Content Server (OCSERVER) , Portal (PORTAL), Discoverer (DISCOVERER), Oracle Identity Federation (OIF) , Discussions (DISCUSSIONS) and Wiki and Blog (WIKI)
Repository could be Database-based or File-based, most component (Webcenter, SOA, OID…) requires Database-based Repository.
.
How to create Database-based repository ?
RCU 
- Repository Creation Utility is tool to create schema and load repository in existing database for Fusion Middleware components.
Download RCU from here
.
Key points for Repository Creation Utility (RCU) in FMW
1. RCU can be run in two mode – GUI (Graphical User Interface) & CLI (Command LineInterface)

2. 
For Fusion Middleware 11g R1 (11.1.1.X) , RCU can only load schema in Oracle Database (version 10.2.0.4 and higher or 11.1.0.7 and higher)

3. 
You can run RCU locally (same machine where Database is running) or Remotely(Database is on remote machine)

4. 
By default RCU creates default schema and load repository in default tablespaces. RCU provides flexibility to change schema or tablespace name. (Only exception to this is Oracle Internet Directory (OID) schema)
5. You could load multiple repository (like Portal, webcenter, SOAINFRA) in single database. You could also load different version of same repository (like dev_soainfra, test_soainfra for DEV & Test instance resp.) in same database. (This is interesting feature for using single database for multiple Fusion Middleware Instances)
6. You can start RCU (Repository Creation Utility) from $RCU_SOFTWARE/bin/ rcu(for Unix) or rcu.bat (for Windows) ; This will start RCU in GUI mode. For CLI mode use “rcu [-silent | -interactive] {<command> <options>}
7. RCU log file is written to the RCU_SOFTWARE_DIR/ rcu/ log/ logdir.<date_timestamp>/ rcu.log
8.For step by step Fusion Middleware Repository Creation Utility with screen-shotsclick here
.


sexta-feira, 5 de outubro de 2012

GLASSFISH erro e correção

[root@shimizu config]# /opt/glassfish/bin/asadmin
Oct 5, 2012 5:42:05 PM com.sun.enterprise.util.ASenvPropertyReader setSystemProperties
SEVERE: property_reader.unknownHost
java.net.UnknownHostException: shimizu: shimizu
        at java.net.InetAddress.getLocalHost(InetAddress.java:1360)
        at com.sun.enterprise.util.net.NetUtils.getCanonicalHostName(NetUtils.java:102)
        at com.sun.enterprise.util.ASenvPropertyReader.setSystemProperties(ASenvPropertyReader.java:201)
        at com.sun.enterprise.cli.commands.S1ASCommand.<init>(S1ASCommand.java:165)
        at com.sun.enterprise.cli.commands.MultiProcessCommand.<init>(MultiProcessCommand.java:76)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
        at java.lang.Class.newInstance0(Class.java:355)
        at java.lang.Class.newInstance(Class.java:308)
        at com.sun.enterprise.cli.framework.CommandFactory.createCommand(CommandFactory.java:91)
        at com.sun.enterprise.cli.framework.CLIMain.invokeCommand(CLIMain.java:160)
        at com.sun.enterprise.cli.framework.CLIMain.main(CLIMain.java:79)
Use "exit" to exit and "help" for online help.


no hosts não constava o hostname 

cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6


depois de adicionado o hostname
[root@shimizu config]# cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4 shimizu
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

terça-feira, 2 de outubro de 2012

Um pouco de Linux RH 6

Trabalhando com repositórios oficiais.

Habilitando e desabilitando o repositório.

4.13.3.2. Enabling Supplementary and Optional Repositories

As systems are subscribed to products, the associated content repositories (identified in the entitlement certificate) are made available to the system. The content repositories are based on the product and on the content delivery network, defined in the baseurl parameter of the rhsm.conf file.
A subscription may include access to optional content channels along with the default channels. These optional channels must be enabled before the packages in them can be installed (even if the system is fully entitled to the products in those channels).
  1. List all available repos for the system, including disabled repos.
    [root@server ~]# yum repolist all
    repo id                      repo name                           status
    rhel-6-server                Red Hat Enterprise Linux 6Server -  enabled
    rhel-6-server-beta           Red Hat Enterprise Linux 6Server Be enabled
    rhel-6-server-optional-rpms  Red Hat Enterprise Linux 6Server Op disabled
    rhel-6-server-supplementary  Red Hat Enterprise Linux 6Server Su disabled
    The optional and supplementary channels are named rhel-6-server-optional-rpms and rhel-6-server-supplementary, respectively.
  2. The repositories can be enabled using the yum-config-manager command:
    [root@server ~]# yum-config-manager --enable rhel-6-server-optional-rpms
Alternatively, simply specify the optional or supplementary repository when installing a package with yum. This uses the --enablerepo repo_name option. For example:
# yum install rubygems --enablerepo=rhel-6-server-optional-rpms
Loaded plugins: product-id, refresh-packagekit, subscription-manager
Updating Red Hat repositories.
....
Using yum is described in Chapter 5, Yum.

4.13.3.3. Disabling the Subscription Manager Repository

When a system is registered using Subscription Manager, the rhsmcertd process creates a special yum repository — redhat.repo. As Section 4.13.3.2, “Enabling Supplementary and Optional Repositories” describes, as the system adds subscriptions, the product channels are added to the redhat.repo file.
Maintaining a redhat.repo file may not be desirable in some environments. It can create static in content management operations if that repository is not the one actually used for subscriptions, such as for a disconnected system or a system using a local content mirror.
This default redhat.repo repository can be disabled by editing the Subscription Manager configuration and setting the manage_repos value to zero (0).
[root@server1 ~]# subscription-manager config --rhsm.manage_repos=0
 
 
 
Maiores informações: https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/entitlements-and-yum.html 

quinta-feira, 21 de junho de 2012

IUm passo a passo bacana de instalação do oracle application server 10gR2


Oracle Application Server 10g R2 – Installation

Introduction
Oracle Application server 10g is a middle ware software by Oracle. Purpose of Application server is to handle the business intelligent and logic. Below is the difference between a two-tier architecture and multi-tier architecture.

In case of a two-tier architecture we business logic and presentation is both handled by client. Hence we call it thick client. Where as in case of multi tier architecture we have only presentation layer in client side and business logic is handled by Application server. Hence such clients are called as think client. Below is the three tier architecture show.

Advantages of 3-tier architecure
1) In case of change in business logic the change needs to be done only in Application server (mid tier) as its centralized. Where as in case of two tier architecture ever client needs to be changed. So management is easy.
2) It reduces the network traffic, because in case of 2 tier architecture the protocol used is TCP/IP which is a stateful connection (continuous). So even if data is been send or not connection will always be there. This increases network traffic and reduces bandwidth. Where as in 3 tier architecture we have TCP/IP connection only between mid tier and database and is set when client request for some data. As soon as data is provided the connection is closed. The connection between client and mid tier is http which is a stateless connection.
3) Performance is another factor which make 3 tier architecture a better solution over 2 tier architecture. Since all business logic gets executed at client side, performance on client reduces. This is in addition to database performance issue. In case of 3 tier architecture performance is not an issue and is handled well in Application server.
Lets start with Application server 10g
Application Server 10g Components
Below is a very simple line sketch of application server 10g component architecture. This shows what are the components that are present in AS (Application Server) and why those are required.

All the above components shown above comes with AS 10g R2 installation. All these components are categorized as given below.
All the components shown in green color + OHS for mid tier (on left) + Web cache is installed as mid tier components. So mid tier includes
  1. Web Cache
  2. OHS (Oracle HTTP Server)
  3. OC4J
  4. FORMS
  5. REPORTS
  6. DISCOVERER
  7. PORTAL
  8. WIRELESS
While installing this middle tier, the installation of these components are divided into 3 main components.
  1. J2EE and Web Cache (This will install Web Cache, OHS and OC4J)
  2. Portal and Wireless (This will install all components of J2EE and Web Cache + Portal and Wireless components)
  3. Business Intelligence and Forms (This will install all components)
If we are installing just option 1 (J2EE and Web Cache) then infrastructure tier is not required. However we can still install infrastructure tier but in this case it wont be used by these 3 components of mid tier.
If we are installing either option 2 or 3, we have to install infrastructure tier before installing these mid tier components. This is because these middle tier component such as portal and wireless will create there own repository in infrastructure’s meta data repository. So its important that we first install infrastructure tier before installing mid tier, in case we want to go for option 2 or 3 for mid tier.
The other components shown in blue + OHS on right side are installed as infrastructure tier. So infrastructure tier includes following components
  1. OHS (Oracle HTTP Server)
  2. Meta Data Repository
  3. SSO (Single Sign on)
  4. OID (Oracle Internet Directory)
  5. DAS (Delegate Administrative Services)
  6. OCA (Oracle Certification Authority)
Out of the above components of infrastructure tier SSO, OID, DAS and OCA are together called as IDM (Identity Management). So infrastructure tier contains mainly meta data repository and identity management.
Having this brief knowledge above AS 10g R2 components, lets start with installation.
Installing Oracle Application server 10g R2
Before starting the installation, we should complete the pre-installation checks. This includes following steps.
Pre-Installation Task
1) Check the required packages are installed in OS or not.
glibc-2.3.4-2.9
glibc-common-2.3.4-2.9
binutils-2.15.92.0.2-13
compat-libstdc++-296-2.96-132.7.2
gcc-3.4.3-22.1
gcc-c++-3.4.3-22.1
libstdc++-3.4.3-22.1
libstdc++-devel-3.4.3-22.1
openmotif21-2.1.30-11.RHEL4.4
pdksh-5.2.14-30
setarch-1.6-1
make-3.80-5
gnome-libs-1.4.1.2.90-44.1
sysstat-5.0.5-1
compat-db-4.1.25-9
control-center-2.8.0-12
xscreensaver-4.18-5.rhel4.2

you can check the status of package using rpm -q command. as a root user.
2) Add following in /etc/sysctl.conf

kernel.shmall = 2097152
kernel.shmmax = 2147483648
kernel.shmmni = 4096
# semaphores: semmsl, semmns, semopm, semmni
kernel.sem = 256 32000 100 142
fs.file-max = 131072
net.ipv4.ip_local_port_range = 10000 65000
kernel.msgmni = 2878
kernel.msgmax = 8192
kernel.msgmnb = 65535

3) Make entry of hostname and domain name in /etc/sysctl.conf
kernel.hostname=advait
kernel.domainname=oracle.com

4) Make following changes in /etc/security/limits.conf
*        soft   nproc         2047
*        hard   nproc         16384
*        soft   nofile        2048
*        hard   nofile        65536

5) Add the following line to the /etc/pam.d/login file
session    required     /lib/security/pam_limits.so
6)  Make the following entry in /etc/profile
if [ $USER = "oracle" ]; then
if [ $SHELL = "/bin/ksh" ]; then
ulimit -p 16384
ulimit -n 65536
else
ulimit -u 16384 -n 65536
fi
fi

7)  Create a group and user.
Primary Group – oinstall
/usr/sbin/groupadd oinstall
Secondary Group
/usr/sbin/groupadd dba
/usr/sbin/useradd -g oinstall -G dba -md /home/oracle oracle
Give the password
[root@dhcp-hydcampusp1-10-176-107-101 home]# passwd oracle
Changing password for user oracle.
New UNIX password:
BAD PASSWORD: it is based on a dictionary word
Retype new UNIX password:
passwd: all authentication tokens updated successfully.

8) Make changes in /etc/hosts as root user and make following entry.
(IP Address)       (hostname.domain.name)       (hostname)
Example
10.176.106.101      advait.oracle.com       advait
Installing Infrastructure Tier
The installation of AS10g should be done in specific order only as explained before. This is because of the dependencies between the components. Here we are going to install Portal and Wireless option of mid tier, this needs database repository for storing the information of these components. So we will first install infrastructure tier and then install Mid tier. Please follow the below screen shots.
run the runInstaller executable present in your Disk1 directory of software dump.

Screen 1 : Welcome – This is the welcome screen. Click on Next.

Screen 2: Specify Inventory location – In this case you can take the default inventory location and then it will ask to run orainstRoot.sh script as root user. Once you run this script as root user on that host, click on continue.

Click on Next

Screen 3: Specify File Locations – Specify the location of Oracle Home for Infra tier and click next.

Screen 4: Select the product to Install – In this case select “Oracle Infrastructure 10g”. If you choose “Oracle Application Server 10g”, then it will install infra tier first and then automatically start installing mid tier.

Screen 5: Select Installation type – As I said before infra tier consists of mainly IDM (Identity Management) and metadata repository. IDM consists of OID, SSO, DAS and OCA. Meta data repository is a 10g oracle database. We will choose both to install here.

Screen 6: runInstaller will perform the basic check on operating system. If for any of the check it generates warning, you can verify the same using the check box and then click on next.

Screen 7: Pre-Installation Requirement – You should have root privileges as you need to run root.sh after installation. Select the checkbox and click on next.

Screen 8: Select Configuration Option – You can select individual components which we are going to install.

Screen 9: Port Configuration Option – For Port Configuration, select Automatic port selection to keep installation simple. Else you can specify the ports in staticports.ini file and upload the same.

Screen 10: Namespace in Internet Directory - Select the default name space only. If your /etc/hosts name file is correct then the default port will be populated correctly. Else it may get populated as localhosts also. In that case check the entry in /etc/hosts.

Screen 11: OCA Distinguish Name – You can specify only the mandatory fields. This is required for creating digital certificate for SSL configuration.

Screen 12: OCA Key length - This is the key length to be used for encryption. You can select the default 2048 and click on next.

Screen 13: OCA Administrator Password - This is the password for Oracle Certificate Authority admin. Select any password, confirm the same and click on next.

Screen 14: Database Configuration Options – Here we provide the name of the database. You can accept the default orcl or give any new name.

Screen 15: Database Schema Password - Select any password for database schema, confirm the same and click on next.

Screen 16: Instance Name and ias_admin Password - Here we are creating a new instance. Note that this is different then database instance. So for infrastructure tier you can give any name (example infra) and also password you want to use for enterprise manager.

Screen 17: Installation Summary - At the end it will show installation summary. Click on Install.

It will show the installation progress. Remember that it is just copying the files and will do some setup. The actual component configuration will come next.

Installer has now started with component configuration. It will configure each component one by one.

When it comes to Meta Data Repository, it will create a new database using DBCA.

At the end of installation it will show the URLs and ports. The above URL is the URL for EM of Infra. Remember we will have 2 EM (Enterprise Manager), one for infra and one for mid-tier.
With the completion of infra tier, we can now start with installation of mid tier. But note that during installation of mid tier your infrastructure tier should be up and running.
Installing Mid Tier components
run the same runInstaller executable present in your Disk1 directory of software dump which you used during infra tier installation.

Screen 1 : Welcome – This is the welcome screen. Click on Next.

Screen 2: Specify File Locations – Specify the location of Oracle Home for mid tier and click next.

Screen 3: Select Product to install - If you remember for infra tier installation we selected second option, i.e. “Oracle Application Server Infrastructure 10g”. Here we have to install mid-tier, which will be present inside “Oracle Application Server 10g” option. So select “Oracle Application Server 10g” option.

Screen 4: Select Installation Type - Here you can select the required installation type depending on the components you want to install. For this installation we will go for Portal and Wireless.

Screen 5: runInstaller will perform the basic check on operating system. If for any of the check it generates warning, you can verify the same using the check box and then click on next.

Screen 6: Pre-Installation Requirement – You should have root privileges as you need to run root.sh after installation. Select the checkbox and click on next.

Screen 7: Select Configuration Option – You can select individual components which we are going to install.

Screen 8: Port Configuration Option – For Port Configuration, select Automatic port selection to keep installation simple. Else you can specify the ports in staticports.ini file and upload the same.

Screen 9: Register with OID – Here you need to provide the hostname and port number of OID which you have already installed as a part of infra tier. By default the port number is 389. You can also check the port numbers of infra tier by going to ORACLE_HOME/install directory and checking file portlist.ini. Here ORACLE_HOME refers to infra ORACLE_HOME.

Screen 10: OID Login - Here OID superuser login should be given. by default its always orcladmin. You have to give the password for this user. This password will be set for orcladmin. You can give any password.

Screen 11: Select AS10g Meta Data Repository - This will show the name of database that we created as meta data repository as a part of infra installation.

Screen 12: Specify Instance Name - Here you will specify the name of the instance that needs to be created for mid tier and also the admin password for logging into EM (Enterprise Manager).

Screen 13: Summary - At the end it will show summary. Click on install.

You can see the progress of installation. After this initial copy and setup, it will start configuring each components one by one as shown below.

Progress of each component.

At the end it will give the URL for enterprise manager and port details. You can access enterprise manager to manage Application server.
I don’t want to extend this post more now. This completes the installation. More details will be provided in next posts. Thanks.
Hope this helps !!
References:
Oracle Application Server 10g R2 Installation guide
http://avdeo.com/2008/04/15/oracle-application-server-10g-r2-installation/

sexta-feira, 8 de junho de 2012

Alguns erros ODI

ODI

Alguns erros que me ocuparam muito tempo.

=================================================================================================
ODI 10G
Conexão URL JDBC para a conexão com um banco de dados ORACLE RAC:
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp)(HOST=[HOSTNAME1])(PORT=[PORT]))(ADDRESS=(PROTOCOL=tcp)(HOST=[HOSTNAME2])(PORT=[PORT])))(CONNECT_DATA=(SERVICE_NAME=[NOME_DO_SERVIÇO])))

Observação importante: O parâmetro LOAD_BALANCE e FAILOVER é sempre YES ou NO, não pode ser ON ou OFF, se for ON ou OFF dará o seguinte erro:


7000 : null : com.sunopsis.sql.l: Oracle Data Integrator Timeout: connection with URL jdbc:oracle:oci:@(DESCRIPTION=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=TCP)(HOST=[HOSTNAME1])(PORT=[PORTA]))(ADDRESS=(PROTOCOL=TCP)(HOST=[HOSTNAME2])(PORT=[PORTA]))(CONNECT_DATA=(SERVICE_NAME=[NOME_DO_SERVIÇO]))) and user Usuário
com.sunopsis.sql.l: Oracle Data Integrator Timeout: connection with URL jdbc:oracle:oci:@(DESCRIPTION=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=TCP)(HOST=[HOSTNAME1])(PORT=[PORTA]))(ADDRESS=(PROTOCOL=TCP)(HOST=[HOSTNAME2])(PORT=[PORTA]))(CONNECT_DATA=(SERVICE_NAME=[NOME_DO_SERVIÇO]))) and user Usuário.
    at com.sunopsis.sql.SnpsConnection.a(SnpsConnection.java)
    at com.sunopsis.sql.SnpsConnection.t(SnpsConnection.java)
    at com.sunopsis.sql.SnpsConnection.connect(SnpsConnection.java)
    at com.sunopsis.sql.SnpsQuery.updateExecStatement(SnpsQuery.java)
    at com.sunopsis.sql.SnpsQuery.executeUpdate(SnpsQuery.java)
    at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execStdOrders(SnpSessTaskSql.java)
    at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
    at com.sunopsis.dwg.dbobj.SnpSessTaskSqlC.treatTaskTrt(SnpSessTaskSqlC.java)
    at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
    at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
    at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
    at com.sunopsis.dwg.cmd.DwgCommandScenario.treatCommand(DwgCommandScenario.java)
    at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
    at com.sunopsis.dwg.cmd.e.i(e.java)
    at com.sunopsis.dwg.cmd.h.y(h.java)
    at com.sunopsis.dwg.cmd.e.run(e.java)
    at java.lang.Thread.run(Thread.java:534)

=================================================================================================
ODI 10G

Erro: 17002 : null : java.sql.SQLException: Io exception: Connection Timed Out - ocorria depois de 60 min de conexão

Ambiente em seguimento de rede diferentes que tinha dois firewalls no caminho. Em um deles estavam sem o timeout de conexão configurado, o outro estava configurado com o timeout em 60 min. Após alterar o timeout para 24 horas o ambiente começou a processar normalmente.

Espero ter ajudado.

Abs

Eric Shimizu

Primeiro Post

Primeiro Post

Vamos lá... Primeiro post no meu Blog, neste blog irei adicionar os erros que acabam dando no dia a dia.. com a resolução adotada.
Entre eles terá problema/resolução relacionado a minha especialidade que é middleware, então escreverei sobre, IIS, Apache, Tomcat, Glassfish, WebSphere, Oracle Application Server, ODI, entre outros que for interessante para compartilhar informações.