Endodontics

Two new platinum complexes, trans-chlorodiammine[N-(2-aminoethyl)-4-[4-(N-methylimidazole-2-carboxamido)-N-methylpyrrole-2-carboxamido]-N-methylpyrrole-2-carboxamide]platinum(II) chloride (DJ1953-2) and trans-chlorodiammine[N-(6-aminohexyl)-4-[4-(N-methylimidazole-2-carboxamido)-N-methylpyrrole-2-carboxamido]-N-methylpyrrole-2-carboxamide]platinum(II) chloride (DJ1953-6) have been synthesized as proof-of-concept molecules in the design of agents that can specifically target genes in DNA. Coordinate covalent binding to DNA was demonstrated with electrospray ionization mass spectrometry. Using circular dichroism, these complexes were found to show greater DNA binding affinity to the target sequence: d(CATTGTCAGAC)(2), than toward either d(GTCTGTCAATG)(2,) which contains different flanking sequences, or d(CATTGAGAGAC)(2), which contains a double base pair mismatch sequence. DJ1953-2 unwinds the DNA helix by around 13 degrees , but neither metal complex significantly affects the DNA melting temperature. Unlike simple DNA minor groove binders, DJ1953-2 is able to inhibit, in vitro, RNA synthesis. The cytotoxicity of both metal complexes in the L1210 murine leukaemia cell line was also determined, with DJ1953-6 (34 microM) more active than DJ1953-2 (>50 microM). These results demonstrate the potential of polyamide platinum complexes and provide the structural basis for designer agents that are able to recognize biologically relevant sequences and prevent DNA transcription and replication.

New and higher yielding synthetic routes to N-protected N-methylpyrrole and N-methylimidazole amino acids are introduced to circumvent difficulties associated with established schemes. Key steps in each synthesis include copper-mediated cross-coupling reaction to directly install a carbamate-protected 4-amine in the N-methylpyrrole derivative and effective nitration followed by a one-pot reduction/Boc protection of the amine in the synthesis of the N-Me-imidazole amino acid.

ABSTRACT An agile, lightweight, but secure extensible hybrid application container and deployment mechanism for mobile devices has the potential to provide improved cross platform support, reduced development lifecycle time and a consistent application security model within large organizations. We demonstrate how such an architecture can provide a set of security and mobile device management interfaces to lightweight applications written in a high level markup and scripting language and also how these applications can be provisioned via push or pull mechanisms to an Enterprise user's device. The use of such a container for hybrid applications widens the potential support and development resource within an organization to employees possessing readily available skill sets, this permits mission critical applications to be developed in a much shorter time frame than with native mobile application deployment methods.

ABSTRACT Enterprises today are faced with critical decisions as they consider exposing corporate data and applications to mobile devices. Many employees already own smartphones and tablets that have now matured to a point where these devices can be effectively managed using mobile device management (MDM) products. While this maturing device capability may provide the platform for enterprises to ensure a certain level of corporate compliance, MDM systems alone do not provide separation between corporate and personal assets in such a way that the “bring your own device” (BYOD) community is willing to adopt it. Key questions such as “Who owns the data on the device?” or “Does the enterprise have the authority to wipe away some or all of the data on a device upon concern of a security breach?” must be addressed. To extend the utility and flexibility of personally owned mobile devices in the enterprise, device management as well as asset separation should be considered. Unlike traditional corporate-issued laptops, which can be protected by full disk encryption techniques, mobile devices are more diverse in their individual platform capabilities. In addition, at most enterprises, most mobile devices that are brought forward for business purposes are personally owned, and this presents unique challenges. For personally owned enterprise-connected devices, it is important to preserve the user experience as it relates to personal use while providing a containerized enterprise experience as well as the additional layers of authentication that the enterprise imposes. This paper describes IBM's internal transformational journey relating to the creation of a comprehensive mobile ecosystem, highlighting newer revolutionary mobile device virtualization and containerization technologies that can separate personal and enterprise assets, provide for a transparent personal device experience, and ensure the security requirements of the enterprise.

ABSTRACT As employees began to bring their consumer mobile devices to the office, employees expected corporations to embrace or to provide solutions similar to consumer solutions they were used to on their smartphones. However, because of accountability and security concerns, many enterprises prefer employees use corporate alternatives to popular consumer apps. However, many of these expected enterprise alternatives to consumer solutions were not available to employees. In this paper, we discuss lessons learned during the BYOD (Bring Your Own Device) transformation process leading to the rapid development and deployment of internal alternatives to consumer applications, as well as the introduction of technologies to reduce the cost brought on by a large influx of mobile devices connected to the enterprise. We also discuss the importance of a filtered approach to access content through the firewall into the enterprise arena as an alternative to the full virtual private network approach granted to PC devices.