I hope this is anwered.
If not, You can use the send manual event button on TSIM event console and select destination and event class. Also have option to select the respective slots you would want your event to carry along.
From CLI, you can use the msend command to send event. you can refere Msend this discussion from communities to understand how msend works.
Actually I have integrated with Remedy for ticket creation.
For example, Unfortunately some technical problem alerts are showing in BPPM, but ticket was not created.
1)So can i use this option to push the alert into Remedy for ticket creation?
2)For example, if already alert is generated and ticket created and still it is active. So if i push this event manually, then existing ticket will be close and create new ticket?
No, you would not use the Send Manual Event feature to push an existing alert into Remedy for ticket creation. Send Manual Event would send a new alert into BPPM and it would only cause a ticket to be created if it matched the Event Management Policy that controls which alerts will create tickets.
We provide a Remote Action called Trigger Remedy Incident For Event that will create a Remedy ticket for an event selected on the BPPM Operations Console. You can find instructions on how to launch the Remote Action here. Remote Actions are automated actions that are executed for events. BPPM comes with a number of pre-defined Remote Actions, but you can also create your own. In this case, you don't need to create an action since we provide one out-of-the-box.
Regarding your second question, if an alert has caused a ticket to be created, sending the same event into BPPM again with a status of 'OPEN' will not cause the ticket to be closed. It will most likely be suppressed (de-duplicated). If it isn't, depending on how the integration is configured, it will either create a new ticket, or add a note to the work log of the existing ticket. The second behavior will happen if the CMDB integration to BPPM is enabled and the ticket is linked to a Configuration Item (CI).
Tickets are only closed automatically when the alert in BPPM is closed, either manually on the BPPM Operations Console, or automatically by the analytics engine, an MRL rule, or an Event Management policy.