LAKSHMI WEBLOGIC/SOA ADMIN

Linux performance related commands top - to check cpu and memory usage top - 03:32:44 up 1 day, 23:09,  6 users,  load average: 0.00, 0.05, 0.32 Tasks: 157 total,   1 running, 156 sleeping,   0 stopped,   0 zombie Cpu(s):  1.1%us,  0.3%sy,  0.0%ni, 97.7%id,  0.8%wa,  0.0%hi,  0.1%si,  0.0%st Mem:   1011508k total,  1001500k used,    10008k free,     3528k buffers Swap:  2097148k total,   333960k used,  1763188k free,    69648k cached   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND    10 root      20   0     0    0    0 S  3.7  0.0   0:19.80 rcu_sched 13415 oracle    20   0 1286m 293m 4116 S  1.8 29.7   0:29.02 java     1 root      20   0 19408  376 ...

Import and Export users from Embedded LDAP using WLST: Export connect(‘weblogic’,’weblogic’, ‘t3://localhost:8003′) domainRuntime() cd(‘/DomainServices/DomainRuntimeService/DomainConfiguration/DomainA/SecurityConfiguration/DomainA/DefaultRealm/myrealm/AuthenticationProviders/DefaultAuthenticator’) cmo.exportData(‘DefaultAtn’,’c:/export.ldif’, Properties()) Import connect(‘weblogic’,’weblogic’, ‘t3://localhost:8003′) domainRuntime() cd(‘/DomainServices/DomainRuntimeService/DomainConfiguration/DomainB/SecurityConfiguration/DomainB/DefaultRealm/myrealm/AuthenticationProviders/DefaultAuthenticator’) cmo.importData(‘DefaultAtn’,’c:/export.ldif’, Properties()) Example as follows: To export security data to a file: In the left pane, select Security Realms and then select the realm whose security data you want to export (for example, myrealm). Expand Migration > Export. In the Export Directory on Server field, specify the directory on the Admin...

connect(‘weblogic’,’weblogic’,’t3://localhost:7001′) edit() startEdit(-1,-1,’false’) serverConfig() cd(‘/SecurityConfiguration/First_Domain/Realms/myrealm/AuthenticationProviders/DefaultAuthenticator’) cmo.createUser(‘faisal’,’weblogic’,”) cmo.groupExists(‘TestGrp’) cmo.createGroup(‘TestGrp’,”) cmo.addMemberToGroup(‘testgrp’,’faisal’) cd(‘/SecurityConfiguration/First_Domain/Realms/myrealm/RoleMappers/XACMLRoleMapper’) cmo.setRoleExpression(”,’Admin’,’Grp(TestGrp)|Grp(Administrators)’) edit() undo(defaultAnswer=’y’, unactivatedChanges=’true’) stopEdit(‘y’)

Creating JDBC DataSources in WebLogic Server using WLST (WebLogic Scripting Tool),including authentication, connection pool configuration, and deployment targets. Prerequisites: WebLogic Server installed JDBC driver JAR available (e.g.,  ojdbc8.jar  for Oracle) Admin credentials and server URL Basic WLST DataSource Creation Script: Save as  create_datasource.py : # Connect to Admin Server connect('weblogic', 'welcome1', 't3://localhost:7001 edit() startEdit() # Create JDBC DataSource cd('/') cmo.createJDBCSystemResource('MyDS') cd('/JDBCSystemResources/MyDS/JDBCResource/MyDS') cmo.setName('MyDS') # JDBC DataSource Parameters cd('/JDBCSystemResources/MyDS/JDBCResource/MyDS/JDBCDataSourceParams/MyDS') cmo.setJNDINames(['jdbc/MyDS'])  # JNDI Name cmo.setGlobalTransactionsProtocol('TwoPhaseCommit')  # For XA transactions #JDBC Driver Properties cd('/JDBCSystemResources/MyDS/JDBCResource/MyDS/JDBCDriverParams/My...

Disabling your Admin Console: We can disable our weblogic admin console in two different ways 1)Admin console 2)Weblogic Scripting Tool From Admin console:- To disable access to the Administration Console: After you log in to admin console click Lock & Edit. In the left pane of the Console, under Domain Structure, select the domain name. Select Configuration > General, and click Advanced at the bottom of the page. Deselect Console Enabled. Click Save. To activate these changes, click Activate Changes. From WLST:- connect(“weblogic“,”weblogic“,”t3://localhost:7001“) edit() startEdit() cmo.setConsoleEnabled(false) save() activate() disconnect() exit() Enabling the Admin Console: After we disable the admin console we can enable it again by using WLST. Following are the steps on the same: connect(“weblogic“,”weblogic“,”t3://localhost:7001“) edit() startEdit() cmo.setConsoleEnabled(true) save() activate() disconnect() exit() Note: Here, 1...

Oracle MDS (Metadata Services)  questions into  realistic admin/developer scenarios —with answers tailored to reflect actual usage and problem-solving. 🔍 Scenario 1: “Why is the shared XSD not updating across composites?” Interviewer Framing : You deployed an updated XSD file into MDS, but the composites that depend on it still use the old version. What’s going wrong? What They're Testing : Your understanding of versioning, MDS cache, and deployment lifecycle. Answer Strategy : MDS artifacts are cached both on the server and at design time. After updating MDS, the dependent composites  must be redeployed  or refreshed in JDeveloper. In some cases, the SOA server may need to be restarted or its cache cleared. 🧠  Extra Tip : Use  ant  scripts or WLST to automate MDS uploads and maintain consistency across environments. 🧰 Scenario 2: “Where exactly does MDS live?” Interviewer Reframe : Can you explain the two types of MDS repositories and when to use ...

Oracle Weblogic Server: How to Change Oracle Weblogic Server User Password Using WLST 1. Setting environment variable     a. go to directory $WLS_HOME/wlserver_10.3/server/bin     b. source file setWLSEnv.sh  as command: . setWLSEnv.sh . 2. Create a domain which name is test1032, 3. Weblogic admin user name is weblogic, password is weblogic1. 4. Create test user, which name is test and password is weblogic1. Instruction $java weblogic.WLST changepw.py <Domain Name> <Admin URI> <Admin user> <Admin password> <user name> <user password> <Domain Name> : the domain name which need to change user password. e.g. test1032 <Admin URI>   : weblogic server adminstration URL, e.g. t3://localhost:7001 <Admin user>  : weblogic admin user, e.g. weblogic <Admin password> : admin user password, e.g. weblogic1 <user name>      : the user who need to change password. e.g. tes...