Back-Up FileStore of a JMS Weblogic Configuration

Main reasons you could be benefits of doing this, are a backup, delete, compress or replace .dat file.

• Shutdown servers, cluster, nodeManager  or coherence (cluster or server) who is occupied the JMS Configuration.

• Having access as a root or weblogic user, you  should execute the following script  shell:

1. setWLSEnv.sh: Located on  /opt/weblogic/XXXX/wlserver_10.3/server/bin or wherever is installed weblogic, maybe /root/Oracle/wlserver_10.3/server/bin is another possible location.
2. wlst.sh: Located on  /opt/weblogic/XXXX/wlserver_10.3/common/bin or wherever is installed weblogic, maybe /root/Oracle/wlserver_10.3/common/bin is another possible location.

• Now, what we have just done?, well setWLSEnv.sh configure on your enviroment several jar  that are part of the neccesary running to calling method or classes for doing changes in weblogic without a web console, at the last one is a script which is necessary for doing python/ironpython o command execution,

• After running wlst.sh, you will have a prompt just like this:  wls:/offline> with the weblogic password, user and ip/port the possibilites are unlimted to whatever your imagination could do.

1. Execute: 

wls:/offline> compactstore('<LOCATION_FILESTOREORIGINAL>','<LOCATION_COPYONFAIL>')

•  Depends on your dat size is the time that you will be waiting, may I say that for a 5 files amout of 2GB takes me about 1 hour, please waiting after the execution is complete.

1. In your LOCATION_FILESTOREORIGINAL(ex:/root/jms/filestore) you must a found a compressend file, in my case the size reduce about a 20% per file. 
2. In your LOCATION_COPYONFAIL(ex:/root/jms/backup), you must found the original file with the same size of the original file.

Now, what we have in mind?, perhaps you could limite the size of  your persistence store in the way that you could make a backup for auditing process as I said this could be benifit for each part of development.

Best regards,

Clase en Auditoria en Informática, Actividad Webinar

Como parte de la actividad Seleccion de Webinar para discusion en equipo de contenido de auditoria, hacemos una pequena sintesis de lo realizado en la actividad.

Guide to Auditing and Logging in the Oracle E Business Suite

Nombre del Equipo: Zeus

• Francisco Goicochea Romero
• Carlos Eduardo Vega Castillo
• David Eduardo Magaña
• Sanchez Huerta Octavio

Descripcion:

Oracle publica sus herramientas y su conjuncion con estandares de auditoria en Informática un punto son las rutinas que posee cada una de sus tecnologias para hacer un reporte de analisis de auditoria un ejemplo de ello es oracle database addm los cuales miden el uso de la base de datos de acuerdo a queriea optimizados, Oracle Service Bus tambien posee pistas de auditoria con caulquier tipo de adaptador en el mercado un ejemplo importe es la intercomunicacion con SAP sus herramientas tienen nodos que pueden interconectarse con transaciones que pueden ser monitoreadas.

Enlance del webinar:

Proveedor: Oracle

How to resolve "Object has been closed" driver exception on Oracle Weblogic?

Oracle Weblogic provide a list of jdbc driver which you could connect with another database different of Oracle Database Grid Link, If you chose a configuration of a simple datasource you will get a error like this on your log file:


Caused by: java.sql.SQLException: [FMWGEN][SQLServer JDBC Driver]Object has been closed.
    at weblogic.jdbc.sqlserverbase.ddb_.b(Unknown Source)
    at weblogic.jdbc.sqlserverbase.ddb_.a(Unknown Source)
    at weblogic.jdbc.sqlserverbase.ddb9.b(Unknown Source)
    at weblogic.jdbc.sqlserverbase.ddb9.a(Unknown Source)
    at weblogic.jdbc.sqlserverbase.BaseConnection.getTransactionIsolation(Unknown Source)
    at weblogic.jdbc.wrapper.PoolConnection_weblogic_jdbc_sqlserverbase_ddah.getTransactionIsolation(Unknown Source)
    at org.springframework.jdbc.datasource.DataSourceUtils.prepareConnectionForTransaction(DataSourceUtils.java:190)


After a quick look inside of the log file I figure out that is Memory Problem of OracleWeblogic so I imagine that driver should be changed by an updated driver made it by a the original vendor in this case we are talking of Microsoft SqlServer 2008 R2, if you following a changing configuration of a driver inside of a weblogic you might get an idea of you was. After a successful artifact update and depending of application I get an error like this:

Reached maximum capacity of pool

So after a shameful explanation of what in the hell I was doing with a Database Connection with my leaders the decision was taken, increase capacity connection inside of oracle weblogic, in future releases I will fix my problem with shared configuration using weblogic.xml and probably using a SqlAdapter created with Oracle Service Bus.

 Best regards,