Andreas' Adventures

http://localhost:7200/oc4j-service?cmd=Getprocs Show the processes http://localhost:7200/oc4j-service?cmd=p Show the status

Recently I was busy with the mod_oc4j clustering of two standalone OHS machines. As Oracle has integrated ONS into OC4J in 10.1.3.x you have to provide your own ons.conf file (just copy one from a 10.1.2.0.2 environment). But what happend to me was strange. I added a new node (machine_C.mydomain.local) while I removed another one (machine_A.mydomain.local). However getting the opmnctl status @farm still showed the machine_A in the list. Some investigation delivered the following: In the directory $ORACLE_HOME\opmn\logs\states two entries do exist: .opmndat p12345678 When you shutdown the OPMN the p* file will disappear. However the .opmndat file will remain there. Remove it, it will be rebuild with the next opmnctl startall. Now my machine_A.mydomain.local was gone and the machine_C showed up. cu Andreas

In another posting I described how to edit the system-jazn-data.xml in order to create a user. To my astonishment there seems to be a possibility to create these users using the Application Server Control. Here are the steps: In the ASC cluster topology click on the OC4J that contains the javasso. Click on Applications Select javasso Click on the module javasso-web Click on Security provider Select Realms In the realm jazn.com click on the number in the users column. In this screen you can create users!

Trying to fix the problems I encountered earlier I found out that the removal of the OID security provider is performed by the following steps. During the setup where OID is created as a security provider the ssoreg.sh is run on the OID layer. Remove this with the web-based ORASSO (http://host:port/pls/orasso). But the second step involved the usage of the new osso_newsite.conf file. This is done with the $ORACLE_AS10131_HOME/Apache/Apache/bin/osso1013 . Just comment out the entries in the httpd.conf and the mod_osso.conf, create a new empty_osso.conf in $OH/Apache/Apache/conf/osso/ and rerun the osso1013. This did the trick for me. cu Andreas

This seems to be a very difficult task. Here is my setup on a VMWare instance (RH 4.3): AS 10.1.2.0.2 Infrastructure with OID AS 10.1.3.1 SOA Suite AS 10.1.3.2 Webcenter Now I want to use the OID as the security provider for the SOA Suite. First I register the SOA Suite as a "remote_midtier" in the SSO. Then I go to the AS Control of the SOA Suite and configure the Identity Management for the two OC4J's - home and oc4j_soa. This does only work for the OC4J called home. The OC4J oc4j_soa does not get changed. Then after some restarts the whole system decides to just stop with using any of the two security providers (file-based JAZN and OID). Therefore I cannot login to the AS Control. After several attempts to fix this I parked this problem. This will probably be a reinstall :-( Any ideas are welcome. cu Andreas

A little gem I found in the Oracle Metalink Notes: Steps to enable OC4J logging: a- Each OC4J instance has a separate logging configuration file: $ORACLE_HOME/10.1.3/j2ee/ /config/j2ee-logging.xml b- By default the log level is set to something like: c- You can set level to the desired value as using following syntax: : Message type: INTERNAL_ERROR, ERROR, WARNING, NOTIFICATION & TRACE Message level: 1-32 (1 most severe, 32 least) d- Each OC4J instance has file: $ORACLE_HOME/10.1.3/j2ee/ /application-deployments/ /orion-application.xml Which contains tag like: to specify the log file name. e- Each OC4J has its own log file in the following path: - Plain Text Log: $LOG_HOME/ora/10.1.3/j2ee/ / _ /application.log - ODL Log: $LOG_HOME/ora/10.1.3/j2ee/ / _ /log.xml