Yup. It work’s. Thanks.

Thanks

We checked the space in the database and it was without problems, what we did was to restart the opc application, thank you very much

Hi,

Email alert’s default sender value is “[email protected]”.

You can edit sender(from) as below.

Regards.

1.Go to “Configuration > WLSDM System Settings” in WLSDM menu.
menu.jpg

2.Be sure you are in “mail.account” tab then edit “mail.account.smtp.username” property.
sender.jpg

Set property value in modal window then save.
111111.jpg

Hi,

You can select any range by using date field. But the maximum backward range is the WLSDM monitoring start time.

Kind regards.

Hi,

WLSDM log viewer line limit is 1000 but you can search any string and find searched string where line is located in whole log file via “text filter”.

There is another way to view log files via WLSDM file explorer. Go to “Operational Tools & Utils -> File Explorer” pick “.log” file then click view button (max 1 mb view size). Also you can download log file to your local environment via file explorer.

Kind Regards…

Log viewer text filter:
1.png

File Explorer:
2.png

Hi,

The WLSDM and the WL-OPC have their own data-archive mechanism.

For the WLSDM, default data archive range is 90 days, and for the WL-OPC, default data archive range is 365 days.

You can find the settings below.

Kind regards.

WLSDM: Configuration > WLSDM System Settings > system.archive
77.jpg

WL-OPC: Administration > System Settings > Notification
88.jpg

Hi,

Non-adminstrator users not allowed for administrative operations by default as below screenshots.

Metric configuration for monitor user:
2..png

Metric configuration for adminstrator user:

3..png

File explorer for monitor user:

4..png

You can change access restriction configuration in “WLSDM System Settings > system.authorization” page.

Default value is OFF in “system.authorization.page.access.fileexplorer.allgroups” feature. It means only administrators can access to “file explorer”. If you turn on this feature, you must set access path for non-adminstrator users then non-adminstrator users only can access the path(s).

You can restrict log viewer access configuration via “system.authorization.page.access.logviewer”. Default value is on, it means all users can access log viewer, if you turn off this feature, non-adminstrator users will not able to access logviewer.
56.jpg

Hi,
On the other hand, Make sure you have not applied wlsdm_agent JVM arguments to the AdminServer?
If you send the whole details and logs we would like to help you to alter this problem. We have never seen this error before. It looks like this is something relevant to this environment. Have you tried the installation on another domain environment?
Regards…

Hi Jeba,

If you want to see File/Socket events you should increase your WLDF Diagnostic volume on WebLogic

Go to “Servers > $ManageServerName > General (tab)” page and set “Diagnostic Volume” high. Then you are able to see file read/write events.

Note: This option means additional overhead on your managedservers; just activate only one managedserver which file read/write monitoring is important.

Regards.

diagnostics.png

No; this property is usefull when OPC is down. You had better enable it. Disabling that property will NOT disable for all domains.

You can still configure notification settings on WLSDM part; like ON/OFF backend notifications… etc.

The configuration is still same; all the functionalities on WLSDM are still supported by OPC. If you have a specific case; then please let us know in detail to reproduce it.

Regards…

Thanks…

Hi,

This timeout value is a precaution to protect the system.

That’s why we can’t let the increase the timeout value by users.

If you need a long-running process; you can trigger your WLST script using a shell command.

That will cause an immediate return for the main process (Shell Script) but not for the child process (Triggered WLST Script).

Also, this type of usage means; The script is out of the control to WLSDM.

Kind regards.

Hi,

You can’t call the stored WLST scripts from the scheduler module.

And you need a shell script (custom action) to run an external WLST script from the scheduler module.

Kind regards.

@bibarrav

Hi Bibarrav,

WLSDM doesn’t support the feature you ask.

But you can complete the installation quickly using the wizard.

– How many domain installation planning you are exactly?

Kind Regards…

@bibarrav

Hi,

Probably it is a WebLogic issue. If it is a “Devlopment Mode” WebLogic domain; you should not see the “Change Center” in WebLogic console. But, in your sceen capture “WebLogic Change Center” is available (attached below). We are recommending to setup your WebLogic domain from scratch as Development mode domain.

Regards…

image.png

Thanks,

The point 1 resolved it. OHS was being used here. Using the listen port helped to resolve the issue.

Regards,

Thanks a lot !

It is working fine now after removing the boot.properties file.

Regards,

Hi,

We have another product named WL-OPC for systems that have many domains and these requests can be made in there.Otherwise, you can define many rules as you want in WL-OPC.

Even there is no need for email, when you using WL-OPC console, you can monitor every notification from all domains in one operation center. More information http://www.wlsdm.com/wl-opc/index

Regards.

Hi,

Are you sure you have created HTTP transactions for the relevant managed server? Remember you need to create real traffic to exceed 8kb buffer size for the response times monitoring. So, at least there must be +100 request after managed server restart.

Are you sure you have selected the right managed server on the “Response Times” page? (Please take below screen capture as a reference)

2..jpg

Go to “Configuration > Monitoring & Diagnostics > Response Times (tab)” page and check the status. Is there any server needs to be restarted?
3..jpg

Kind Regards…

Please try registering the domain by using the “overwrite” and retry delete domain.

ow.jpg

Hi,

It looks like a WLSDM DB issue.

This is might be happening because you do not have enough disk space on the machine.

Please check your disk for enough space.

After that please restart the (only) AdminServer.

Kind regards.

Hi,

Unfortunately, we are not supporting “bash 3.2” version. At least you have to use “bash 4.x version”. Adding compatible bash version as below.

Here are our recommendations:

Our recommended OS is Linux. (centOS, Red Hat… etc.). You had better choose Linux servers. This information is already available in the help at the “prerequisite” section.

Upgrade your bash version to 4.1 at your current working Solaris server.

Kind Regards…

Hi,

This is a cache issue.

As a workaround: Please restart your WebLogic AdminServer to apply your new license.

Hi,

This is an “Internet Explorer” issue (also, previous issue too).

Please prefer the Chrome or the Firefox as browser while we fix the problem in next WL-OPC release.

Kind Regards…

Hi,

This script is endless; you should echo a result for capturing a variable in WLSDM.

You should use the ping command like i.e. “ping $servername –c 1” then extract output from the ping command.

We are recommending you to use the script which is available in WLSDM README for pinging database. Please follow the readme link here: http://www.wlsdm.com/docs/README#VI.ConsoleUsage&DevOpsMBean

Also we are pasting below.

Step-1 Write Shell Script: Ping database and calculate database response time using WebLogic API (weblogic.jar)

#Variables _dbStatus=0 #0:DB_DOWN,1:DB_UP #start DB Ping _startTime=$(($(date +%s%N)/1000000)) _pingResult=`java -cp weblogic.jar utils.dbping ORACLE_THIN $YOUR_USER_NAME $YOUR_PASSWORD $YOUR_IP:$YOUR_PORT/$YOUR_SERVICE_NAME` _endTime=$(($(date +%s%N)/1000000)) _dbResponseTime=`expr $_endTime - $_startTime` if [[ "$_pingResult" == *"Success!!!"* ]]; then _dbStatus=1 #echo "Database connection SUCCESS!!!" #DB_UP echo DatabaseStatus=$_dbStatus else _dbStatus=0 #echo "Database connection FAILURE!!!" #DB_DOWN echo DatabaseStatus=$_dbStatus fi echo DatabaseResponseTime=$_dbResponseTime```

Hi Jeba,

First of all your WLSDM version is not the latest; please upgrade to v3.4.1 (it will took about 5 min). Please do a fresh installation. This domain was open for all the metrics about “STORE DATA” feature. That’s why you faced this issue.

Let us analyze more. Is this thread is in ManagedServer or AdminServer? We need below information to help you.

Could please at least take 3 thread dump for AdminServer and ManagedServer then send us to us? (thread dump: kill -3, or from WLSDM console) Could you please zip all WLSDM log files and send to us? (Available at WLSDM\logs folder) Could you please runt this command and share the output with us? cd $DOMAIN_HOME{WLSDM_RUNTIME_FOLDER}
du -sh * Could you please share the WLSDM version?

We are suspecting about data archive. As a workaround please DISABLE all your (make OFF) data archive settings. Go to “System Settings > system.archive (tab)” page and OFF all archive settings if they are currently ON. Then restart only AdminServer then observe the new states about high CPU consumption.

Kind Regards…

@whching said:

Hi @wlsdmsupport

I am just start looking at WLSDM, what is the difference of having one agent per cluster against one agent per managed server?

BTW, where I could find the resource overhead when WLSDM is used on managed servers? say, how much more heap memory it will use and how about any extra I/O it would introduced?
Thanks

Regards,
Rock

Hi,

If you have two member cluster and these members are on different machine then install two agent. If you have 4(four) member cluster and these members on two machine (two managed server per machine). Then install two agent (same with previous). Much agent, much traffic. Same behavior, same machine… Then go for one agent.

More information is available on README: http://www.wlsdm.com/docs/README#IV.Installation

WLSDM runs on AdminServer and you should not install any application on WebLogic admin console. So, it’s run-time console, should not affect your domain. WLSDM’s AdminServer overhead is negligible; one of the least overhead in the market; because we are not injecting any code to run-time classes. Maximum overhead for the managed server (considering backend monitoring is open) is about 3%-4%.

You had better, test on your current domain; because your domain is extra ordinary and you will see that WLSDM would be one of the best solution for this domain and its infrastructure.

Regards…

@jeba

Hi Jeba,

Also, check “store data” for back-end monitorings. It may generate too large data sets. especially if the “WebLogic Diagnostic Volume” set high for the related managed server.

Capture4.PNG

I enabled the store option for all of our datasources. So, in total there were around 75. Would this be an issue?

75 data sources cost you avg ~30 Mb per day (it depends on your metric instance count). If you have enough disk space it is not an issue.

How can I control the retention period for these metrics collections?

You can change the archive date range from the “Configuration> WLSDM System Settings” page. Archive module purges your data beyond the given date range. But do not reduce the date range instantly. You have too much data on your database and it may cause too much memory consumption. Prefer gradual reduction (like 3 or 5 days).

“system.archive.metric.data.range”

Capture2.PNG

Regards.

@jeba

Hi Jeba,

WLSDM does not have the feature for your requirement which is giving a threshold for the specific IP/hostname.

But it could be a nice feature, we will evaluate this feature for the next releases.

Regards.

Hi Tom,

You can filter back-end dashboard threshold value in “Configuration > WLSDM System Settings > system.monitoring > system.monitoring.diagnostic.backend.event.filter.threshold” property. Click edit button and give threshold value as 1000 (ms).

Regards.

1.png