BizTalk360 - Administration
We love your feedback and look forward to hearing from you. A great place to post your ideas and vote up others. Please share your stories to help us build a product that best fits your needs.
Please note this site is only to get future ideas and suggestions. If you have any technical challenges with the current version of BizTalk360 please use our support site
Version 11.2 is now released. Download and give it a try
You can provide any ideas/suggestions related to the Administration & Operations capabilities of BizTalk360 in this forum.
- or
No existing idea results
- ~ No ideas found ~
116 results found
-
Customizing grids in Message Box Queries
We have the following situation at our Customer LichtBlick SE. The customer resumes messages based on the URI. So they must know what is the end system to decide if the message will be resumed or not. That works well. But now we are implementing a FIFO pattern with ODX possibilities so if a ODX breaks this will be suspended and all messages too. But we do not see the URI on the suspended messages even if we set transport location and transport type in the context. So our customer cannot decide which messages shall be resumed. If there a way to use custom promoted properties in this way, so we can set them to some values or you can show the URI. Is there an easy way to put the error description on the grind like the error code? Error code is not really helpful.
- Idea shared by Milen Koychev.
We have the following situation at our Customer LichtBlick SE. The customer resumes messages based on the URI. So they must know what is the end system to decide if the message will be resumed or not. That works well. But now we are implementing a FIFO pattern with ODX possibilities so if a ODX breaks this will be suspended and all messages too. But we do not see the URI on the suspended messages even if we set transport location and transport type in the context. So our customer cannot decide which messages shall be resumed. If there a…
1 vote -
Message delay and message delay by shapes in orchestration in BizTalk360
To implement message count, message delay and message delay by shapes in orchestration in BizTalk360? We don’t have any way to monitor how may message processed by BizTalk and where in orchestration it caused to delay.
- Idea shared by Markand Patel
1 vote -
Information on Receive location for MQSC
I'd like to know if you could add the information "Polling Interval" on the Receive Locations for MQSC ?
MQSC adapters
By Steve Melan
1 vote -
Graphics for data in the msgbox
I have interest in the graphical representation of the (technical) flow, which I can map to a model (logical flow) that those administrators do understand.
If an interchange completes and gets into the tracking database I have those graphics, very nice.
But, I would also like such graphics for data in the msgbox e.g. an interchange in process waiting to continue.
Can I visualize data still in the msgbox with BizTalk360?- Idea Shared by Gerard Michels.
1 vote -
ESB authentication while resubmission
Need an feature to "Specify the username and password to Re-submit messages".
By- Fabio Marini
1 vote -
ESB resubmissiom improvements
It appears from the profiler output that 360 uses hard-coded SQL for updating messages upon resubmission.
A stored proc exists for doing this, named uspUpdateMessage – ,Is this can be taken in BizTalk3601 vote -
BAM Aggregations
We use BAM Aggregations to give our IT Operations Managers a summarised view of the state of the BizTalk system in terms of volumes which can be used to identify possible contention issues.
1 vote -
Providing KB Article on Generic Level
Currently the KB articles can be created only for
Service Instances
ESB Exceptions
Event Logs
Throttling DataWe need a provision to create KB article for 'General' category where we can provide KB articles for issues apart from the above 4.
This will help the new users of BizTalk 360.
9 votes -
See metrics grouped by BizTalk Application
We have over 100 applications in BizTalk and we would like to see metrics for each of them individually (performance, message volume, alerts, errors, etc.).
2 votes -
Graphical message flow (tracking) link to messaging pattern
In the Graphical Message flow (Tracking), if a related messaging pattern exists, it could be good to have a link to it so to see the KPIs.
1 vote -
Direct link between Monitoring and Operations tabs
When you see for example a stopped send port in the monitor tab, I want a direct link to the corresponding operations tab so I easy can start the send port again. As it functions today you need to perform five or six steps before you can start the send port.
2 votes -
Ability to "Find the Failed Messsage" (As per Biztalk Administration capabilities)
Within Biztalk Administration Console, when viewing a suspended instance you can right click and "Find Failed Message" This is key to us as often we need to remove the failed message and resume the rest in the queue. (Terminate kills all messages and resume just resends the same failed one, resulting in them being suspended again)
2 votes -
View Hydrated Orchestrations
In BizTalk Admin Console you have the option to view all Dehydrated Orchestrations directly from the group overview.
That was a quick way to view all dehydrated orchestrations and would be helpfull in BizTalk360 as well.
BizTalk 360:
In BizTalk360 you an see the dehydrated orchestrations in the Mssagebox queries or in the grafhical flow but is not posible to view only the dehydrated orchestrations. In some cases that should be very helpfull.In the messagebox queries it is not posible to choose Dehydrated.
In the Graphical Flow you can add a filter on state but it is not posible tot choose the state dehydrated.
Is this because there are no dehydrated items or is that status missing.In one of those or maybe even in both I'd expected to be able to choose Dehydrated to see all dehydrated orchestrations
In BizTalk Admin Console you have the option to view all Dehydrated Orchestrations directly from the group overview.
That was a quick way to view all dehydrated orchestrations and would be helpfull in BizTalk360 as well.
BizTalk 360:
In BizTalk360 you an see the dehydrated orchestrations in the Mssagebox queries or in the grafhical flow but is not posible to view only the dehydrated orchestrations. In some cases that should be very helpfull.In the messagebox queries it is not posible to choose Dehydrated.
In the Graphical Flow you can add a filter on state but it is not posible…3 votes -
BAM Portal drill down
Currently Via BizTalk 360 its not possible to drill down, to get example the XML message or look at the details. It only gives an Overview.
8 votes -
Expected State should be clearly visible when starting or stopping Artifacts
When restarting many Artifacts (Ports or Host Instances) the Expected State should be clearly visible in order to avoid wrong manipulation (for instance: restarting a port which should remain stopped).
Also, the Application or Artifcat should be Red only if an artifact is not in the Expected State, not if an artifact is stopped (which could be the Expected State).3 votes -
Link in error information
When you have a suspended message and go into:
"Service Properties -> Error Information"
in order to see the error message.
It would be handy if the path to a server /folder could be a clickable link in the "Error Description"0 votes
- Don't see your idea?