Dell component in unmonitored state

Hi,
Under Monitoring/Dell/State Views/CMC, a number of components are listed but have Open Circles next to them.
One of the components is Dell Chassis Power Supply Group.
How can this be turned from being Not Monitored to Monitored? (Object Discoveries seem enabled to me, but I must be looking in the wrong place. The chassis are discovered fine).
Thx,
John Bradshaw

Hi,
It seems like that you are using Dell management pack to monitor Dell component, have you followed the management pack guide to configure it?
The not monitored icon indicates that there are no monitors for the object. When an object shows as not monitored, check whether the appropriate management pack for monitoring the object is imported. Ensure that the appropriate monitors are enabled.
Sometimes restarting the System Center Management Health service on the agent-managed computer can resolve the issue. You can also try placing the object in maintenance mode for several minutes.
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Similar Messages

Component binding and state saving

Hello,
I have a few questions in regards to component binding and state saving (specifically in regards to the reference implementation) when the saving method is client and backing-beans are in the request scope rather than in the session scope:
1) if a component instance is bound to a backing-bean property then does the state of that component get saved when the view state is saved?
2) for UIData component, if the component value is bound to a list, does the actual list (after being wrapped) serve as the local data for the component? If this is the case, when the state is saved and then subsequently restored, does the list get re-created with the original number of items?
Regards,
Len Takeuchi

Thanks for the quick response.
(2) The actual list is not saved; the list will be
re-queried on subsequent requests.The list composition may have changed by the time the list is re-queried. If the table being displayed is updatable then transfer of information from request back to the list (during Apply Request Values) may not happen properly. So does that pretty much mean that the original list has to be kept around (in the session)? If the state saving method is server then does the saved state maintain a reference to the original list across requests?
Len Takeuchi

Revert custom component to default state?

I am building a website which has multiple pages, and within those pages are image galleries. I have used custom components for the galleries so i dont end up with an unmanagable amount of main pages. (15 pages containg galleries of up to 7 images) The problem is when you navigate away from a page and then back to that page the custom component remains in the state it was left in, obviously you would want an image gallery to always revert to the first image. (this is also the case with flvs) Is it possible to make a component revert to a particular state? I dont realy have to skills to do it in builder or anything unless it was very simple.
thanks!

Hi lucky_p,
There is a great post on the FlashCats blog that explains how to get components to reset after a state change; I think this may answer your question:
How do I get Flash Catalyst components to reset after changing states?
Hope that helps.
Regards,
Kim

Custom Component vs. States

Dear Catalyst team,
After trying to work around the 15 states limitation by converting them into custom components. I ran into the problem that the pages of those custom components have the tendency to change their apearance relatively to the first page of the custom component. As a result, moving a button element up a bit from the first page to the next will, when running, move the same element up EACH time I click it, moving it out of the screen eventually. Is there a way to anchor the elements in a custom component? Otherwise, by the complex nature of my project, I might run into a dead end. Please let me know if you know of any solution.
All the best,
Wulffrunner

ok, got it:)
so how about this:
Can I trigger action sequences outside of the custom component
using buttons that are in the custom component, and vice-versa?
Haven't found a way to do this yet...

Open tree component in expanded state

I have built a small framework to display demos -- and use an
XML-driven tree component to provide access to demo segments and
published files.
I would like the TOC in the Tree component to open in
expanded state, but am having no luck with myTree.setIsOpen.
The tree connects to the XML OK -- I can expand/collapse,
etc... and it all looks great. But I cannlt get the tree to open
expanded.
The code I'm trying to open the TOC expanded:
this.demoTOC.setIsOpen(this.demoTOC.getTreeNodeAt(0), true);
OR
this.demoTOC.setIsOpen(this.demoTOC.getTreeNodeAt(0).getTreeNodeAt(0),
true);
The XML that's connected to the tree:
<?xml version="1.0" encoding="UTF-8"?>
<toc>
<demosection label="MY TITLE" >
<demo ID="00demo.flv" label="title01" isBranch="true"
/>
<demo ID="01demo.flv" label="title02" isBranch="true"
/>
<demo ID="02demo.flv" label="title03" isBranch="true"
/>
<demo ID="03demo.flv" label="title04" isBranch="true"
/>
</demosection>
</toc>
If anyone can point out what I'm doing wrong, I am ready to
learn.
Thx.

Never mind -- figured it out.
It was a scoping issue -- calling the setIsOpen form inside
the XML loader function.

How to Dynamically Display Different ViewStack component without using State?

I have a type column in a datagrid record, when type = A, I want to display ViewStack A, when type = B, I want to display ViewStack B, any body can give me some clues? sample code is best. Thanks a lot. BTW, I don't want to use state to control them, as both ViewStacks are already within the same application state.

hi,
you can try something like this.....
David.
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute" minWidth="955" minHeight="600">
<mx:Script>
<![CDATA[
import mx.collections.ArrayCollection;
import mx.events.ListEvent;
[Bindable] private var arr:ArrayCollection = new ArrayCollection([
{info:"record 1", type:"A"},
{info:"record 2", type:"B"},
{info:"record 3", type:"A"},
{info:"record 4", type:"B"}
protected function dg_changeHandler(event:ListEvent):void
if (arr[dg.selectedIndex].type=="A") tn1.visible = true else tn1.visible = false;
tn2.visible = !tn1.visible;
]]>
</mx:Script>
<mx:DataGrid id="dg" x="279" y="239" dataProvider="{arr}" change="dg_changeHandler(event)">
<mx:columns>
<mx:DataGridColumn headerText="Info" dataField="info"/>
<mx:DataGridColumn headerText="Type" dataField="type"/>
</mx:columns>
</mx:DataGrid>
<mx:TabNavigator x="279" y="408" width="200" height="200" id="tn1">
<mx:Canvas label="Tab 1" width="100%" height="100%">
</mx:Canvas>
</mx:TabNavigator>
<mx:TabNavigator x="507" y="408" width="200" height="200" id="tn2">
<mx:Canvas label="Tab 1" width="100%" height="100%">
</mx:Canvas>
</mx:TabNavigator>
</mx:Application>

States in a custom component

I am having a problem getting my states to view correctly from a custom component.
I call in the custom component that has states in it, and they do not view correctly.
Here is an example:
The states from my custom component:
<mx:states>
        <mx:State name="state1">
            <mx:RemoveChild target="{formitem3}"/>
            <mx:RemoveChild target="{hbox4}"/>
            <mx:RemoveChild target="{vbox1}"/>
            <mx:RemoveChild target="{panel24}"/>
            <mx:AddChild relativeTo="{hbox3}" position="before">
                <components:SensitivityValue2 variableString="Capital Cost Multiplier" unitsString="" close="currentState=''"/>
            </mx:AddChild>
            <mx:RemoveChild target="{button31}"/>
        </mx:State>
        <mx:State name="state2">
            <mx:RemoveChild target="{formitem3}"/>
            <mx:RemoveChild target="{hbox4}"/>
            <mx:RemoveChild target="{vbox1}"/>
            <mx:RemoveChild target="{panel24}"/>
            <mx:AddChild relativeTo="{hbox5}" position="before">
                <components:SensitivityValue2 variableString="Replacement Cost Multiplier" unitsString="" close="currentState=''"/>
            </mx:AddChild>
            <mx:RemoveChild target="{button1}"/>
        </mx:State>
and here is how I am calling in the custom component to my main application:
<components:MyCustomComp id="customComp" width="100%" height="100%" label="CustomComp"/>

when you switch to a state (by click a button) it should just move some icons down and
insert a panel.
And when you switch back it should just move everything back up and remove the panel.
What does happen is nothing, or an error, or it adds the panel to a strange location.

Change base view state from a custom component

I'm pretty new to flex and I'm having a small issue in change the view state from a component.
My Application have 2 custom components called userlogin and main menu. In the main application page I have userlogin component in one state and the main menu component in another. I'm trying to change the state if the login in successful from user login to main menu. I have the following function written inside the login component.
private function IsUserLoggedIn(evt:ResultEvent):void
                if (evt.result.islogin.toString() == "true")
                    currentState = "MainMenu";
                else
                    Alert.show("Login failed, please try again.", "Login Failed");
This code worked when I had all the controls in the main page. But then I created components and included them in to components and now when the login is success, its giving the following error.
ArgumentError: Undefined state 'MainMenu'.
    at mx.core::UIComponent/getState()[E:\dev\4.0.0\frameworks\projects\framework\src\mx\core\UI Component.as:9908]
    at mx.core::UIComponent/findCommonBaseState()[E:\dev\4.0.0\frameworks\projects\framework\src \mx\core\UIComponent.as:9928]
    at mx.core::UIComponent/commitCurrentState()[E:\dev\4.0.0\frameworks\projects\framework\src\ mx\core\UIComponent.as:9750]
    at mx.core::UIComponent/setCurrentState()[E:\dev\4.0.0\frameworks\projects\framework\src\mx\ core\UIComponent.as:9701]
    at mx.core::UIComponent/set currentState()[E:\dev\4.0.0\frameworks\projects\framework\src\mx\core\UIComponent.as:6087 ]
    at components::UserLoginForm/__btnSubmit_click()[C:\Projects\WarrantyAutomation\src\componen ts\UserLoginForm.mxml:60]
I'm sure this has something to do with accessing the states from a custom component, but I do not know how to change the state to the main menu. Please help me with this. Any help is greatly appriciated.

Hi dasun1981,
private function IsUserLoggedIn(evt:ResultEvent):void
                if (evt.result.islogin.toString() == "true")
                    currentState = "MainMenu";
                else
                    Alert.show("Login failed, please try again.", "Login Failed");
If I am right the above function is in your userlogin component and the two components "userlogincomponent" and "maincomponent" are in main application file and the states were also defined in main application file.
But in the function above the currentState refers to the state of the userlogin component and not the main application ...but the states are defined in main application file...that's the reason why the exception was thrown...
Instead you replace the line in the above function with the below line:
Application.application.currentState = "MainMenu";
Please mark it as answer if it helped you.
Thanks,
Bhasker Chari

Change States in component from main view

The scenario like this:
The main view includes many component views. On my main view
there have a radio button to choice different role type, for
example: admin and user. For different role have different views.
But they don’t have big difference.
My question is how could I implement my component view change
states when I click button on the main view? I don’t want do
change states in main view since I need create two component views
for different roles.
Thanks.

Consider adding a second state to your application, even if
you don't put anything into it.
In each of the components that should change state when the
role is changed, add a listener on the application for the state
change event ("currentStateChange"). When this event is fired,
query the application for its current state:
var appState:String = (Application.application as
Application).currentState;
Use that to change the state of the component. Remember
you'll also need to do this when your component is first
created.

Throwing error message for a component

I have a form in which there are several fields. One of field is LOV for which i do some validation on valuechangeListener. If that validation fails, i send error to the form for that particular field. It is working fine. but after this if user submits the form, it is submitted. In case of validation failed by framewrok, it is not submitted. HOw i can set that component in error state so that form is not submitted. I am using following code to throw error or component:
FacesMessage msg = new FacesMessage(FacesMessage.SEVERITY_ERROR, null, "Invalid value");
FacesContext context = FacesContext.getCurrentInstance();
context.addMessage(binding.getClientId(context), msg);
I am using Jdeveloper 11g with latest patch set of ADF i.e. 11.1.3.x

Hi,
actually you are not throwing an error but set a message to display to the user. Can't you just create a validation for the input field. The field has a property for you to define a managed bean validation reference. You can generate the method skeleton from JDeveloper.
Frank

Reset custom component

Hello!
I have an app with some states.
Each state shows a different custom component.
My problem is that if someone types somthing in one of the states then changes state and then comes back the text will still be there.
Is there a way to reintitialize the custom component on each state chage or do I have to create functions to reset everything myself?
Thank you!

Ok, thank you.
Were they only Form fileds it would have been nice and easy.
I have some AMF calls etc.
I could probably remove the component with removeChild and add it when it's accessed again I guess, but that doesn't seem too elegant.

Operations on a Shutdown Component.

I solicit your views on the behavior:
I shutdown a component.
I attempt a shutdown operation or a stop operation.
Should a JBI Exception be thrown?
SUN RI throws an exception.

Hi Ron,
There are two places in spec component life cycle diagram is given, one in Management chapter and one in Component Framework chapter. Both differs in transition from shutdown to stop state. Prior does not allow while later allows it. Which one to be followed?
Again under System Restart topic in Component Framework chapter:
The JBI implementation MUST persist the running state of each component, such that, upon system restart, the implementation will attempt to restore each component to its previous running state.If we follow the life cycle depicted in Management chapter and let us say component was in stopped state. Restart the system how will the JBI implementation take the component to stopped state? It has to momentarily start the component, which I think should not be the desired behavior.
Expecting your direction on this!
--Rajesh

Best practice - transitions without state?

I'm noticing that, sometimes, its easier to just do a
Transition on a component without having the changes in a State.
For example, I can't seem to get a sequence of Resize effects
when the properties are set in State, but I succeed when I empty
out the state. No combination of SetPropertyAction seems to work.
Is this a best practice? Or is it considered sloppy? How do
you decide what to put in a State, and what to put in a
Transition?

I have been coding Flex for a little over 2 years and the
first project used states. We moved away from states because we ran
into a couple bugs (in Flex 2) and it made the code less easy to
read and organize.
Transitions seemed more natural from a coding aspect. So now
most everything is done in transitions and once in a while a custom
component will use states.

mx:states & button click problem.

Hi,
I use <mx:states> build two screen,(base state and
screen).
I have button on <base state>,for the click event I add
the code like
<mx:Button x="105" y="323" label="Button"
click="currentState='screen1'" id="button1"/>
But when I put the button in a mxml component and then I add
the component on base state.
I get error when I use the same code and click the button.
MAIN PAGE
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
layout="absolute" xmlns:CTComp="*">
<CTComp:page1 id="page11"/>
</mx:Application>
page1.mxml
<?xml version="1.0" encoding="utf-8"?>
<mx:Canvas xmlns:mx="
http://www.adobe.com/2006/mxml"
width="400" height="300">
<mx:Label x="51" y="89" text="Requestor"/>
<mx:TextInput x="133" y="87"/>
<mx:Button x="133" y="136" label="Login" width="103"
click="currentState='screen2'"/>
<mx:Label x="112" y="33" text="Catering Request Form"
width="158" fontWeight="bold" fontSize="12"/>
</mx:Canvas>
How to fix the button event on mxml component?Thanks for help
M

To get this working correctly, you need to import
mx.core.Application:
<mx:Script>
<![CDATA[
import mx.core.Application;
]]>
</mx:Script>
Then you can access the
Application.application.currentState='yourState' through your click
handler:
click="Application.application.currentState='yourState'"

Overlay a component with another component?

Can you overlay a component with PopUp-like component that
doesn't overlay the entire Application?
I have a dashboard application that displays smaller
sub-components that each call out to a WebService to retrieve data.
I am able to create a PopUp for each and center it over the
sub-component in order to show a Progress Bar, but each PopUp ends
up overlaying the entire application, when I want it to simply
overlay the individual sub-component. Is there anyway to do this
with Flex 3? Like, some kind of layering or something?
Thank you.

Why not create states within the component wherin a state
contains the pop up?
That would make the popup a child of the component

Dell component in unmonitored state

Similar Messages

Maybe you are looking for