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