As mentioned in earlier posts our Metasolv installation is clustered so we will do ASR installation in clustered environment.
Pre Installation checklist
Metasolv 6.2.x is installed.
below paths are set as per your directory structure.
PATH= BEA_Home/jdk_version/bin $PATH
BEA_HOME=/opt/app/mss_home/bea(installation directory of Oracle Weblogic 10.3 server)
JAVA_HOME=/opt/app/mss_home/bea/jdk_version
Installation of ASR
STEP 1.
From Metasolv installation directory mss_home run the following command.
java -jar Asr.releaseNo.buildNo_M62.jar
for version 53 it should be java -jar Asr.R53_0_0.b23_M62.jar
STEP 2.
The above java command will ask to choose Metasolv Home directory, a directory asr53installer(asr+version+installer) will be created in the selected directory.
It will automatically invoke setup.sh/setup.cmd in mss_home/asr53installer directory.
STEP 3.
Click Next.
STEP 4.
Enter the path and name of the MetaSolv Home directory, MetaSolv Domain directory, and MetaSolv Server directory or click Open to search for the directories.
STEP 5.
Click Next.
STEP 6.
Select any one of the following installation types:
- Install all ASR Files
- Install Only ASR EAR File
For a clustered environment, you can choose an option to extract the .EAR file only
For a non-clustered environment, choose the option to install and deploy all files.
STEP 7.
Click Next.
STEP 8.
Click Finish.
STEP 9.
For a clustered environment.
- Locate the loggingconfig_cluster-ASR53.xml file located in the mss_home/managedserver/appserver/config directory, where managedserver is the WebLogic managed server.
<appender name="XMLFileAppASR53" class="org.apache.log4j.RollingFileAppender">
<param name="ImmediateFlush" value="true"/>
<param name="append" value="true"/>
<param name="MaxFileSize" value="10000KB"/>
<param name="MaxBackupIndex" value="10"/>
<param name="File" value="${mslv.log.dir}/appserverlog_ASR53.xml"/>
<layout class="com.metasolv.common.framework.logging.api.log4jext.xml.MSLVXMLLayout">
</layout>
</appender>
<appender name="AuditFileAppASR53" class="org.apache.log4j.RollingFileAppender">
<param name="ImmediateFlush" value="true"/>
<param name="append" value="true"/>
<param name="MaxFileSize" value="10000KB"/>
<param name="MaxBackupIndex" value="10"/>
<param name="File" value="${mslv.log.dir}/appserver_auditlog_ASR53.xml"/>
<layout class="com.metasolv.common.framework.logging.api.log4jext.xml.MSLVXMLLayout">
</layout>
</appender>
Add the following snippet in category element for ASR 53.
<category name="cmm.ASR" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLogger" additivity="false">
<level value ="error" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLevel"/>
<appender-ref ref="XMLFileAppASR53"/>
</category>
<category name="ASR" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLogger" additivity="false">
<level value ="debug" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLevel"/>
<appender-ref ref="XMLFileAppASR53"/>
</category>
<category name="cmm.SecurityASR" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLogger" additivity="false">
<level value ="debug" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLevel"/>
<appender-ref ref="AuditFileAppASR53"/>
</category>
<level value ="error" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLevel"/>
<appender-ref ref="XMLFileAppASR53"/>
</category>
<category name="ASR" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLogger" additivity="false">
<level value ="debug" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLevel"/>
<appender-ref ref="XMLFileAppASR53"/>
</category>
<category name="cmm.SecurityASR" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLogger" additivity="false">
<level value ="debug" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLevel"/>
<appender-ref ref="AuditFileAppASR53"/>
</category>
2. Rename the file to loggingconfig_cluster-ASR53.xml.
STEP 10.
RUN the ASR installation in each managed server instance.
STEP 11.
Restart managed servers.
STEP 12.
RUN prodfixsql/procs sqls.
- Run pfixSQL_Master.sql file located in the mss_Home/server/appserver/sql/ASR53/prodfixsql. This sql will call rest of sql files located in same directory.
- Run the asr_master.sql file located in the mss_Home/server/appserver/sql/ASR53/procs directory that was created during the installation to apply the contents of the ASR procs directory to the database.
STEP 13.
- Undeploy existing ASRversion.ear from application servers
- Deploy ASRnewVersion.ear(cluster-ASR53.ear for clustered env) on application servers from admin console.
“log4j: ERROR Attempted to append to closed appender named [XMLFileApp”
STEP 14.
Modify the gateway.ini , add below entry.
ASR53SERVER=MetaSolv.CORBA.WDIASR53.WDIROOT,MetaSolv.WDIASR53.WDIRootImpl
comment out similar entry for earlier version by placing a semi-colon in front of the entry.
;ASR52SERVER=MetaSolv.CORBA.WDIASR52.WDIROOT,MetaSolv.WDIASR52.WDIRootImpl
I hope this will help installing ASR newer upcoming versions, I will also try to post further the post ASR installation customization (e.g. generate java files from new IDL ASR files) for ASR new versions, please leave your feedback or query.