Oracle Weblogic 12C with forms and reports
make sure /tmp is at least 2GB
you would also need Java Developers Kit (JDK)
check for X windows, if xauth do not work with direct putty, you can try with MobaXterm
Also you need xming (X server for windows) for windows x display streaming to your system from remote server
For display settings, once you get in with the restricted user, list the display settings
techsmachine01:techs [/home/userdir/nw09gy] xauth list $DISPLAY
techsmachine01/unix:11 MIT-MAGIC-COOKIE-1 9e5c40068e60717487a9d8ca145e6abd
Note- sometime its worth using xhost + after above steps
If you still get errors cant open display, then clear all the auth sessions
with the command -uxauth list | cut -f1 -d\ | xargs -i xauth remove {}
and repeat the steps again
techsmachine01:techs [/home/userdir/nw09gy] sx su - techs
Password:
techs: [/home/techs]> xauth add techsmachine01/unix:11 MIT-MAGIC-COOKIE-1 9e5c40068e60717487a9d8ca145e6abd
Now test the X-Windows functionality
techs: [/home/techs]> xclock
Error: Can't open display: localhost:11.0
this error came because on client side i.e. my laptop, xwindows client like XMing is not running
I started the XMing and all is ok now
techs: [/home/techs]> xclock
this will display the clock on your laptop/desktop
check for prerequisites:
oel6-prerequisitechecks
yum install libXext.i686 -y
yum install libXtst.i686 -y
yum install openmotif -y
yum install openmotif22 -y
# OL7 Only
yum install ocfs2-tools -y
yum install motif -y
yum install motif-devel -y
yum install numactl -y
yum install numactl-devel -y
Make sure DB user with DBA privilleges is available to create required schemas and tablespaces
Make sure Database is configured to use AL32UTF8 charatcter set
Now place the required software on your server:
This is the list of software with JDK package:
fmw_12.2.1.2.0_infrastructure.jar jdk-8u144-linux-x64.tar.gz V789399-01_forms.zip
fmw_12.2.1.2.0_wls.jar V779119-01_wls_server.zip V789399-01_reports.zip
fmw_12212_readme_wl_server.htm V779119-01_wls_with_coherence.zip V834474-01_wls_plugins.zip
forinfrastructure_readme V779122-01_Infrastructure.zip
Download the required software from Oracle website.
For Oracle Weblogic 12C with Forms and Reports Installation, following steps with softwares are required:
1. Install FMW binaries (fmw_12.2.1.0.0_infrastructure.jar) steps given below:
Run infrastructure jar file with absolute path to jdk
pathtojdk/jdk1.8.0_144/bin/java -jar fmw_12.2.1.0.0_infrastructure.jar
On the Welcome page …click next
Skip auto update….Next
Now provide Middleware home path and click next:
check the provided details (keep Fusion Middleware Infrastructure selected) and click next:
On this page, java version error can be ignored:
on next click Skip email notification part
you can save response file and click install
Now you should see installation progress:
First step is complete i.e. Infrastructure binaries are installed.
2. Now we need to install the forms and reports softwrare (no need to install domain at this stage)
./fmw_12.2.1.0.0_fr_linux64.bin
3. Once forms and reports are installed, next step is to run the RCU
cd $ORACLE_HOME/oracle_common/bin
./rcu
You needs to have a database user with sysdba privilleges
On step 3 of RCU, provide hostname(DB SERVER) port: 1521, Service name (db service defined e.g. techapp)
user name and password for DB user
Role: Select SYSDBA and not the normal user role
Once RCU is completed successfully, next step is to create the domain.
4. For domain setup go into cd $ORACLE_HOME/oracle_common/common/bin
./config.sh
Click Here for Domain Setup Reference
Note: For forms and Reports, Oracle WSM Policy manager is not required and do not select this as a component on Page 2 of Fusion Middleware Configuration Wizard - Page 2 of 12 (This require a MDS schema and will create issues)
rest fill in the details and complete the setup.
Installing Infrastructure…
===============TIPS and Tricks on Weblogic, forms and reports 12C with OHS===========================
changing the wrong machine name to correct one
you need to change the name from config.xml file, make sure you take a backup of the file before making the changes.
once changes are done, stop the environment and start again.
Note: This change broke the environment completely with following errors:
errors
—-OHS Installation once forms and reports are installed—-
Register OHs for the first time
wls:/offline> connect('weblogic', 'nodemanpassword', 'localhost:7001')
Connecting to t3://localhost:7001 with userid weblogic ...
Successfully connected to Admin Server "AdminServer" that belongs to domain "techs_domain".
Warning: An insecure protocol was used to connect to the server.
To ensure on-the-wire security, the SSL port or Admin port should be used instead.
wls:/techs_domain/serverConfig/> ohs_updateInstances()
Location changed to edit custom tree. This is a writable tree with No root.
For more help, use help('editCustom')
Starting an edit session ...
Started edit session, be sure to save and activate your changes once you are done.
Saving all your changes ...
Saved all your changes successfully.
Activating all your changes, this may take a while ...
The edit lock associated with this edit session is released once the activation is completed.
Activation completed
OHS instances have been updated successfully.
wls:/techs_domain/serverConfig/>
start node manager
then connect to wlst.sh
nmConnect('weblogic','Welcome123', 'localhost', '5556', 'domainname', '/techs/Middleware/user_projects/domains/domainname')
start ohs - nmStart(serverName='ohs1', serverType='OHS')
stop ohs - nmKill(serverName='ohs1', serverType='OHS')
setup ohs instance
modify the httpd conf file
stop start the ohs
Errors while restarting the ohs—
wls:/nm/techsdomains> nmKill(serverName=’ohs1′, serverType=’OHS’) Killing server ohs1 …
Traceback (innermost last):
File “<console>”, line 1, in ?
File “<iostream>”, line 150, in nmKill
File “<iostream>”, line 553, in raiseWLSTException
WLSTException: Error occurred while performing nmKill : Error killing server ohs1 : Receivedhs1′ is not currently running]. Please check Node Manager log for details.
Use dumpStack() to view the full stacktrace :
wls:/nm/techsdomains> nmStart(serverName=’ohs1′, serverType=’OHS’) Starting server ohs1 …
Successfully started server ohs1 …
wls:/nm/techsdomains> nmConnect(‘weblogic’,’Welcome123′, ‘localhost’, ‘5556’, ‘domainnames/techsdomains’)
——————————————————————–
make sure exe are mapped in the setFormsEnv.sh and other important env files
ccc_output must me configured on apache configuration
place already working SA ords into the middleware home dir and then create i.war deploy both to the new MN
create the locations for both /i/ and ords in the httpd.conf file and restart the apache (both run time and deve mode)
—————————————————————————
Reports setup on new installed OFR
—————————————————————————-
wlst reports installation —> add weblogic to admin group —> disable reports security —-> make sure app.env has COMPONENT_CONFIG_PATH environment variable set to ->
DOMAIN_HOME should be replaced with the literal directory structure.
NOTE:reports managed server should be in stop state when you start instance configuration
sh /apphome/techs/products/Middleware/oracle_common/common/bin/wlst.sh
wls:/offline> connect('weblogic','password4yourweblogicuser','t3://servername:7001')
Connecting to t3://servername:7001 with userid weblogic ...
Successfully connected to Admin Server "AdminServer" that belongs to domain "yourdomain_domain".
Warning: An insecure protocol was used to connect to the server.
To ensure on-the-wire security, the SSL port or Admin port should be used instead.
wls:/yourdomain/serverConfig/> createReportsToolsInstance(instanceName='reptools1',machine='servername')
Location changed to edit custom tree. This is a writable tree with No root.
For more help, use help('editCustom')
Starting an edit session ...
Started edit session, be sure to save and activate your changes once you are done.
Saving all your changes ...
Saved all your changes successfully.
Activating all your changes, this may take a while ...
The edit lock associated with this edit session is released once the activation is completed.
Activation completed
Reports Tools instance "reptools1" was successfully created.
wls:/yourdomain/serverConfig/>
enable web commands to check and test the reports
Oracle document id to refer- Doc ID 2072876.1
add RW_ADMINISTRATOR role to user (for example, weblogic)
goto WeblogicDomain...security.....Application Roles....select reports from Application Stripe....click search....select RW_ADMINISTRATOR.....Edit
Now click on Add under Members.... on Add Principal Dialog....select User from Type........click Search........Select weblogic....press ok
---------
and then press ok again
you will get an display - Information An application role RW_ADMINISTRATOR has been updated.
Now restart the reports server
REP-51002: Bind to Reports Server rep_wls_reports_servervm03 failed.
check the report server status - https://app-url/reports/rwservlet/getserverinfo?
check report server name info from configuration file - $DOMAIN_HOME/config/fmwconfig/servers/WLS_REPORTS/applications/reports_12.2.1/configuration/rwservlet.properties
check and find the reports server - ./rwdiag.sh -findall
call report directly - https://appurl/reports/rwservlet?report=/tmp/report12340r.rep&destype=cache&desformat=pdf&userid=db_user/password123@dbname
Make sure to add following line in the env file (default.env) of your application
COMPONENT_CONFIG_PATH=$DOMAIN_HOME/config/fmwconfig/components/ReportsToolsComponent/
——————————————————————–
To Disable security for the Reports Server 12c follow step as.
Start the report server before doing below steps: –
1. Log in to Oracle Enterprise Manager.
2. Navigate to the EM MBean browser Weblogic Domain > System MBean Browser
3. Navigate to reports server mbean
Standalone server – Folder: Configuration Beans –> Folder:oracle.reports.serverconfig –> type=ReportsServer, name=rwserver-
Inprocess server – Folder: Application Defined MBeans –> Folder:oracle.reportsApp.config –> Server:
4. Click child mbean ReportsServerJob.
5. Change SecurityId of rwEngrwJaznSec from rwJaznSec to empty.
* Note:
In Standalone server the SecurityID is gray out and can’t modify.
Need to click [Lock & Edit] -> [Change SecurityId of rwEngrwJaznSec from rwJaznSec to empty] -> Click [Apply] -> Click [Activete Changes] (* Inprocess server don’t need this step)
After changing the SecurityId value of rwEngrwJaznSec to “empty” the bean name of rwEngrwJaznSec will become rwEngnull.
6. Restart WLS_REPORTS or Reports Server.
——————————————————————–
PRoduction Mode installation:
Stopping Derby server...
Derby server stopped.
create a security directory and then boot.properties file inside it
register ohs for the first time
script_dir=/techsapps/oracleapps/bin
##sh ${MIDDLEWARE_HOME}/oracle_common/common/bin/wlst.sh
#Change to the scripts directory
. $WLS_HOME/server/bin/setWLSEnv.sh
java weblogic.WLST $script_dir/scripts/start_ohs.py
sleep 2
start the wlst
sh ${MIDDLEWARE_HOME}/oracle_common/common/bin/wlst.sh
connect to the weblogic
connect(‘weblogic’, ‘password5$$’, ‘hostname:7001’)