Steps to Deploy the OFSAA application in WEBLOGIC server:

- 
Steps to Deploy the OFSAA application in WEBLOGIC server:
=========================================================

1) Generate the "context_name.ear" from the FIC_WEB area by executing the ./ant.sh
2) Create a folder by the name "applications" within the domain directory
3) Create a folder by the name "context_name.ear" within the newly created "applications" folder
4) Copy the context_name.ear file from the FIC_WEB folder to the newly create the "context_name.ear" folder created within the applciations folder
5) Explode the .ear file copied from the FIC_WEB area (jar -xvf context_name.ear), There are 2 files and 1 directory created after the .ear file is exploded as mentioned below
 a) context_name.war ---> file
 b) context_name.ear ---> file
 c) META_INF      ---> folder
6) Delete the above files (.ear and .war files) 
7) Create a new folder by the name "context_name.war"
8) Copy the context_name.war file from the FIC_WEB area into the newly created "context_name.war" folder
9) Explode the context_name.war file (jar -xvf context_name.war)
10) Folder and files which are same as in the FIC_WEB area are created on exploding

log into the weblogic console
=============================

1) create data sources for atomic and config schemas
2) Make sure the REVELEUS server is up before the deployment is started in the WEBLOGIC
3) Before deploying, increase the memory for the webserver. Navigate to domain/bin and modify the below mentioned properties in the file setDomainEnv.sh 
  WLS_MEM_ARGS_64BIT="-Xms512m -Xmx512m"
  export WLS_MEM_ARGS_64BIT

  WLS_MEM_ARGS_32BIT="-Xms512m -Xmx512m"
  export WLS_MEM_ARGS_32BIT 
4) From the Deployments int he console, deploy the context_name.ear
5) once the deployment is complete, restart both APP and WEB servers and login to OFSAA

Comments

Post a Comment

Popular posts from this blog

Steps for OFSAA ALM cash flow generation

-
Please find the steps below for the OFSAA ALM cashflow generation. -------------------------------------------------------------------------------------------------------------- 0. OBJECT REGISTRATION 1. Create Product Hierarchy in front end.--- DIM_PRODUCTS_B 2. Create COA hierarchy in the front end. -- dim_common_coa_b 3. Map product members to COAs 4. Create one Legal Entity in the Front end. 5. Execute "Reverse Population" -- DT name : REVERSE_POPULATION 6. Create one Active Time bucket. 7. Populate DIM_DATE : Execute function "" in the back end with start date and end date. 8. Populate FSI_D_LOAN contracts 9. Create one product characteristic in ALM 10. Create one ALM Static Deterministic process for Loan data. 11. Execute from ALM Process. 12. Use the below queries for cashflow data. select /* + PARALLEL(16)*/ a.as_of_date, a.account_number, a.amrt_type_cd, a.int_type, a.origination_date, a.last_reprice_date, a.next_reprice_date, a.ma
Read more

Client / Server Applications

-
What is: The client–server characteristic describes the relationship of cooperating programs in an application. The server component provides a function or service to one or many clients, which initiate requests for such services. Advantages: * In most cases, a client–server architecture enables the roles and responsibilities of a computing system to be distributed among several independent computers that are known to each other only through a network. This creates an additional advantage to this architecture: greater ease of maintenance. For example, it is possible to replace, repair, upgrade, or even relocate a server while its clients remain both unaware and unaffected by that change. * All data is stored on the servers, which generally have far greater security controls than most clients. Servers can better control access and resources, to guarantee that only those clients with the appropriate permissions may access and change data. * Since data storage is centralized, update
Read more