1. Webview is working very slowly
Have you configured the webview agent within the webview.lax file? Have you deployed the webview management module? Both of these help put some of the performance issues in webview in perspective... (lol, see what I did there)
We had an slowness with webview and we increased the memory by the webview.lax file to 3 GB and that appears to help. Depending on how many elements WebView has to deal with, results may vary.
2. You gotta give me a bit more than the attribute name or attribute value. is 'wsOperation" an attribute if so what is the value, if it is an attribute value, then what was the attribute name.
Each of the different agents will have a standard set of basic attributes. Wished I could screen shot one of my team center nodes, but since the screen shot has server names and such, I am not allowed unless I blank out all of the nouns, but at that point, there isn't a point.
Away from the basic attributes, each agent will declare other attributes and appear to be very broad depending on the agents you are using.
3. Creating a beginning perspective
We are on version 10.0 and there are some features in 10.2 and 10.5 that might help with building up your perspectives. For my first perspective, I started with the Hostname out of the box perspective and add a custom attribute that would be meaningful to the profile user for that perspective. Such as CRM, Mobile, WebServices, if your hosts can be divided into like nodes. Try to use the nouns that the end user would recognize.
Then you can add a new perspective using your new custom attribute as one of the defined levels. In my case, it was Environment
You could give your perspective name something that the end user would identify with. Production Support, NOC, Environment, etc.
For a beginning perspective, you really need to know your end users, their profiles, what are interested in, which group, which applications, which business elements or are you talking enterprise wide beginning perspective, sort of like the big "your business is doing" status button?
If it is a big button, then create a new custom attribute, company and tag everything through a rule to have everything in one node. Then build a perspective "company" that will basically have one single node with the alert counts and such on it.
I'm taking a slightly different route. Instead of trying to fit our best guess dashboards, metrics and the other parts into team center, I'm trying to use the native elements of team center to define or provide nouns and verbs to define the end users. Yes, the majority of our dashboard effort was to try to discover the nouns and verbs from the end user view, and that has us caught up in the misconceptions of what APM is, how it can help and how APM will relate data, actions and targets.
Then once the base nouns and verbs are not enough, then I link in a dashboard with a URL link to the nodes within Team Center to change the dictionary away from the team center nouns and verbs to the custom end user terms.
Hope this helps,
Billy