Showing posts with label Weblogic. Show all posts
Showing posts with label Weblogic. Show all posts

Monday, August 13, 2018

Migrate an Enterprise Capture Workspace


This can be accomplished by using the WLST commands "exportWorkspace" on the source Enterprise Capture system and "importWorkspace" on the target Enterprise Capture system.

The exact steps are :

1) Run the wlst command (.sh for Linux, .cmd for Windows) from the Middleware home /common/bin directory:

  wlst.sh

2) Connect to the Capture managed server:

    wls:/offline> connect("weblogic","welcome1","t3://localhost:16400")

3) Retrieve Workspace ID, which is passed to the export command.  To get a list of current workspaces and their IDs:

    wls:/content/serverConfig>listWorkspaces()

The list will look like the following:

         8 wkspace1

         6 fred-wk2

         7 test-capture1

4) Run the export command:

    wls:/content/serverConfig>exportWorkspace(8,'/home/isyed/wkspace1.xml')

5) Import the workspace to the same instance (only if you deleted the workspace since exporting) or a different Capture instance:

   wls:/content/serverConfig>importWorkspace('/home/isyed/wkspace1.xml')


Saturday, July 7, 2018

Disable 8dot3


Disable 8dot3 naming, what is requested during UCM install procedure, by running "Installer DisableNtfs8dot3" and then restarting windows. This procedure can be run after UCM installation is done.

Run: DomainHome\ucm\cs\bin\Installer.exe DisableNtfs8dot3
Page 153: http://download.oracle.com/docs/cd/E17904_01/doc.1111/e14495.pdf

If that still leaves 8dot3 naming enabled, modify registry:
1. Start/Run/regedit
2. In the left pane of the window navigate to [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
3. In the right pane of the window, edit the DWORD "NtfsDisable8dot3NameCreation" and set its value to 1 (The default value is 2)
4. Reboot the system

Wednesday, February 17, 2016

Big Performance Mistake - Java Application Development.

1. The framework sample that you use, keep close eye on on following:

a. Every library included in project.
b. Every xml created that's load on runtime.
c. Every default code generate by tool

all above items will decrease a chances of bad performance for application.

Review a debug logs and try to resolve any unknown error and exception that caused but not disturbing application process but it might overloading JVM or database and other related applications / connections.

You might not able to feel any performance issue on development / test server because application is running with sample data / limit number of records and users.

2. Not every architect makes a good decisions:-

Custom measuring for example:-
a. Was impacted by garbage collection
                b. just measured overall time but not # SQL Exceptions

DON'T ASSUME you know what code does somebody else developed

3. Use performance test tools dynatrace, New Relic, AppDynamics, HP Load Runner.

4. Idenfity how many sql exection in your code also number of same sql statement executed in your code.
a. Optimize the sql statement or cache data
b Connection equitation time

5. Identify how many number of threads are created and utilized by application and number of call made to API's and time take by each in API.

6. Bad Deployments
a. Different framework / library version between development and production server.
b. Perform Unit Test, Functional Test, Performance Test before deployment

7. Push without a plan ( Idea was great but implementation wasn't correct)
a. Need to check number of images on each page that might cause application slowness.
b. Number of redirection and size of resources are used in each page.
c. Use diagnostics tools to make sure overloading won't happen.






Monday, February 15, 2016

Error while domain creation - Weblogic



Preparing...
Extracting Domain Contents...
Creating Domain Security Information...
Domain Creation Failed!

Domain Location: C:\Oracle\Middleware\user_projects\domains\custom_domain

Reason: null

Exception:

Traceback (innermost last):
  File "<iostream>", line 155, in ?
  File "<iostream>", line 53, in writeUcmAutoInstallFile
  File "C:\Oracle\Middleware\wlserver_10.3\common\wlst\modules\jython-modules.jar\Lib/javaos$py.class", line 334, in system
  File "C:\Oracle\Middleware\wlserver_10.3\common\wlst\modules\jython-modules.jar\Lib/popen2.py", line 235, in system
  File "C:\Oracle\Middleware\wlserver_10.3\common\wlst\modules\jython-modules.jar\Lib/popen2.py", line 72, in __init__
  File "C:\Oracle\Middleware\wlserver_10.3\common\wlst\modules\jython-modules.jar\Lib/javashell.py", line 64, in execute
OSError: (0, 'Failed to execute command ([\'sh\', \'-c\', \'chmod 755 C:\\\\Oracle\\\\Middleware\\\\user_projects\\\\domains\\\\hassad/ucm/cs/bin/autoinstall.cfg\']): java.io.IOException: Cannot run program "sh": CreateProcess error=2, The system cannot find the file specified')


Solution:

To solve this we need to patch the jython-modules.jar. For default JDeveloper installation path we need to go to C:\Oracle\Middleware\wlserver_10.3\common\wlst\modules and extract the jython-modules.jar using a utility like 7-zip. Then we need to open the javashell.py python script inside lib folder and add at line 139 a String for Windows 8 OS:

_osTypeMap = (
        ( "nt", ( 'nt', 'Windows NT', 'Windows NT 4.0', 'WindowsNT',
                  'Windows 2000', 'Windows 2003', 'Windows XP', 'Windows CE',
                  'Windows Vista', 'Windows Server 2008', 'Windows 7', 'Windows 8' )),
        ( "dos", ( 'dos', 'Windows 95', 'Windows 98', 'Windows ME' )),
        ( "mac", ( 'mac', 'MacOS', 'Darwin' )),
        ( "None", ( 'None', )),
        )



Remove Domain from Weblogic Server


As of now there is no out of the box feature with Weblogic Configuration wizard to remove or delete a domain.

These are basically manual steps.
For example if I want to delete a domain named geo_domain below are the steps you need to remove the domain.

1. Open domain-registry.xml under $Middleware_HOME .Remove the corresponding entry referring to geo_domain.
CodeSnippet :: domain-registry.xml
<?xml version="1.0" encoding="UTF-8"?>
<domain-registry xmlns="http://xmlns.oracle.com/weblogic/domain-registry">
<domain location="C:\Oracle\Middleware\user_projects\domains\soa_domain"/>
<domain location="C:\Oracle\Middleware\user_projects\domains\geo_domain"/>
</domain-registry>

2. Open nodemanager.domains file under $Middleware_HOME \wlserver_10.3\common\nodemanager\ folder. Remove the corresponding entry referring to geo_domain.
CodeSnippet :: nodemanager.domains
#Domains and directories created by Configuration Wizard
geo_domain=C\:\\Oracle\\Middleware\\user_projects\\domains\\geo_domain

3. Delete the domain folder under domains folder manually.
        $Middleware_HOME\user_projects\domains\geo_domain

4. Delete the domain folder under applications folder manually.
        $Middleware_HOME\user_projects\ applications\geo_domain

Installing the NodeManager service


1.    Open the Command Prompt
2.    Run %WL_HOME%\wlserver_10.3\server\bin\setWLSEnv.cmd to set Weblogic Environment variables like WL_HOME, JAVA_HOME, PATH, CLASSPATH etc.
3.    Edit the installNodeMgrSvc.cmd to bind to a hostname for remote starts 
set NODEMGR_HOST=localhost
4.    Now run the %WL_HOME%\wlserver_10.3\server\bin\installNodeMgrSvc.cmd Validate the service from the services list as well using the services.msc utility.


5.    Start the NodeManager service named as above “Oracle WebLogic NodeManager…”
6.    Make sure starting the NodeManager service should create a  nodemanager.properties file under %WL_HOME%\wlserver_10.3\common\nodemanager.

Setup NodeManager to restore servers to their last known state after a reboot

1.   
Open nodemanager.properties located at %WL_HOME%\wlserver_10.3\common\nodemanager
2.    Set CrashRecoveryEnabled property value to true CrashRecoveryEnabled=true 
3.    Set StartScriptEnabled property value to true to invoke the startWeblogic script StartScriptEnabled=true
4.    Set StopScriptEnabled property value to true to invoke the stopWeblogic script and get the managed servers to shutdown cleanly StopScriptEnabled=false
5.    Set ListenAddress property value ListenAddress=localhost
6.    Set SecureListener property value (In case you selected plan for as communication type) SecureListener=false
7.    Restart of NodeManager service for each change to this nodemanager.properties file



Setup the machine

1.    Login to the AdminServer console

2.    Navigate through Domain Structure to %DOMAIN_NAME% -> Environment -> Machines

3.    Create a new machine Name : localhost, OS : Other - as my operating system is Windows Node Manager - Type: Plan

4.    Create one machine for each instance of OS for a different host.

5.    Assign the ManagedServer to machines based on which machine the ManagedServer is hosted. Take Lock & Edit and navigate through %DOMAIN_NAME% -> Environment -> Machines -> %MACHINE_NAME% -> Configuration tab -> Servers tab

6.    Do not forget to save and Activate the changes.

Enrolling the domain with NodeManager      

1.    Open command prompt

2.    Run %DOMAIN_HOME%\bin\setDomainEnv.cmd to set domain specific environment variables

3.    Start WLST using java weblogic.WLST

4.    At WLS prompt connect to AdminServer using connect ('weblogic','weblogic','t3://localhost:7001')

5.    Run nmEnroll(domainDir='C:/oracle/Middleware/user_projects/domains/base_domain',nmHome='C:/oracle/Middleware/common/nodemanager'). Make sure that you use forward slashes "/" instead of backward "\" as WLST does not recognize forward slashes. If you use backward slashes "\" you get the following error.



6.    Once the domain is successfully enrolled with NodeManager the nodemanager.domains should be updated too with below values.

#Thu Apr 28 11:54:41 MDT 2014
            base_domain=C\:\\Oracle\\Middleware\\user_projects\\domains\\base_domain 
            Also NodeManager should be reachable in AdminServer console. To validate this,

a)    Login to AdminServer console

b)   Navigate through %DOMAIN_NAME% -> Environment -> Machines -> %MACHINE_NAME% -> Monitoring -> Node Manager Status it should be Reachable (If not please check the nodemanager.log in  C:\Oracle\Middleware\wlserver_10.3\common\nodemanager)
               


Server Startup Configuration

1.    Login to the AdminServer console
2.    Navigate through Domain Structure to %DOMAIN_NAME% -> Environment -> Servers -> ManagedServer_1 -> Configuration tab -> Server Start tab
3.    Take Lock & Edit and input values as appropriate.
Java Home - C:\oracle\Middleware\jdk160_14_R27.6.5-32
Java Vendor - Sun - As I am using Sun JDK 
Weblogic Home - C:\oracle\Middleware
Root Directory -C:\oracle\Middleware\user_projects\domains\base_domain 
Classpath - Can be left blank as we have configured the nodemanager.properties to use startWeblogic script in  Setup nodeManager to restore servers to their last known state after a reboot  step 3 and you can setup necessary values in that script.
Arguments - Can be left blank as we have configured the nodemanager.properties to use startWeblogic script in  Setup NodeManager to restore servers to their last known state after a reboot  step 3 and you can setup necessary values in that script. But i am using memory arguments as input here "-Xms64m -Xmx128m" 
Security Policy - File - C:\oracle\Middleware\wlserver_10.3\server\lib\weblogic.policy
User Name – weblogic
Password – weblogic
Confirm Password – weblogic
4.    Save and activate the changes
5.    Repeat steps 1-4 for each ManagedServer in the domain.



NodeManager Domain Username and password

1.    Login to the AdminServer console

2.    Click on Domain name in the Domain Structure and navigate through %DOMAIN_NAME% (cs_domain) -> Security tab -> General tab -> Advanced link

3.    Take Lock & Edit  and input the NodeManager username/password/confirm passwords fields and these could be unique from your weblogic console password. I have chosen to input same as my console credentials username: weblogic & password: weblogic. This setup would help user who use WLST to connect to NodeManager via nmConnect()

4.    Save and Activate the changes


Complete Setup

Finally the setup is complete and now its time to start your ManagedServer in Admin console using NodeManager.
Starting the ManagedServer using the NodeManager setup
1.    Login to the AdminServer console
2.    Navigate through Domain Structure to %DOMAIN_NAME% -> Environment -> Servers -> ManagedServer_1 -> Control tab -> Start/Stop tab
3.    Under the Server Status section select the ManagedServer and click on start button
4.    When prompted to confirm the Action to be performed, click yes button.
5.    Monitor the server logs and after a while the server should be in RUNNING state


Weblogic ServletContext.getRealPath() - NullPointerException

Setting weblogic Admin Console option

Domain | Web Application | Archived Real Path Enabled to

You can also apply fix in application level by adding the following entry to weblogic.xml file:

<container-descriptor>
    <show-archived-real-path-enabled>true</show-archived-real-path-enabled>
</container-descriptor>

Monday, August 17, 2015

How to Remove Domain From weblogic



As of now there is no out of the box feature with Weblogic Configuration wizard to remove or delete a domain. These are basically manual steps.

For example if I want to delete a domain named geo_domain below are the steps you need to remove the domain.

Open domain-registry.xml under $Middleware_HOME .Remove the corresponding entry referring to geo_domain.

CodeSnippet :: domain-registry.xml
<?xml version="1.0" encoding="UTF-8"?>
<domain-registry xmlns="http://xmlns.oracle.com/weblogic/domain-registry">
<domain location="C:\Oracle\Middleware\user_projects\domains\soa_domain"/>
<domain location="C:\Oracle\Middleware\user_projects\domains\geo_domain"/>
</domain-registry>

Open nodemanager.domains file under $Middleware_HOME \wlserver_10.3\common\nodemanager\ folder.
Remove the corresponding entry referring to geo_domain.
CodeSnippet :: nodemanager.domains
#Domains and directories created by Configuration Wizard
geo_domain=C\:\\Oracle\\Middleware\\user_projects\\domains\\geo_domain

Delete the domain folder under domains folder manually.
$Middleware_HOME\user_projects\domains\geo_domain


AWS EC2 - SSH locked with UFW

Need to update the instance's user data: 1. Stop the instance 2. Right click (windows) or ctrl + click (Mac) on the instance to open a c...